LIVE PROTOCOL EVIDENCE / NO SYNTHETIC ACTIVITY
MCP is knocking.
Is anyone calling?
A live view of initialize handshakes, named tool requests and provider-verified clients observed by H/M endpoints. A handshake is discovery evidence, not an AI user.
Window
Loading observed traffic...
01 / SIGNAL LADDER
Discovery is not adoption
Each stage requires stronger evidence. Counts never move upward by assumption.
02 / TIME
Observed requests by day
Initialize volume and named tools/call requests. Internal QA is excluded.
HandshakesNamed tool requests
03 / ENDPOINTS
Where machines arrived
| Endpoint | Init | Tools | Last seen |
|---|
04 / CLIENT CLASS
What self-declared clients resemble
05 / NEGOTIATION
Protocol and capability observations
Forward-only aggregate telemetry. Custom capability names and raw initialize payloads are discarded.
Waiting for the next post-release initialize handshake.
| Protocol | Declared capabilities | Client class | Init |
|---|
EVIDENCE BOUNDARY
What these numbers do not prove
- Initialize does not prove that an AI model used the server.
- clientInfo is self-declared and may be a registry, monitor or probe.
- A tools/call request does not prove a successful or useful outcome.
- This is H/M traffic, not a census of the MCP ecosystem.
SHA-256
--FROM DISCOVERY TO EVIDENCE
Give an AI one useful action
Audit a public site for crawler policy, retrieval, action and trust surfaces. The free result includes a checksum share receipt; the URL and response bodies are not retained.
The paid endpoint requires explicit operator authorization for the current Base mainnet x402 payment. No automatic purchase.