ID MANDAT — Registry for AI Agents MCP server
io.github.idmandat/registryidmandatstreamable-httpv0.1.1Scanned
Open registry for AI agents: check who stands behind an agent and what it may do.
4 tools: 1 do something that can't be undone, 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ID MANDAT — Registry for AI Agents MCP server can do
The ID MANDAT — Registry for AI Agents MCP server is published by the GitHub account idmandat. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_payment_address) and create or change data (2 tools: verify_agent and verify_signature_agent), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Can't be undone 1Claude Code: ask
check_payment_addressBefore paying a company in crypto, check whether the payment address (XRP Ledger, Ethereum/EVM incl.2 findings
Why it is in this group
- The name "check_payment_address" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...s (XRP Ledger account Domain field plus credential file, or a wallet signature). "declared..."
- Warn
The server marks "check_payment_address" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_payment_address" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Check payment address
Changes things 2Claude Code: ask
verify_agentCheck 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).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Verify agent
verify_signature_agentA website received a request signed with HTTP Message Signatures (Web Bot Auth) and a Signature-Agent header.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Verify signature agent
Only reads 1Show 1 read-only tool
search_registrySearch registered companies by name, industry, city, offer or agent capability (e.g.No findings
Why it is in this group
- The name "search_registry" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search registry
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://idmandat.com/mcp: tools/list returned 4 tools to an anonymous client, including check_payment_address (irreversible), verify_agent (write), verify_signature_agent (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_payment_address" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_payment_address" says "payment": a word that usually means money moves, which cannot be taken back.
The description mentions "credential".
What this check looks forMatched text
description: "...s (XRP Ledger account Domain field plus credential file, or a wallet signature). "declared..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:check_payment_addressCan't be undone
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http registry https://idmandat.com/mcpclaude mcp add --transport http registry https://idmandat.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__registry__search_registry"
],
"ask": [
"mcp__registry__verify_agent",
"mcp__registry__verify_signature_agent",
"mcp__registry__check_payment_address"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as registry. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.idmandat/registry/verify?hash=3e50c54291b79a89fc1eceb839c4e095b8daf45f157b300549f78a31a7cbe661" | jq -e '.changed == false'Pinned hash 3e50c54291b7, from Nov 13, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.idmandat/registry/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.idmandat/registry)Source: MCP Registry · repository. Synced Nov 13, 2026, 07:17 UTC.
ID MANDAT — Registry for AI Agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ID MANDAT — Registry for AI Agents MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ID MANDAT — Registry for AI Agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ID MANDAT — Registry for AI Agents MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: check_payment_address.
What tools does the ID MANDAT — Registry for AI Agents MCP server have?
- 4 tools: 1 irreversible, 2 write, 1 read. check_payment_address, verify_agent, verify_signature_agent and search_registry.
Does the ID MANDAT — Registry for AI Agents MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ID MANDAT — Registry for AI Agents MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ID MANDAT — Registry for AI Agents MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.