mcpbeat Sign in

nAIm — API Registry for Agents MCP Server

by aiall-tars Your server? Claim it
answering

nAIm — API Registry for Agents is answering right now. Last checked 3 min ago. It exposes 7 tools.

316 AI APIs searchable by shared failure domain, freshness and agent-sourced ratings.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 48 days of history · worst day 0%
48 days agonow
100.0%
Uptime 24h
184 of 184 checks
7
Tools
read from the server
117 ms
Response time
average over 24h
open, no key
Access
sse

What changed 13

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 August 2026. No other catalogue keeps this.

9 Sep 4 tool descriptions were rewritten get_service, rate_service, search_services and 1 more
9 Sep 4 tools changed the parameters they ask for get_ratings, get_service, rate_service and 1 more
22 Aug 4 tools changed the parameters they ask for get_ratings, get_service, list_categories and 1 more
20 Aug a tool changed version

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add naim --transport http https://mcp.naim.janis7ewski.org/sse
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "naim": {
      "url": "https://mcp.naim.janis7ewski.org/sse"
    }
  }
}
~/.codex/config.toml
[mcp_servers.naim]
url = "https://mcp.naim.janis7ewski.org/sse"
.cursor/mcp.json
{
  "mcpServers": {
    "naim": {
      "url": "https://mcp.naim.janis7ewski.org/sse"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "naim": {
      "url": "https://mcp.naim.janis7ewski.org/sse"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

categories
list_categories
List all available API service categories in the nAIm registry (e.g. tts, llm, embeddings).
rate
rate_service
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'.
ratings
get_ratings
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.
service
get_service
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.
services
search_services
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.
submit
submit_rating
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.
suggest
suggest_service
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.naim.janis7ewski.org/sse sse answering 46 ms 3 min ago
https://mcp.naim.janis7ewski.org/mcp streamable-http answering 52 ms 3 min ago

Alternatives to nAIm — API Registry for Agents

same job, measured the same way
Midnight Rgb
by midnight-rgb

Domain registrar for AI agents. Search, register, and manage domains via API.

24 installs/wk local only
OriginGrid
by origingrid

AI Agent Source Registry. 288K+ curated sources for agentic search and discovery.

19 tools answering
Mnema — Shared Brain for You and Your AI Agents
by theboringpeople

Self-hostable shared brain for you and your AI agents — docs, flows, meetings, decisions, rationale

answering
Evergences Shared Memory
by seanmeverett

Public source-linked memories for AI agents: search, read, cite, reply, and share findings.

local only
Mote Registry
by mote

Search the MOTE AI agent registry for machine-readable businesses.

37 installs/wk local only
Clirank
by alexanderclapp

Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.

78 installs/wk local only
Knowledge for Agents
by knowledgeforagents

Search real problems, solutions, failed approaches and observed outcomes shared by AI agents.

4 tools answering
Unstoppable Domains
by unstoppabledomains

Domain search, registration, DNS, marketplace, and checkout with your AI agent.

answering

nAIm — API Registry for Agents — questions

Answers built from our own checks of this server.

What can nAIm — API Registry for Agents do?
It exposes 7 tools, read directly from the server on our last check. Among them: get_ratings, get_service, list_categories, rate_service, search_services, submit_rating and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is nAIm — API Registry for Agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 117 ms. The bar chart above shows every period we have measured.
Is nAIm — API Registry for Agents still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect nAIm — API Registry for Agents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does nAIm — API Registry for Agents need an API key?
No. nAIm — API Registry for Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is nAIm — API Registry for Agents?
It answers our handshake in 117 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.