mcpcost

com.robinsaige/verifier

robinsaige-verifier

MCP tool observatory: do registry servers answer, and are their answers true? No key.

alive probed 2026-10-05 · HTTP 200

8tools
2.1ktokens in Claude Opus 5.5
2.2ktokens in Claude Code
1.1 %of a 200k context window
1.3ko200k_base estimate
260 msto initialize
119 msto list tools
Endpoint
https://robinsaige.com/mcp (streamable-http)
Host
robinsaige.com
Protocol
2025-06-18
Reports itself as
robinsaige-verifier 0.1
Capabilities
tools
Instructions
958 characters
Claude count
Claude Opus 5.5, measured 2026-10-05. Counted again when the tool definitions change. Method.
Website
https://robinsaige.com
Registry
active, updated 2026-08-13 · registry entry
Reachable
6 of the last 6 probes

Most expensive tools

ToolTokens (o200k)Share of this server
find_tools30724 %
should_i_use20816 %
report_call19916 %
check_server18214 %
resolve_server_name1099 %

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-10-05 13:38alive260 ms82.1k1.3k
2026-10-05 00:20alive206 ms81.3k
2026-10-04 09:58alive1.0 s81.3k
2026-10-04 07:51alive707 ms81.3k
2026-10-03 20:31alive840 ms81.3k
2026-10-03 17:49alive847 ms81.3k

Badge and feed

mcpcost: alive

[![mcpcost](https://mcpcost.ulehla.dev/badge/com.robinsaige/verifier.svg)](https://mcpcost.ulehla.dev/s/com.robinsaige/verifier)

An entry for every probe that changed the result, the tool count or the token cost: Atom feed. Add it to a feed reader or a Slack RSS app to hear when the server stops answering or its tool set grows.