Buy a finished outcome through services, agents, marketplaces, humans, tools, or swarms.
Connect Remote server
claude mcp add --transport http agentwork-outcomes https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry
{
"mcpServers": {
"agentwork-outcomes": {
"url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
}
}
}
{
"servers": {
"agentwork-outcomes": {
"type": "http",
"url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
}
}
}
Settings > Connectors > Add custom connector
URL: https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry
Tools 4 found in our last check
request_outcomeFind a reliable procurement plan for an outcome and return one retail quote for confirmation. This does not spend, post, purchase, or invoke anything.
confirm_outcomeExplicitly confirm a previously returned quote and begin configured funding. This may cause a financial action when funding is enabled.
get_outcomeRead the current payment, supplier, artifact, verification, and remediation state for an outcome.
resume_outcomeIdempotently poll or reconcile pending supplier and financial operations for an outcome.
Details
| Endpoint | https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry (Streamable HTTP) |
| First published | 30 Aug 2026 |
| Last updated | 30 Aug 2026 |
| Registry name | io.github.mitchellOpZero/agentwork-outcomes |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
