# criba: who is calling your MCP server (remote · criba.cribalo.com)

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

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `criba.cribalo.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-cribalo-criba/criba.md), [page](https://verifymcp.io/servers/com-cribalo-criba/criba)

## Channel facts

- Endpoint: `https://criba.cribalo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 413 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the criba: who is calling your MCP server server?

criba: who is calling your MCP server is a hosted endpoint at https://criba.cribalo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-cribalo-criba 'https://criba.cribalo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cribalo-criba": {
      "url": "https://criba.cribalo.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cribalo-criba": {
      "type": "http",
      "url": "https://criba.cribalo.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cribalo-criba]
url = "https://criba.cribalo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cribalo-criba": {
      "type": "remote",
      "url": "https://criba.cribalo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cribalo-criba --url 'https://criba.cribalo.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cribalo-criba:
    url: "https://criba.cribalo.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cribalo-criba": {
      "Transport": "http",
      "Url": "https://criba.cribalo.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cribalo-criba -t streamable-http -u 'https://criba.cribalo.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cribalo-criba": {
      "type": "http",
      "url": "https://criba.cribalo.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 70, +5)

- [security improvement] HTTPS: unverified → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_known_bots” rewrote its description, which is the text the model reads

### 2026-11-10 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 64)

First indexed and scored.

## MCP tools (3)

### `identify_client` (~102 tokens)

Identify a client

Who 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.

Input parameters:

- `client_name` (string): MCP clientInfo.name sent in initialize
- `user_agent` (string): HTTP User-Agent header

### `classify_visitor` (~108 tokens)

Classify a visitor

Classify 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 declared identity. All event fields are optional; send what your server parsed. At most 500 events.

Input parameters:

- `events` (array, required): One visitor's requests, in order

### `list_known_bots` (~90 tokens)

List known bots

List 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).

Input parameters:

- `category` (string)
- `protocol` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cribalo-criba/criba#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 64

## Common questions

### What is the criba: who is calling your MCP server server?

criba: who is calling your MCP server is listed in the public MCP registry as com.cribalo/criba. Identify who calls your MCP server or A2A agent: declared identity vs observed behaviour. This page covers its hosted endpoint (https://criba.cribalo.com/mcp).

### Is the criba: who is calling your MCP server server safe to use?

criba: who is calling your MCP server scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the criba: who is calling your MCP server server expose?

criba: who is calling your MCP server exposes 3 tools: identify_client, classify_visitor, list_known_bots. Their descriptions and schemas cost roughly 300 tokens of context every time the server is loaded.

### Does the criba: who is calling your MCP server server require authentication?

No. We connected to criba: who is calling your MCP server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the criba: who is calling your MCP server server still maintained?

criba: who is calling your MCP server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the criba: who is calling your MCP server server?

VerifyMCP ran 13 checks on criba: who is calling your MCP server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://criba.cribalo.com/mcp
- Website: https://criba.cribalo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-cribalo-criba/criba.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cribalo-criba/criba/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-cribalo-criba/criba.json
- HTML version of this page: https://verifymcp.io/servers/com-cribalo-criba/criba
