Connect Verifier and your agent gets 8 tools, among them changes_since, check_server, find_tools. It answers at https://robinsaige.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 9 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
MCP tool observatory: do registry servers answer, and are their answers true? No key.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: since |
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` grouped Inputs: name |
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, BM25-r Inputs: need, verdict, free_only, open_only, max_latency_ms, nature |
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 wro |
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 m |
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 a Inputs: server, tool, ok, latency_ms, cost_tokens, call_hash |
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 e Inputs: query |
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' = dead/unreac Inputs: name, names |
Every block below points at https://robinsaige.com/mcp. Pick your client and copy.
claude mcp add --transport http verifier https://robinsaige.com/mcp
{
"mcpServers": {
"verifier": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://robinsaige.com/mcp"]
}
}
}{
"mcpServers": {
"verifier": {
"url": "https://robinsaige.com/mcp"
}
}
}{
"servers": {
"verifier": {
"type": "http",
"url": "https://robinsaige.com/mcp"
}
}
}{
"context_servers": {
"verifier": {
"url": "https://robinsaige.com/mcp"
}
}
}{
"mcpServers": {
"verifier": {
"serverUrl": "https://robinsaige.com/mcp"
}
}
}{
"mcpServers": {
"verifier": {
"url": "https://robinsaige.com/mcp"
}
}
}name: Verifier
version: 0.0.1
schema: v1
mcpServers:
- name: Verifier
type: streamable-http
url: https://robinsaige.com/mcp{
"mcpServers": {
"verifier": {
"httpUrl": "https://robinsaige.com/mcp"
}
}
}{
"mcpServers": {
"verifier": {
"type": "http",
"url": "https://robinsaige.com/mcp"
}
}
}{
"mcpServers": {
"verifier": {
"url": "https://robinsaige.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Frobinsaige.com%2Fmcp&type=streamable_http&id=verifier&name=Verifier
It answered our last check on 18 October 2026 in 357 ms. Over 10 checks since 5 September 2026 it answered 9. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by robinsaige.com and served from robinsaige.com, the vendor's own domain: https://robinsaige.com/mcp.
8, as returned by the server's own tools/list on 31 August 2026: changes_since, check_server, find_tools, list_findings, registry_pulse, report_call, resolve_server_name, should_i_use.
It answered our last check on 18 October 2026 in 357 ms. Over 10 checks since 5 September 2026 it answered 9.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://robinsaige.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.robinsaige. Endpoint host: robinsaige.com. ARD identifier: urn:air:com.robinsaige:mcp:verifier.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.