Skip to content
The Outcome Layer logo

The Outcome Layer MCP server

Which MCP servers are The Outcome Layer's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to The Outcome Layer

Whose server it is
  • Registry namecom.theoutcomelayer/outcome-layerverified in the MCP registry

The registry name sits under theoutcomelayer.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools14
  • Server calls itselfthe-outcome-layer-public
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 411 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Keep approval on for send_to_tol: they delete, send or pay without saying so.
  • send_to_tol change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 8 of 14 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer577 ms
  • Space in an agent's context≈ 1,970 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results0 of 14 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 8 of 14

What an agent can do with it

  • not sure · Produce recurring management and weekly ops reports
  • cannot · Reconcile invoices and accounts against source records
  • not sure · Triage and route incoming customer service tickets

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that delete, send or pay, marked as not destructive: send_to_tol
  • Tools that change data, on a server that answers without a sign-in: send_to_tol

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-29
  • get_company_facts

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

  • get_offer

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

  • get_pricing_model

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

  • list_answer_pages

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

  • get_answer

    Full text for one answer page by slug.

  • how_to_start

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

  • estimate_automation

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

  • start_proposal

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

  • ask_clarifying_questions

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

  • get_proposal

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

  • adjust_proposal

    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.

  • 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…

  • send_to_tol

    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…

  • build_handoff_link

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http theoutcomelayer https://theoutcomelayer.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://theoutcomelayer.com/api/mcp as a custom connector in the settings.

OpenAPI spec

3 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.