Identify who calls your MCP server or A2A agent: declared identity vs observed behaviour.
Connect Remote server
claude mcp add --transport http criba https://criba.cribalo.com/mcp
{
"mcpServers": {
"criba": {
"url": "https://criba.cribalo.com/mcp"
}
}
}
{
"servers": {
"criba": {
"type": "http",
"url": "https://criba.cribalo.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://criba.cribalo.com/mcp
Tools 3 found in our last check
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 th…
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 behavi…
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-11, CC-BY-NC-4.0 (non-commercial use with attribution).
Details
| Endpoint | https://criba.cribalo.com/mcp (Streamable HTTP) |
| First published | 9 Nov 2026 |
| Last updated | 9 Nov 2026 |
| Registry name | com.cribalo/criba |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
