mcpcost

io.github.TerminallyLazy/sentinel-recovery-services

Sentinel Payment Boundary Tools

Is the Sentinel Payment Boundary Tools MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.

Read-only payment-boundary preflights plus an unsubmitted public quote-request draft tool.

alive probed 2026-11-15 · unchanged since 2026-10-27

3tools
1.3ktokens in Claude Opus 5.5
0.6 %of Claude's 200k window
0.5×the median server
345 msto initialize
10 msto list tools
Bundle
https://github.com/TerminallyLazy/sentinel-recovery-support/releases/download/v0.4.1/sentinel-agent-payment-boundary-v0.4.1.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host
github.com
Reports itself as
sentinel-recovery-mcp-server 0.4.1
Capabilities
resources, tools
Instructions
589 characters
Of a 1M window
0.1 % of a 1M context window
Count
1.3k tokens in Claude Opus 5.5, exact, measured 2026-10-28. With the Claude Code prefix mcp__…__ on each tool name: 1.3k. The o200k_base estimate is 677. Counted again when the tool definitions change. Method.
Repository
https://github.com/TerminallyLazy/sentinel-recovery-support
Website
https://terminallylazy.github.io/sentinel-recovery-support/
Registry
active, updated 2026-07-11 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.85×.

Tool≈ Claude tokenso200k estimateShare of this server
prepare_agent_payment_boundary_quote_request47325638 %
preflight_agent_payment_boundary46625237 %
preflight_x402_v2_payment_required31316925 %

Compare this server with others.

More servers

Other registry entries on github.com, the ones next to this name; all of them.

Servers that mention recovery.

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher