Developer Tools
robinsaige.com
Provides registry analysis, server discovery and verification, and public corrections for MCP servers.
ENDPOINT 1
https://robinsaige.com/mcp
MCP server metadata
- Name
- robinsaige-verifier
- Version
- 0.1
Robin Saige checks the tools AI agents call. registry_pulse = the ecosystem at a glance (does it answer + is the answer true); find_servers = discover a server by name fragment; check_server = one server's full record incl. whether its answers are verified true; 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.
Known tools 4
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 truth summary (how many server answers were re-derived against a public primary source and matched).
Inferred read-onlyfind_serversLook up servers by a fragment of their registry name — use this to DISCOVER the exact name before calling check_server (e.
Inferred read-onlycheck_serverThe full verification record for ONE server, by exact registry name (use find_servers first if you don't have it).
Inferred read-onlylist_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).
Inferred read-onlyCONNECT 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.
robinsaige.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.