# ID MANDAT – Registry for AI Agents (remote · idmandat.com)

Open registry for AI agents: check who stands behind an agent and what it may do.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `idmandat.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/idmandat-registry/idmandat.md), [page](https://verifymcp.io/servers/idmandat-registry/idmandat)

## Channel facts

- Endpoint: `https://idmandat.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-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 815 tokens (~203/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ID MANDAT – Registry for AI Agents MCP server?

ID MANDAT – Registry for AI Agents is a hosted endpoint at https://idmandat.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 idmandat-registry 'https://idmandat.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "idmandat-registry": {
      "url": "https://idmandat.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.idmandat-registry]
url = "https://idmandat.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  idmandat-registry:
    url: "https://idmandat.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "idmandat-registry": {
      "type": "http",
      "url": "https://idmandat.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-05 (score 80, +1)

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

### 2026-11-03 (score 79, +1)

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

### 2026-11-01 (score 78, +1)

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

### 2026-10-29 (score 77, +1)

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

### 2026-10-27 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-26 (score 75, 0)

- [functional regression] Schema quality: 570 → 803
- [functional] New tool “check_payment_address”

### 2026-10-25 (score 75, +1)

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

### 2026-10-23 (score 74, +1)

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

## MCP tools (4)

### `verify_agent` (~103 tokens)

Verify a company's AI agents

Check whether a company domain is registered at ID MANDAT and return its verification level, its declared AI agents and each agent's mandate (what it may and may not do). Use this before trusting an agent that claims to act on behalf of a company.

Input parameters:

- `agent` (string): Optional: name of the agent to check, e.g. "Captain".
- `domain` (string, required): Company domain, e.g. "example.com" (URLs are accepted too).

### `verify_signature_agent` (~139 tokens)

Who is behind a signed agent request?

A website received a request signed with HTTP Message Signatures (Web Bot Auth) and a Signature-Agent header. Pass the https address from that header (or the whole header value). Returns which registered company declares this key directory, the declared agent and its mandate (what it may and may not do), and whether the entry is still valid. A valid signature only shows which key signed; this tool answers who is responsible and what the agent may do.

Input parameters:

- `signature_agent` (string, required): Address from the Signature-Agent header, e.g. "https://signer.example.com", or the header value such as sig="https://signer.example.com".

### `check_payment_address` (~233 tokens)

Does this payment address belong to this domain?

Before paying a company in crypto, check whether the payment address (XRP Ledger, Ethereum/EVM incl. BNB Chain and Base, Solana) belongs to the company domain. Result "proven": the operator of the domain controls the address (XRP Ledger account Domain field plus credential file, or a wallet signature). "declared": the operator lists the address but it is not proven. "different_from_proven": another address is proven for this domain, treat as a warning. "not_declared", "domain_not_registered" and "invalid_address" mean nothing confirms it: do not pay without confirming through another channel. This confirms who controls an address, not that a company is trustworthy or that a payment is safe.

Input parameters:

- `address` (string, required): The payment address you were given.
- `chain` (string): Optional: xrp, ethereum, bnb, base, polygon, arbitrum, optimism, avalanche, evm or solana. Detected from the address format if omitted.
- `domain` (string, required): Company domain you intend to pay, e.g. "example.com".

### `search_registry` (~124 tokens)

Search the ID MANDAT registry

Search registered companies by name, industry, city, offer or agent capability (e.g. "book_appointment"), optionally filtered by country. Returns up to 20 entries, best verified first.

Input parameters:

- `country` (string): Optional ISO 3166-1 alpha-2 country code, e.g. "DE", "AT", "CH".
- `query` (string): Free text, e.g. "art gallery", "Osnabrück", "book_appointment".
- `with_agent` (boolean): Optional: only companies that declare at least one AI agent.

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 71

## Common questions

### What is the ID MANDAT – Registry for AI Agents MCP server?

ID MANDAT – Registry for AI Agents is an MCP server listed in the public MCP registry as io.github.idmandat/registry. Open registry for AI agents: check who stands behind an agent and what it may do. This page covers its hosted endpoint (https://idmandat.com/mcp).

### Is the ID MANDAT – Registry for AI Agents MCP server safe to use?

ID MANDAT – Registry for AI Agents scores 80 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 ID MANDAT – Registry for AI Agents MCP server expose?

ID MANDAT – Registry for AI Agents exposes 4 tools: verify_agent, verify_signature_agent, check_payment_address, search_registry. Their descriptions and schemas cost roughly 599 tokens of context every time the server is loaded.

### Does the ID MANDAT – Registry for AI Agents MCP server require authentication?

No. We connected to ID MANDAT – Registry for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ID MANDAT – Registry for AI Agents MCP server still maintained?

ID MANDAT – Registry for AI Agents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://idmandat.com/mcp
- Repository: https://github.com/idmandat/check
- Website: https://idmandat.com/
- Changelog RSS feed: https://verifymcp.io/servers/idmandat-registry/idmandat.xml
- Changelog JSON feed: https://verifymcp.io/servers/idmandat-registry/idmandat.json
- HTML version of this page: https://verifymcp.io/servers/idmandat-registry/idmandat