MCP Radar
Servidor MCP

verifier

com.robinsaige/verifier
Infraestructura MCP y de agentes Seguridad Público y accesible MCP 2026-07-28

Qué hace este MCP

Monitors and evaluates MCP servers for availability, reliability, capability quality, trust, drift, and tool selection.

Capacidades

Herramientas

8 herramientas
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.
Esquema de entrada 
{'type': 'object', 'properties': {'since': {'type': 'string', 'description': 'YYYY-MM-DD; omit for the whole latest diff'}}}
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 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 true vs a public primary), a cluster tag, a distinctiveness score, and an explicit not_claimed block. Argument: name.
Esquema de entrada 
{'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': 'exact registry name, e.g. io.github.you/your-mcp'}}}
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-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, current-protocol servers rank on top; dead / costume-farm / walled ones sink. Argument: need.
Esquema de entrada 
{'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'}}}
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 wrong. No arguments.
Esquema de entrada 
{'type': 'object', 'properties': {}}
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). Every number is re-derivable; grades observed/reported/derived. No arguments.
Esquema de entrada 
{'type': 'object', 'properties': {}}
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 against our own probe: a 'worked' report on a server we saw dead is discarded. Does NOT change the current rating yet (probing stays load-bearing) — this is accumulate-ahead-of-demand. Args: server (required), tool, ok, latency_ms, cost_tokens, call_hash (a hash binding the report to a real call).
Esquema de entrada 
{'type': 'object', 'required': ['server'], 'properties': {'ok': {'type': 'boolean'}, 'tool': {'type': 'string'}, 'server': {'type': 'string', 'description': 'exact registry name'}, 'call_hash': {'type': 'string'}, 'latency_ms': {'type': 'integer'}, 'cost_tokens': {'type': 'integer'}}}
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 exact names with each one's latest liveness outcome. Empty query rejected.
Esquema de entrada 
{'type': 'object', 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': "a fragment of a registry name, e.g. 'tariff'"}}}
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/unreachable/costume-farm-shaped, don't depend on it; 'warn' = usable but look first; 'allow' = safe to depend on. If you have a NEED not a name, use find_tools; if you have a fuzzy name, use resolve_server_name. Argument: name, e.g. 'com.trimtabist/us-tariff-ledger'.
Esquema de entrada 
{'type': 'object', 'properties': {'name': {'type': 'string', 'description': 'exact registry name, e.g. io.github.you/your-mcp'}, 'names': {'type': 'array', 'items': {'type': 'string'}, 'maxItems': 20, 'description': 'batch form: vet a whole config at session start (max 20)'}}}
Historial

Cambios recientes en herramientas

Añadido
list_findings
17 de September de 2026 a las 12:37
Añadido
changes_since
17 de September de 2026 a las 12:37
Añadido
report_call
17 de September de 2026 a las 12:37
Añadido
check_server
17 de September de 2026 a las 12:37
Añadido
resolve_server_name
17 de September de 2026 a las 12:37
Añadido
find_tools
17 de September de 2026 a las 12:37
Añadido
should_i_use
17 de September de 2026 a las 12:37
Añadido
registry_pulse
17 de September de 2026 a las 12:37
Descubrir

Servidores MCP similares

AIMEAT

io.aimeat/aimeat

Provides a self-hosted agent operating system with agent work delegation, access controls, federation, hooks, SSO, security admin…

hyperion

com.thetempleofdoom.hyperion/hyperion

Acts as a paid MCP tool marketplace and utility gateway with server discovery, HTTP and JavaScript tools, research, data conversi…

Japan Public Ledgers MCP

com.mcp-revenue-empire/japan-public-ledgers

Provides agent identity, memory, audit, trust, proxy, temporary email, webhook, CAPTCHA, and alerting capabilities alongside publ…

PHION Agent Trust Infrastructure

systems.phion/evidence-engine

Provides agent trust, policy, provenance, evidence, delegation, telemetry, and transaction-control services for MCP and agent wor…

Swamp

world.swampai/swamp

Coordinates security agents through scoped bug-bounty programs, target claims, vulnerability submissions, peer review, shared fin…

AgentBIT

app.agentbit/mcp

Routes pay-per-call tools over x402 on Base, covering discovery, data conversion, company research, counterparty screening, domai…

SaSame MCP Observatory + Gold Rush Town

online.sasame/research

Audits and profiles MCP servers, provides ecosystem analytics, trust and claim records, and non-custodial transaction or escrow a…

ThinkNEO Control Plane

ai.thinkneo/control-plane

Provides an enterprise AI control plane for governance, guardrails, spend tracking, compliance, and model or tool routing.