# AgentWork Outcomes (remote · agentwork-outcomes.agentwork-market.workers.dev)

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

- Trust score: 71/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agentwork-outcomes.agentwork-market.workers.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes.md), [page](https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes)

## Channel facts

- Endpoint: `https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 412 tokens (~103/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the AgentWork Outcomes MCP server?

AgentWork Outcomes is a hosted endpoint at https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.mitchellopzero-agentwork-outcomes]
url = "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mitchellopzero-agentwork-outcomes": {
      "type": "remote",
      "url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mitchellopzero-agentwork-outcomes --url 'https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mitchellopzero-agentwork-outcomes:
    url: "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "mitchellopzero-agentwork-outcomes": {
      "Transport": "http",
      "Url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mitchellopzero-agentwork-outcomes -t streamable-http -u 'https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 0)

- [security] Stability: 0.97 → pass

### 2026-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-08 (score 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 88 → 103
- [cosmetic] “request_outcome” reworded the description of “max_spend_micros”
- [cosmetic] “request_outcome” reworded the description of “repeat_of_outcome_id”

### 2026-09-02 (score 0)

- [cosmetic] “request_outcome” added an optional parameter “authority_scopes”

### 2026-08-31 (score 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-30 (score 0)

First indexed and scored.

## MCP tools (4)

### `request_outcome` (~198 tokens)

Request an 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.

Input parameters:

- `authority_scopes` (array): Explicit non-financial authority granted for this outcome. Quote confirmation grants spend only.
- `context` (object): Optional non-secret context needed to plan the outcome.
- `deadline` (string): Optional delivery deadline.
- `done_when` (string): Optional observable completion criteria.
- `max_spend_micros` (integer): Optional maximum retail spend in USDC micros. Zero permits only free routes.
- `outcome` (string): The complete outcome the caller wants.
- `repeat_of_outcome_id` (string): Reuse a verified route where compatible. Supply a fresh outcome, done_when, inputs, and authority; previous values are never inherited.
- `retry_gap_id` (string): Retry a previously recorded routing or scoping gap with fresh supply checks.

### `confirm_outcome` (~40 tokens)

Confirm an outcome quote

Explicitly confirm a previously returned quote and begin configured funding. This may cause a financial action when funding is enabled.

Input parameters:

- `quote_id` (string, required)

### `get_outcome` (~35 tokens)

Get an outcome

Read the current payment, supplier, artifact, verification, and remediation state for an outcome.

Input parameters:

- `outcome_id` (string, required)

### `resume_outcome` (~32 tokens)

Resume an outcome

Idempotently poll or reconcile pending supplier and financial operations for an outcome.

Input parameters:

- `outcome_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 71
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-10: 71
- 2026-10-04: 71
- 2026-10-03: 71
- 2026-10-02: 71
- 2026-10-01: 71

## Common questions

### What is the AgentWork Outcomes MCP server?

AgentWork Outcomes is an MCP server listed in the public MCP registry as io.github.mitchellOpZero/agentwork-outcomes. Buy a finished outcome through services, agents, marketplaces, humans, tools, or swarms. This page covers its hosted endpoint (https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry).

### Is the AgentWork Outcomes MCP server safe to use?

AgentWork Outcomes scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AgentWork Outcomes MCP server expose?

AgentWork Outcomes exposes 4 tools: request_outcome, confirm_outcome, get_outcome, resume_outcome. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.

### Does the AgentWork Outcomes MCP server require authentication?

No. We connected to AgentWork Outcomes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AgentWork Outcomes MCP server still maintained?

AgentWork Outcomes is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the AgentWork Outcomes MCP server?

VerifyMCP ran 11 checks on AgentWork Outcomes, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about AgentWork Outcomes: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry
- Repository: https://github.com/mitchellOpZero/agentwork-api
- Website: https://agentwork-api.mitchellmosesai.chatgpt.site/
- Changelog RSS feed: https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes.xml
- Changelog JSON feed: https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes.json
- HTML version of this page: https://verifymcp.io/servers/mitchellopzero-agentwork-outcomes/agentwork-outcomes