Skip to content

AgentWork Outcomes

by mitchellOpZero · remote · no sign-in to list tools · v0.1.0 · published by GitHub user mitchellOpZero

Buy a finished outcome through services, agents, marketplaces, humans, tools, or swarms.

Changes · 3
CompareRegistry entry

4 tools: 3 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http agentwork-outcomes https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 3Claude Code: ask
  • confirm_outcomeExplicitly confirm a previously returned quote and begin configured funding.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Explicitly confirm a previously returned quote and begin configured funding. This may cause a financial action when funding is enabled.
  • request_outcomeFind a reliable procurement plan for an outcome and return one retail quote for confirmation.No findings

    Why it is in this group

    • The name "request_outcome" says "request": a word for a change.
    Description, as the server wrote it
    Find a reliable procurement plan for an outcome and return one retail quote for confirmation. This does not spend, post, purchase, or invoke anything.
  • resume_outcomeIdempotently poll or reconcile pending supplier and financial operations for an outcome.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Idempotently poll or reconcile pending supplier and financial operations for an outcome.
Only reads 1Claude Code: allow
  • get_outcomeRead the current payment, supplier, artifact, verification, and remediation state for an outcome.No findings

    Why it is in this group

    • The name "get_outcome" says "get": a word for reading.
    Description, as the server wrote it
    Read the current payment, supplier, artifact, verification, and remediation state for an outcome.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agentwork-outcomes https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agentwork-outcomes__get_outcome"
    ],
    "ask": [
      "mcp__agentwork-outcomes__request_outcome",
      "mcp__agentwork-outcomes__confirm_outcome",
      "mcp__agentwork-outcomes__resume_outcome"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agentwork-outcomes. Review it before you use it.