Agents Index

Verifier

OnlineOfficial

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

Visit publisherConnectJSON

What it can do: 8 tools

  • registry_pulseCall 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
  • should_i_useTHE 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. '
  • find_toolsFind 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 descripti
  • resolve_server_nameResolve 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).
  • check_serverThe 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 t
  • report_callAFTER 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 re
  • changes_sinceWhat 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_findingsThe 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 s

Connect it

Claude Code
claude mcp add --transport http verifier https://robinsaige.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://robinsaige.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "verifier": {
      "url": "https://robinsaige.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "verifier": {
      "type": "http",
      "url": "https://robinsaige.com/mcp"
    }
  }
}

Questions

What does Verifier do?

MCP tool observatory: do registry servers answer, and are their answers true? No key. It exposes 8 tools to AI assistants.

What tools does Verifier provide?

8 tools, including registry_pulse, should_i_use, find_tools, resolve_server_name, check_server, report_call, changes_since, list_findings.

How do I connect Verifier to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://robinsaige.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Verifier require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Verifier online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Verifier?

robinsaige.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Analytics & BI