ID MANDAT – Registry for AI Agents
by idmandat · remote · no sign-in to list tools · v0.1.0 · published by GitHub user idmandat
Open registry for AI agents: check who stands behind an agent and what it may do.
3 tools: 2 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http registry https://idmandat.com/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
3 tools
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 1Claude Code: allow
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.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http registry https://idmandat.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__registry__search_registry"
],
"ask": [
"mcp__registry__verify_agent",
"mcp__registry__verify_signature_agent"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as registry. Review it before you use it.
