Tool-result size governor for MCP Server

by textforagents Your server? Claim it

answering

Tool-result size governor for MCP is answering right now. Last checked 6 min ago. It exposes 3 tools.

Per-route output budgets for MCP: windowing, spill artifacts, signed omission receipts.

Uptime history 4 days of history · worst day 96%

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

320 ms

Response time

average over 24h

open, no key

Access

streamable-http

Tool-result size governor for MCP does not always answer

Over the last week it answered 99.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tool-result-size-governor --transport http https://textforagents.com/products/tool-result-size-governor/mcp

Settings → Connectors → Add custom connector, then paste this address

https://textforagents.com/products/tool-result-size-governor/mcp

~/.codex/config.toml

[mcp_servers.tool-result-size-governor]
url = "https://textforagents.com/products/tool-result-size-governor/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tool-result-size-governor": {
      "url": "https://textforagents.com/products/tool-result-size-governor/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "tool-result-size-governor": {
      "type": "http",
      "url": "https://textforagents.com/products/tool-result-size-governor/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

shape

shape_result

Shape one tool result under your per-route budgets -> shaped window + signed omission receipt. Trial: first 100 shaped results free once per operator; then $0.001/result (X-PAYMENT header) or a plan.

slice

fetch_slice

Re-fetch a narrower slice of your own spilled payload, byte-exact, checksum re-verified. unknown_artifact is a clean error.

verify

verify_receipt

Verify a signed omission receipt.

Endpoints

URL	Transport	State	Latency	Checked
https://textforagents.com/products/tool-result-size-governor/mcp	streamable-http	answering	319 ms	6 min ago

Alternatives to Tool-result size governor for MCP

same job, measured the same way

tab

by paidwithtab

Agents pay per call over HTTP 402: 8,600+ API routes, owner-signed budgets, signed receipts.

34 installs/wk local only

Routavo

by routavo

Any API, four tools: discover, call with routing and signed receipts, verify, dispute.

4 tools answering

Namespace guard for merged toolboxes

by textforagents

Pre-connection collision audit for merged MCP toolboxes, trust-graded, with signed routing receipts.

4 tools answering

Agoragentic Agent OS MCP

by rhein1

Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.

546 installs/wk 17 tools answering

Aga MCP Server

by attestedintelligence

Verifiable decision records for AI agents: signed receipts for calls to its own governed tools.

70 installs/wk local only

Fetchmux

by krutftw

Self-hosted retrieval router for AI agents: budgets, provider routing, route receipts.

12 installs/wk local only

Regent Protocol

by regentprotocol

Spending control for AI agents: approved budgets, a decision before each payment, signed receipts.

answering

Hatun MCP - Governed Agent Gateway

by szl-holdings

Governed MCP gateway: policy gate on every tool call, hash-chained DSSE receipt on every result.

local only

Tool-result size governor for MCP — questions

Answers built from our own checks of this server.

What can Tool-result size governor for MCP do?

It exposes 3 tools, read directly from the server on our last check. Among them: fetch_slice, shape_result, verify_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Tool-result size governor for MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 320 ms. The bar chart above shows every period we have measured.

How do I connect Tool-result size governor for MCP?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Tool-result size governor for MCP need an API key?

No. Tool-result size governor for MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Tool-result size governor for MCP?

It answers our handshake in 320 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.