Developer Tools

robinsaige.com

Provides registry analysis, server discovery and verification, and public corrections for MCP servers.

1 endpoint8 known toolsFirst detected August 14, 2026Last detected September 17, 2026

ENDPOINT 1

https://robinsaige.com/mcp

No auth detected

MCP server metadata

Name: robinsaige-verifier
Version: 0.1

Capabilities

tools

Server instructions

Robin Saige rates the tools AI agents call, so you can check one before you depend on it. The core loop: should_i_use(name) = the one-word gate (allow/warn/block) before depending on a tool; find_tools(need) = describe the task in plain words — full-text over tool names AND descriptions, so your words need not appear in a tool's name — each row already carrying its verdict; resolve_server_name(query) = a fuzzy name → exact id; check_server(name) = the full evidence behind a verdict; registry_pulse() = the ecosystem at a glance; list_findings() = ruled findings + public corrections. Method: https://robinsaige.com/method. Grades are strict; auth-walled servers are alive-but-unverifiable, never scored dead or verified; 'true' verdicts require a public primary source; every rating is a dated observation, not a warranty. After you use a tool you may report_call(server, ok, latency_ms, ...) — anchored to our probe; it does not change the verdict yet.

Known tools 8

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 many server answers were re-derived against a public primary source and matched).

Inferred read-only

should_i_use

THE GATE — call this before your agent depends on a tool you don't already trust.

Inferred read-only

find_tools

Find and RANK the trustworthy tool for a NEED.

Inferred read-only

resolve_server_name

Resolve a partial or misspelled server name to its EXACT registry id before calling should_i_use / check_server.

Inferred read-only

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.

Inferred read-only

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).

Inferred read-only

changes_since

What changed in the tool economy since a date: verdict flips, deaths, revivals, new servers, confirmed drift — the census diff as data.

Inferred read-only

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).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.robinsaige-verifier]
url = "https://robinsaige.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: robinsaige-verifier
Remote MCP URL: https://robinsaige.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "robinsaige-verifier": {
      "url": "https://robinsaige.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "robinsaige-verifier",
  "transport": "streamable-http",
  "url": "https://robinsaige.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for robinsaige.com was fetched 2026-08-23T17:21:52.507Z and is being refreshed.

Trust status Neutral

robinsaige.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.