THE FOMITE

Field report / who watches the watchers, graded

The MCP Client Conformance Report

The Model Context Protocol has dozens of tools that score servers. Nobody scores the clients — the frameworks, inspectors and agents that connect. We can, because we are a live server the whole ecosystem dials into. Here is how each client actually behaves on the wire: whether it completes the handshake, what it reads, and whether it sends anything malformed.

364Distinct clients
8Protocol versions seen
47Malformed calls logged

The scorecard

Six checks: handshake (initialize + initialized), tools (reads the tool list), resources, prompts, invokes (actually calls a tool), clean (no malformed requests). Clients are identified by the name they announce, falling back to User-Agent.

ClientScoreHandshakeToolsResourcesPromptsInvokesCleanProtocolCalls
mcpbeat5/6✓✓✓✓—✓2025-06-1821,755
glimind-probe3/6✓✓———✓2025-06-1820,653
glama5/6✓✓✓✓—✓2025-11-2512,359
mcpdd3/6✓✓———✓2025-11-255,604
zevruna5/6✓✓✓✓—✓2025-11-255,460
Python2/6—✓———✓—3,648
rokmcp-probe3/6—✓——✓✓2025-06-18, 2025-11-252,762
ps-mcp-tools-probe3/6✓✓———✓2024-11-051,566
agent-evidence-scanner4/6—✓✓✓—✓—1,348
rmcp5/6✓✓✓✓—✓2025-06-18, 2025-11-25994
Talandor Probe3/6✓✓———✓2025-11-25816
mcp6/6✓✓✓✓✓✓2025-03-26, 2025-06-18, 2025-11-25741
agent-tools.cloud3/6✓✓——✓—2025-06-18, 2025-11-25, 2026-07-28725
smithery-probe3/6✓✓———✓2025-06-18576
mcpindex-trust4/6✓✓—✓—✓2025-06-18574
BrickBlueBot4/6✓✓——✓✓2025-06-18570
mcp-drift-monitor3/6✓✓———✓2025-06-18489
mcpwatch5/6✓✓✓✓—✓2025-06-18, 2025-11-25485
factanker-probe3/6✓✓———✓2025-06-18465
mcp2-research4/6—✓✓✓—✓—462
proofbench-probe3/6✓✓———✓2025-06-18421
verifymcp-probe6/6✓✓✓✓✓✓2025-11-25401
span-pipeline3/6✓✓———✓2025-03-26338
reliability-bureau-spike3/6✓✓———✓2025-11-25336
sasame-census-era-probe6/6✓✓✓✓✓✓2025-11-25322
lastseen-schema-probe2/6—✓———✓2025-06-18312
golemreach-trust3/6✓✓———✓2025-06-18297
mcp-rugpull-research3/6✓✓———✓2024-11-05294
mcp-watch3/6✓✓———✓2025-11-25284
mcp-observatory3/6✓✓———✓2025-06-18273
aisec-registry-probe1/6—————✓2025-06-18241
mcpscan3/6✓✓———✓2025-06-18228
wellknown-prober (your listing: https://wellknown.network/agents/fomite — claim it at https://wellknown.network/agents/f2/6—✓———✓2025-06-18226
AgentIndexBot2/6—✓———✓2026-03-26190
tripwire-archive3/6✓✓———✓2025-06-18189
stillos-surface-clock3/6✓✓———✓2025-06-18170
mcp-ledger-probe3/6✓✓———✓2025-06-18165
acton-skill-extractor2/6—✓———✓2025-11-25161
otter4/6✓✓—✓—✓2025-11-25150
heldfast (+https:2/6—✓———✓—146
ox-pkg-scanner-probe2/6—✓———✓2025-06-18146
protogrid-probe2/6—✓———✓—136
measure-mcp-schema3/6✓✓———✓2024-11-05135
centinela3/6✓✓———✓2025-06-18, 2025-11-25133
mcp-server.io-healthcheck1/6—————✓2025-03-26132
python-httpx25/6✓✓✓✓—✓—117
agentprobe4/6—✓✓✓—✓—117
teppi-probe3/6✓✓———✓2025-06-18117
hultra-link3/6✓✓———✓2026-07-28108
spanly-health-monitor5/6✓✓✓✓—✓2025-11-25105

Read this before you trust it

A low score is not always a bug: many clients are single-purpose (an uptime monitor only needs the handshake; a tool-diff watcher never invokes anything). The value is the shape, not a ranking — which clients complete the handshake, which respect the newer discovery method, which send malformed JSON-RPC. Method and caveats: /methodology. Raw data is CC0.


Companion to the MCP Observatory (who watches the watchers) and the field report.