# The Outcome Layer (remote · theoutcomelayer.com)

AI-vs-consultant cost estimates, adjustable task proposals and opt-in handoff to The Outcome Layer.

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

## Components

- remote · `theoutcomelayer.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-theoutcomelayer-outcome-layer/api-mcp.md), [page](https://verifymcp.io/servers/com-theoutcomelayer-outcome-layer/api-mcp)

## Channel facts

- Endpoint: `https://theoutcomelayer.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1435 tokens (~102/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the The Outcome Layer MCP server?

The Outcome Layer is a hosted endpoint at https://theoutcomelayer.com/api/mcp, 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 com-theoutcomelayer-outcome-layer 'https://theoutcomelayer.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-theoutcomelayer-outcome-layer": {
      "url": "https://theoutcomelayer.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-theoutcomelayer-outcome-layer": {
      "type": "http",
      "url": "https://theoutcomelayer.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-theoutcomelayer-outcome-layer]
url = "https://theoutcomelayer.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-theoutcomelayer-outcome-layer": {
      "type": "remote",
      "url": "https://theoutcomelayer.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-theoutcomelayer-outcome-layer --url 'https://theoutcomelayer.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-theoutcomelayer-outcome-layer:
    url: "https://theoutcomelayer.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-theoutcomelayer-outcome-layer": {
      "Transport": "http",
      "Url": "https://theoutcomelayer.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-theoutcomelayer-outcome-layer -t streamable-http -u 'https://theoutcomelayer.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-theoutcomelayer-outcome-layer": {
      "type": "http",
      "url": "https://theoutcomelayer.com/api/mcp"
    }
  }
}
```

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-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 70)

First indexed and scored.

## MCP tools (14)

### `get_company_facts` (~31 tokens)

Canonical read-only facts about The Outcome Layer (entity, positioning, illustrative scenario, disambiguation).

### `get_offer` (~21 tokens)

Free entry offer (Free First Task): price 0 SEK.

### `get_pricing_model` (~24 tokens)

How The Outcome Layer prices work (ROI-first, fixed fee packages).

### `list_answer_pages` (~21 tokens)

List citable English answer pages under /answers/<slug>.

### `get_answer` (~43 tokens)

Full text for one answer page by slug.

Input parameters:

- `slug` (string, required): Answer slug, e.g. is-ai-automation-cheaper-than-hiring-a-consultant

### `how_to_start` (~22 tokens)

How a buyer or agent should start engaging with The Outcome Layer.

### `estimate_automation` (~69 tokens)

Deterministic illustrative estimate: workflow pattern, model tier, consultant vs fixed monthly range, running cost. Not a quote.

Input parameters:

- `consultant_hours_per_month` (number)
- `hourly_rate_sek` (number)
- `language` (string)
- `task_description` (string, required)

### `start_proposal` (~98 tokens)

Begin interactive proposal intake from a task description. Returns clarifying questions (volume, systems, frequency, sign-off). Stateless.

Input parameters:

- `consultant_hours_per_month` (number)
- `frequency` (string)
- `hourly_rate_sek` (number)
- `language` (string)
- `sign_off` (string)
- `systems` (string)
- `task_description` (string, required)
- `volume` (string)

### `ask_clarifying_questions` (~47 tokens)

Merge answers to clarifying questions into intake and return remaining questions. Pass the intake object from start_proposal.

Input parameters:

- `answers` (object)
- `intake` (object, required)

### `get_proposal` (~44 tokens)

Build a concrete indicative proposal (steps, automation split, model tier, pricing ranges, Free First Task CTA). Stateless — pass intake JSON.

Input parameters:

- `intake` (object, required)

### `adjust_proposal` (~60 tokens)

Adjust an existing proposal (review level, model tier, volume, budget cap, disable steps). Returns feasibility, price/risk notes, optional alternative. Stateless — pass full proposal JSON.

Input parameters:

- `adjustments` (object)
- `proposal` (object, required)

### `request_free_first_task` (~273 tokens)

Submit a Free First Task lead to The Outcome Layer (same as the website form).

REQUIRED BEFORE CALLING:
1\) Ask the user if they want TOL to review/build this — get explicit consent.
2\) Collect real name, work email, and company from the user — never invent or guess contact data.
3\) Include task_summary and/or proposal JSON from prior tools.

Set consent=true only after the user agrees. Use test=true for dry runs (no customer email; lead marked TEST).

Input parameters:

- `company` (string, required): User's company (must come from the user)
- `consent` (boolean, required): true only after the user explicitly agreed to contact TOL
- `email` (string, required): User's work email (must come from the user)
- `mcp_client` (string): Name of the MCP client, e.g. cursor, claude-desktop
- `name` (string, required): User's real name (must come from the user)
- `phone` (string)
- `proposal` (object): Proposal JSON from get_proposal
- `ref` (string): Attribution ref, e.g. chatgpt_handoff
- `task_summary` (string): Free-text task summary
- `test` (boolean): If true, lead is TEST — no confirmation email to the user

### `send_to_tol` (~279 tokens)

Alias for request_free_first_task. Submit a Free First Task lead to The Outcome Layer (same as the website form).

REQUIRED BEFORE CALLING:
1\) Ask the user if they want TOL to review/build this — get explicit consent.
2\) Collect real name, work email, and company from the user — never invent or guess contact data.
3\) Include task_summary and/or proposal JSON from prior tools.

Set consent=true only after the user agrees. Use test=true for dry runs (no customer email; lead marked TEST).

Input parameters:

- `company` (string, required): User's company (must come from the user)
- `consent` (boolean, required): true only after the user explicitly agreed to contact TOL
- `email` (string, required): User's work email (must come from the user)
- `mcp_client` (string): Name of the MCP client, e.g. cursor, claude-desktop
- `name` (string, required): User's real name (must come from the user)
- `phone` (string)
- `proposal` (object): Proposal JSON from get_proposal
- `ref` (string): Attribution ref, e.g. chatgpt_handoff
- `task_summary` (string): Free-text task summary
- `test` (boolean): If true, lead is TEST — no confirmation email to the user

### `build_handoff_link` (~72 tokens)

Build a shareable URL that opens a one-step Free First Task handoff page with proposal/summary prefilled (no PII). For chats without MCP submit.

Input parameters:

- `language` (string)
- `proposal` (object)
- `ref` (string)
- `task_summary` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-theoutcomelayer-outcome-layer/api-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70

## Common questions

### What is the The Outcome Layer MCP server?

The Outcome Layer is an MCP server listed in the public MCP registry as com.theoutcomelayer/outcome-layer. AI-vs-consultant cost estimates, adjustable task proposals and opt-in handoff to The Outcome Layer. This page covers its hosted endpoint (https://theoutcomelayer.com/api/mcp).

### Is the The Outcome Layer MCP server safe to use?

The Outcome Layer scores 74 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 The Outcome Layer MCP server expose?

The Outcome Layer exposes 14 tools: get_company_facts, get_offer, get_pricing_model, list_answer_pages, get_answer, and 9 more. Their descriptions and schemas cost roughly 1,104 tokens of context every time the server is loaded.

### Does the The Outcome Layer MCP server require authentication?

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

### Is the The Outcome Layer MCP server still maintained?

The Outcome Layer 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.

## Links

- Remote endpoint: https://theoutcomelayer.com/api/mcp
- Website: https://theoutcomelayer.com/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-theoutcomelayer-outcome-layer/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-theoutcomelayer-outcome-layer/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-theoutcomelayer-outcome-layer/api-mcp