INDIVIDUAL MCP TOOL
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).
LIVE ENDPOINT
https://robinsaige.com/mcp
Connect to this endpoint to inspect the live schema for list_findings and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
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).find_servers— Look up servers by a fragment of their registry name — use this to DISCOVER the exact name before calling check_server (e.check_server— The full verification record for ONE server, by exact registry name (use find_servers first if you don't have it).