mcp-registry/com.robinsaige/verifier · v0.1
As of 2026-10-25 17:30 UTC, the Robinsaige Verifier MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 61 outages in 90 days, with a median recovery of 5 minutes.
MCP tool observatory: do registry servers answer, and are their answers true? No key.
Claude Code
claude mcp add --transport http robinsaige-verifier-mcp-server https://robinsaige.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"robinsaige-verifier-mcp-server": {
"type": "http",
"url": "https://robinsaige.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
5 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.robinsaige%2Fverifier/fixes
{
"name": "check_server",
"description": "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 as REACH (answers, latency vs population, protocol, auth), USE (tool count vs population, capability breadth, harness readiness) and TRUST (costume-farm?, duplicate inventory?, verifiability grade, drift / rug-pull, and where checkable whether its ANSWERS are ",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "exact registry name, e.g. io.github.you/your-mcp"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_tools",
"description": "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-ranked), so your words need not appear in any tool's name. Servers come best-rated first, and EACH ROW carries its verdict (allow/warn/block), cluster, distinctiveness and the matching tool names, so you can pick without a second call. Alive, non-costume, curre",
"inputSchema": {
"type": "object",
"required": [
"need"
],
"properties": {
"need": {
"type": "string",
"description": "what the tool should do, in plain words"
},
"nature": {
"enum": [
"retrieval-public",
"retrieval-private",
"action",
"generative",
"predictive",
"computational",
"orchestration"
],
"type": "string",
"description": "only servers whose dominant tool nature is this (see robinsaige.com/verification)"
},
"verdict": {
"enum": [
"allow",
"warn",
"block"
],
"type": "string",
"description": "only servers with this verdict"
},
"free_only": {
"type": "boolean",
"description": "exclude servers that demand payment at the handshake"
},
"open_only": {
"type": "boolean",
"description": "exclude auth-walled servers"
},
"max_latency_ms": {
"type": "integer",
"description": "only servers at or under this probe latency"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_findings",
"description": "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 wrong. No arguments.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.robinsaige/verifier"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.robinsaige/verifier"}) over MCP.
find_tools ~363 tokensreport_call ~227 tokensshould_i_use ~227 tokenscheck_server ~194 tokensresolve_server_name ~144 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.robinsaige%2Fverifier?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.robinsaige%2Fverifier?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.robinsaige%2Fverifier.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.robinsaige%2Fverifier.svg :target: https://glimind.com/server/mcp-registry%2Fcom.robinsaige%2Fverifier?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:39e18b8e50d7dd1e…, first seen 2026-10-17, included at leaf 14946 of 67,505. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 17:30 UTC, the Robinsaige Verifier MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 61 outages in 90 days, with a median recovery of 5 minutes.
Robinsaige Verifier MCP server advertises 8 tools, including changes_since, check_server, find_tools, list_findings, registry_pulse.
Point your MCP client at this streamable-http endpoint: https://robinsaige.com/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.