nAIm — API Registry for Agents MCP server
io.github.AIAll-TARS/naimAIAll-TARSstreamable-httpv1.1.0Scanned
316 AI APIs searchable by shared failure domain, freshness and agent-sourced ratings.
7 tools: 3 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
3 tools here change things. Govern them.
- 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 nAIm — API Registry for Agents MCP server can do
The nAIm — API Registry for Agents MCP server is published by the GitHub account AIAll-TARS. It has 7 tools. It can create or change data (3 tools: submit_rating, suggest_service and rate_service), but cannot delete data. 4 tools only read.
1 tool reads private data (get_service); 1 tool brings in text other people can write (get_service); 1 tool can send data out of your system (suggest_service). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.1.0.
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.
7 tools
Changes things 3Claude Code: ask
rate_serviceOptional judgement on an API you used, by slug (e.g.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.
Description, as the server wrote it Optional judgement on an API you used, by slug (e.g. 'elevenlabs-tts'). The default after use is last={ok, latency_ms} on your next nAIm call, not this tool. Scores are 1–5 and every one is optional. Quality, cost, reliability and compliance are judgement — omit them if you cannot know (a text model that generated audio cannot hear it; n=1 is not reliability). Latency only if you clocked it. notes is the slot for observation without judgement, e.g. 'produced 4.55s pl-PL audio; did not evaluate quality'.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
submit_ratingOptional judgement on an API you used, by slug or UUID.No findings
Why it is in this group
- The name "submit_rating" says "submit": a word for a change.
Description, as the server wrote it Optional judgement on an API you used, by slug or UUID. Prefer last={ok, latency_ms} on your next nAIm call for observation. Scores 1–5, every one optional. Omit any dimension you cannot evaluate — quality especially, if you cannot hear/see/taste the output. Returns the recomputed averages so you can see what a judgement moved.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
suggest_serviceSuggest an API service that is missing from the nAIm registry.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Suggest an API service that is missing from the nAIm registry. Use this when you needed an API, could not find it via search_services, and had to go elsewhere — that gap is exactly what the registry should close. Submissions enter a review queue and go live once approved. Only 'name' and 'url' are required, but fill in whatever else you actually know: a submission with auth type, pricing and docs URL gets approved far faster than a bare name. Do not guess — leave a field out if you are unsure.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
Only reads 4Show 4 read-only tools
get_ratingsGet aggregated agent ratings for a service — overall, quality, latency, reliability, cost scores.No findings
Why it is in this group
- The name "get_ratings" says "get": a word for reading.
Description, as the server wrote it Get aggregated agent ratings for a service — overall, quality, latency, reliability, cost scores. Each dimension carries its own count of how many raters actually assessed it, because raters score only what they observed. A low count on a dimension means that average is weak evidence, and avg_overall is a summary rather than a ranking key — two services rated on different dimensions are not directly comparable. If you have used this service, add your own rating via rate_service; thin counts are what make these numbers unreliable.
Annotations the server declares
- readOnlyHint: true
get_serviceGet full details for a specific API service, including docs URL, pricing, and auth type.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_service" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get full details for a specific API service, including docs URL, pricing, and auth type. Accepts the slug straight from search_services results — no UUID lookup needed. After you use it, pass last={token, used, ok, latency_ms} on your next nAIm call. That is observation. rate_service is optional judgement — omit any dimension you cannot actually evaluate.
Annotations the server declares
- readOnlyHint: true
list_categoriesList all available API service categories in the nAIm registry (e.g.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it List all available API service categories in the nAIm registry (e.g. tts, llm, embeddings).
Annotations the server declares
- readOnlyHint: true
search_servicesSearch the nAIm registry for API services.No findings
Why it is in this group
- The name "search_services" says "search": a word for reading.
Description, as the server wrote it Search the nAIm registry for API services. Filter by category slug (e.g. 'tts', 'llm'), a keyword, and/or a failure_domain tag (e.g. 'openai', 'azure-us-east') to find services that share infrastructure — useful for auditing pipeline coupling and shared failure domains. If you go on to use one of the services returned here, pass last={token, used, ok, latency_ms} on your next nAIm call. That is observation. rate_service is optional judgement.
Annotations the server declares
- readOnlyHint: true
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.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__naim__suggest_service"
]
}
}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, 18:56 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 526
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 526.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 526
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- Oct 29, 2026
- Protocol version: 2024-11-05 to 2025-06-18
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 526; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 526
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Tools7 changed.~7 changedView diff
- Changed:get_ratingsOnly readsannotations
- Changed:get_serviceOnly readsannotations
- Changed:list_categoriesOnly readsannotations
- Changed:rate_serviceChanges thingsannotations
- Changed:search_servicesOnly readsannotations
- Changed:submit_ratingChanges thingsannotations
- Changed:suggest_serviceChanges thingsannotations
PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18.View diff
- Protocol version: 2024-11-05 to 2025-06-18
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http naim https://mcp.naim.janis7ewski.org/mcpclaude mcp add --transport http naim https://mcp.naim.janis7ewski.org/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__naim__list_categories",
"mcp__naim__search_services",
"mcp__naim__get_service",
"mcp__naim__get_ratings"
],
"ask": [
"mcp__naim__submit_rating",
"mcp__naim__suggest_service",
"mcp__naim__rate_service"
],
"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 naim. Review it before you use it.
Capability tags behind 2 rules
- mcp__naim__get_service private-data, untrusted-input
- mcp__naim__suggest_service outbound
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.AIAll-TARS/naim/verify?hash=419bd48a50d124199137a9e95b90b8c92e03efe629263820f2706841ec6c5375" | jq -e '.changed == false'Pinned hash 419bd48a50d1, from Nov 15, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.AIAll-TARS/naim/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.AIAll-TARS/naim)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.
nAIm — API Registry for Agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the nAIm — API Registry for Agents MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 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 nAIm — API Registry for 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 nAIm — API Registry for Agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the nAIm — API Registry for Agents MCP server have?
- 7 tools: 3 write, 4 read. submit_rating, suggest_service, rate_service, list_categories, search_services, get_service and get_ratings.
Does the nAIm — API Registry for Agents MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the nAIm — API Registry for Agents MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): suggest_service.
Has the nAIm — API Registry for Agents MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.