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.
Available components
Last scanned (2 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 26 Oct 26 0
- Schema quality: 570 → 803 ▼ functional
- New tool “check_payment_address” functional
- 25 Oct 26 +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.
- 23 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://idmandat.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=idmandat.com | CN=YE2,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6ef80c4564263b0b7ece1dc5e13e8970d05 |
| SANs: idmandat.com, www.idmandat.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of idmandat.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| idmandat.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://idmandat.com/mcp | Verified | 200 | |
| http (plaintext) | http://idmandat.com/mcp | HTTPS enforced | 301 | https://idmandat.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_payment_address Does this payment address belong to this domain? ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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 | yes | Company domain you intend to pay, e.g. "example.com". |
No output schema declared.
No examples provided.
search_registry Search the ID MANDAT registry ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
verify_agent Verify a company's AI agents ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional: name of the agent to check, e.g. "Captain". |
| domain | string | yes | Company domain, e.g. "example.com" (URLs are accepted too). |
No output schema declared.
No examples provided.
verify_signature_agent Who is behind a signed agent request? ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| signature_agent | string | yes | Address from the Signature-Agent header, e.g. "https://signer.example.com", or the header value such as sig="https://signer.example.com". |
No output schema declared.
No examples provided.
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.
remote · idmandat.com
claude mcp add --transport http idmandat-registry 'https://idmandat.com/mcp'
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.