Skip to content
External endpointresponds

verifier

MCP tool observatory: do registry servers answer, and are their answers true? No key.

Endpoint URL
https://robinsaige.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
327 ms
Response record
1 of 1 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.robinsaige/verifier

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
robinsaige-verifier
Version
0.1
Capability keys
tools
Tool names
registry_pulse, should_i_use, find_tools, resolve_server_name, check_server, report_call, changes_since, list_findings
Instructions excerpt

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.

Reported Aug 17, 2026, 05:07 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 327ms