criba: who is calling your MCP server

com.cribalo/criba · v0.1.0 · agents-and-memory

criba: who is calling your MCP server is healthy: it completed an MCP handshake in 858 ms and exposes 3 tools.

Identify who calls your MCP server or A2A agent: declared identity vs observed behaviour.

Endpoint: https://criba.cribalo.com/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count3
Latency858 ms
Last checked (UTC)2026-11-09T10:15:20.214Z

Health history

Checked (UTC)StatusLatencyError
2026-11-09T10:15:20.214ZHealthy858

Tools (3)

identify_clientWho a User-Agent and/or an MCP clientInfo.name claims to be, matched against criba's catalog of known MCP indexers, verifiers, A2A directories, AI crawlers, scanners and HTTP libraries. This is a declaration, not proof: use classify_visitor for behaviour. Pass at least one of the two.
classify_visitorClassify one visitor from its requests to your MCP server, A2A agent or website. Returns the declared identity, the observed behaviour class (acts-on-results, agent-tool-use, agent-message, probe, indexer, web-scanner, web), the signals and reasons, and mismatch=true when behaviour contradicts the d
list_known_botsList criba's catalog of known agent-ecosystem bots, optionally filtered by category or protocol. Each entry has its id, name, category, URL, matching rules and what it was seen doing. Catalog 2026-11-08, CC-BY-NC-4.0 (non-commercial use with attribution).