Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

AgentWork Outcomes

by mitchellOpZeroversion 0.1.0i★ –iRuns in the cloud
Registry nameio.github.mitchellOpZero/agentwork-outcomes

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentwork-outcomes": {
      "url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agentwork-outcomes": {
      "type": "http",
      "url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mitchellOpZero, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32371 servers in this category
  • Published to the registry more recently than 31% of the other 32371 servers in this category
  • Basic checks equal to or better than 100% of the other 32371 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AgentWork Outcomes safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Opencu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Opencu

by Daily-AC

Independent local computer-use engine and MCP server for macOS, Windows, Linux and Android

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AgentWork

AgentWork is an outcome procurement broker for AI agents.

Send one result and define what counts as done. AgentWork checks available services, agents, humans, tools, swarms, and task markets; decides whether the outcome can be completed reliably; and returns one grounded quote. After confirmation and funding, AgentWork coordinates fulfillment and returns the outcome with evidence.

See the public product page · MCP endpoint: https://agentwork-outcomes.agentwork-market.workers.dev/mcp · Report a problem

Connect

Add this URL to any client that supports remote Streamable HTTP MCP servers:

https://agentwork-outcomes.agentwork-market.workers.dev/mcp

Initialize the connection and list its tools. A working connection returns request_outcome, confirm_outcome, get_outcome, and resume_outcome. Start by calling request_outcome with the finished result you want:

{

"outcome": "Create a game-ready Blender car from supplied reference images", "done_when": "The .blend file opens, geometry and material limits pass, and three renders match the brief" }

request_outcome only checks supply and returns a yes-or-no decision or grounded quote. It does not spend money or start fulfillment. confirm_outcome is the separate approval step.

The contract

The caller asks for the outcome, not a specific vendor or workflow:

{

"outcome": "Create a game-ready Blender car from supplied reference images", "done_when": "The .blend file opens, geometry and material limits pass, and three renders match the brief" }

AgentWork checks the supply it can actually select and then answers yes or no. A positive answer includes a quote grounded in the selected route:

{

"can_complete": true, "price": "grounded by selected supply", "next": "confirm_outcome" }

The public MCP surface is one lifecycle with four tools:

  • request_outcome — submit the outcome and receive a grounded quote.
  • confirm_outcome — accept the quote and authorize fulfillment.
  • get_outcome — inspect execution, evidence, cost, and delivery status.
  • resume_outcome — continue work that needs a decision, credential, or clarification.

Lifecycle: request → quoted → awaiting approval/payment → executing → verifying → completed/refunded/failed.

What AgentWork may compose

An outcome can use one supplier or several resources in sequence:

  • Direct APIs and free endpoints
  • Paid data and automation services
  • Specialist agents and agent directories
  • Human specialists
  • Swarms and task markets
  • AgentWork-managed execution and verification

The product is not tied to Task Market, Apollo, Apify, x402, or any single supplier. Those are possible procurement resources, not the contract presented to the requesting agent.

Pricing rules

  • Direct supplier costs pass through without markup.
  • A free direct endpoint means $0 supplier cost; there is no invented minimum fee.
  • Managed work can include margin when AgentWork owns fulfillment risk.
  • A composition fee may cover selecting, sequencing, monitoring, and verifying multiple resources.
  • A quote is not completion. Execution and acceptance evidence are required.

Evidence rules

  • A discovered service is not automatically a selectable offer.
  • Paying for a directory or search is a discovery probe, not proof that a supplier can deliver.
  • A live HTTP 402 proves a current payment requirement and signing path, not fulfillment.
  • A successful empty response is NO MATCH, not a reason to invent supply.
  • Blocked, stale, or unverified resources remain UNAVAILABLE.
  • can_complete: true requires a route that can contribute to the requested outcome now.

Current public status

Public MCP access is live at `https://agentwork-outcomes.agentwork-market.workers.dev/mcp`.

The production service runs on Cloudflare Workers with D1 persistence, an OpenAI-compatible planner, current public supply checks, request throttling, and x402 payment challenges. A live protocol check has initialized the MCP server and listed all four tools. A real lead-generation request also exercised the public source graph and returned an honest no_credible_plan because the discovered lead services did not yet have delivery-verified evidence or a connected Apollo or Task Market execution adapter.

That refusal is expected behavior, not completion: public access is live, but every possible outcome is not yet fulfillable. Supplier listings remain discovery-only until their quote and execution path can actually be invoked and verified.

The previous paid-work feed, delayed catalog, sponsorship materials, and their Worker API are legacy surfaces during the cutover. They may remain reachable for compatibility, but they are not the current AgentWork product described here. Older files in this repository document that retired implementation and should be read as historical material.

Feedback and safety

Use a GitHub issue for a broken public link, unclear contract, supplier integration request, or outcome-routing example.

Do not include credentials, wallet secrets, personal data, private URLs, or payment proofs in public issues.

Ask PopNx