Skip to content
Robin Saige logo

Robin Saige MCP server

Which MCP servers are Robin Saige'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-25

← Back to Robin Saige

Whose server it is
  • Registry namecom.robinsaige/verifierverified in the MCP registry

The registry name sits under robinsaige.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-25
  • Stateanswerschecked 2026-10-25
  • Tools8
  • Server calls itselfrobinsaige-verifier
  • Server version0.1
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: look up a verdict for an MCP server; check whether a server answers before an agent depends on it; have an agent ask whether a named server is usable.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "look up a verdict for an MCP server", the likely first call is should_i_use.
  • For "check whether a server answers before an agent depends on it", the likely first call is should_i_use.
  • For "have an agent ask whether a named server is usable", the likely first call is should_i_use.

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: 3, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer299 ms
  • Space in an agent's context≈ 1,404 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsB · 81 of 100
  • Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 8
  • Not saying whether it only reads or can destroy: 8 of 8

What an agent can do with it

  • can do · look up a verdict for an MCP server
  • can do · check whether a server answers before an agent depends on it
  • can do · have an agent ask whether a named server is usable

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

None of the five warning signs in these definitions.

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 offers8 tools · read 2026-10-25
  • registry_pulse

    Call this FIRST for the state of the MCP tool ecosystem in one shot: how many servers exist, how many actually answer a real handshake, how many are behind a login, the largest costume-farm concentration, AND the Tier-2 truth summary (how…

  • should_i_use

    THE GATE — call this before your agent depends on a tool you don't already trust. Give an exact server registry name and get a one-word verdict — allow / warn / block — with the reason, plus the full rating underneath. 'block' =…

  • find_tools

    Find and RANK the trustworthy tool for a NEED. Describe the task in plain words ('screen a company for sanctions', 'US tariff data', 'vessel tracking') — the search is full-text over tool names AND their stored descriptions (stemmed…

  • resolve_server_name

    Resolve a partial or misspelled server name to its EXACT registry id before calling should_i_use / check_server. Matches a fragment against registry NAMES only (not capabilities — for 'which tool does X' use find_tools). Returns candidate…

  • check_server

    The FULL evidence behind the verdict for ONE server, by exact registry name — call should_i_use first for the one-word decision; call this when you want the whole record. Leads with the verdict (allow/warn/block), then the `rating`…

  • report_call

    AFTER your agent calls a tool, fire-and-forget how it went — success/failure, latency, cost — so the observatory accumulates realized reliability (the one thing outside-in probing can't see: did it actually work for a real call). Anchored…

  • changes_since

    What changed in the tool economy since a date: verdict flips, deaths, revivals, new servers, confirmed drift — the census diff as data. Poll this weekly to keep a local view current without re-crawling.

  • list_findings

    The observatory's ruled findings — each with its claim and its falsification test — plus the public corrections log (what we published, then corrected, never deleted). Call this to cite what has been established, or to see where we were…

How to connect

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

{
  "mcpServers": {
    "verifier": {
      "type": "http",
      "url": "https://robinsaige.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http robinsaige https://robinsaige.com/mcp

Add to CursorAdd to VS Code

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

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.