Robin Saige we check the tools AI agents call

Reqistry

dev.reqistry/mcp

Discover, compare, and monitor 1,400+ APIs directly from your AI coding agent.

— the operator's own registry description reported

Publisher dev.reqistry · first seen 2026-08-12 · endpoint https://mcp.reqistry.dev/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
13
tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.125 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency240 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools13
vs populationmid
capabilities1
harnessB
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_769dcf92fd4a347173d6a9ce · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. This server's 13 tools, classified, with what checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public6serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified3not yet classifiable from its textTier-1 only until its tools describe themselves

Tools last seen

assess_api_production_safety check_health compare_apis get_alternatives get_api get_api_trust_score get_category_apis get_change_feed get_use_case_collections list_categories recommend_apis submit_api suggest_alternatives

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility checktools passingok
name is clear & specific13/13
has a description13/13
description is substantive13/13
parameters are typed13/13
parameters are described2/132/13

13 of 13 tools graded · 13 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
2.0.0
server version dev.reqistry/mcp

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-08-14inventorytools 7 → 13
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:45Zok_tools2002402025-06-18
2026-08-12T05:33:58Zok_tools2002542025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/dev.reqistry/mcp.svg)](https://robinsaige.com/s/dev.reqistry/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview