Robin Saige we check the tools AI agents call

registry mcp

com.remote-mcp/registry-mcp

An MCP server that serves informtaion from the official MCP registry

— the operator's own registry description reported

Publisher com.remote-mcp · first seen 2026-08-12 · endpoint https://registry-mcp.remote-mcp.com

allow
verdict
stale-thin-slow-solo
cluster
ok_tools
answers
2
tools served

Dependency rating derived

allow — stale-thin-slow-solo — safe to depend on

Cluster stale-thin-slow-solo · distinctiveness 0.609 (unusual). 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
latency10596 ms
vs populationslow
protocolbehind
authopen
Use — can it use it?
tools2
vs populationlow
capabilities1
harnessC
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_9d497a637907f179a944949f · 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.

Tools last seen

GetMCPServer ListMCPServers

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 C — callable but under-described.

legibility checktools passingok
name is clear & specific2/2
has a description0/20/2
description is substantive0/20/2
parameters are typed2/2
parameters are described2/2

2 of 2 tools graded · 2 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-03-26
protocol version
session model
1.0.0
server version MCP Registry Client

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 (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:26Zok_tools200105962025-03-26
2026-08-12T05:33:41Zok_tools200105512025-03-26

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/com.remote-mcp/registry-mcp.svg)](https://robinsaige.com/s/com.remote-mcp/registry-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