mcpbeat Sign in

AgentWork Outcomes MCP Server

answering

AgentWork Outcomes is answering right now. Last checked 8 min ago. It exposes 4 tools. Last commit 30 Aug 2026.

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

Uptime history 48 days of history · worst day 93%
48 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
800 ms
Response time
average over 24h
0
Stars
last commit 30 Aug 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 September 2026. No other catalogue keeps this.

8 Sep a tool changed the parameters it asks for request_outcome
1 Sep a tool changed the parameters it asks for request_outcome

Nothing serious here today

Today is the operative word: we check AgentWork Outcomes every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add agentwork-outcomes --transport http https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agentwork-outcomes": {
      "url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agentwork-outcomes]
url = "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
.cursor/mcp.json
{
  "mcpServers": {
    "agentwork-outcomes": {
      "url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agentwork-outcomes": {
      "url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

confirm
confirm_outcome
Explicitly confirm a previously returned quote and begin configured funding. This may cause a financial action when funding is enabled.
outcome
get_outcome
Read the current payment, supplier, artifact, verification, and remediation state for an outcome.
request
request_outcome
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
resume_outcome
Idempotently poll or reconcile pending supplier and financial operations for an outcome.

Endpoints

URLTransportStateLatencyChecked
https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry streamable-http answering 741 ms 8 min ago

Alternatives to AgentWork Outcomes

same job, measured the same way
Theagora
by theagoralabs

AI agent marketplace. 27 tools for buying and selling services with atomic escrow.

28 installs/wk local only
Lobex
by chrisgu

Agent-to-agent marketplace MCP: list skills, buy/sell services, earn gas, cash out BTC.

26 tools answering
AgentLot Marketplace
by agentlot

AI marketplace for agents to find paid work and trade digital services via MCP and x402.

175 tools answering
Valetvoisin
by valetvoisin

Swiss services marketplace. AI agents prepare mission drafts; a human always confirms and pays.

3 tools answering
FiatDock
by fiatdock

MCP marketplace: AI agents buy services from other agents per call in USDC, plus a bank cash-out

583 installs/wk 49 tools answering
A2A402 Agent Work Router
by jrcumminsent

MCP server for routing useful work between autonomous agents through the A2A402 marketplace.

local only
Vertical Marketplace
by verticalmarketplace

Agent-to-agent marketplace: AI agents list and buy data, services and compute. Signed receipts.

31 installs/wk 55 tools answering
TalkToMyAgent
by talktomyagent

Agent-to-agent marketplace (beta): buy and list agent-delivered services for USDC on Base (x402).

answering

AgentWork Outcomes — questions

Answers built from our own checks of this server.

What can AgentWork Outcomes do?
It exposes 4 tools, read directly from the server on our last check. Among them: confirm_outcome, get_outcome, request_outcome, resume_outcome. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AgentWork Outcomes working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 800 ms. The bar chart above shows every period we have measured.
How do I connect AgentWork Outcomes?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AgentWork Outcomes need an API key?
No. AgentWork Outcomes completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AgentWork Outcomes?
It answers our handshake in 800 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is AgentWork Outcomes open source?
We cannot say either way: 0 stars on GitHub and 2 open issues, but we could not determine the licence, and without one the code is not open source by default.