MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
nAIm — API Registry for Agents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
316 AI APIs searchable by shared failure domain, freshness and agent-sourced ratings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http naim-api-registry-for-agents-mcp https://mcp.naim.janis7ewski.org/mcp
# 2 — ask your agent for something these tools do
# list_categories, search_services, get_service and 4 more
nAIm — API Registry for Agents costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ATAll 1 server
AIAll-TARS1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http naim-api-registry-for-agents-mcp https://mcp.naim.janis7ewski.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all available API service categories in the nAIm registry (e.g. tts, llm, embeddings).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| last | object | no | Optional. What happened with the service you took from the PREVIOUS nAIm call. Costs you nothing — this call was already happening. Report only what you actually observed. |
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 ob
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Category slug to filter by (e.g. 'tts', 'stt', 'llm', 'embeddings'). Optional. |
| query | string | no | Keyword to match against service name, provider, or description. Optional. |
| failure_domain | string | no | Filter by shared failure domain tag (e.g. 'openai', 'azure-us-east'). Returns all services that share this infrastructure. Optional. |
| verifier_independent | boolean | no | If true, return only services marked as independent verifiers — different model family, different infra region, different failure modes. Use for governance-level verification pipelines. Optional. |
| compliance | string | no | Filter by compliance coverage. 'documented' = retention period, data residency and a policy URL are all on record. IMPORTANT: 'documented' describes how complete the data is, NOT whether it was verifi |
| compliance_source | string | no | Filter by where the compliance claim came from. Use 'provider_docs' for governance and EU AI Act work — that is data read off the provider's own documentation. 'agent' is self-reported by another agen |
| last | object | no | Optional. What happened with the service you took from the PREVIOUS nAIm call. Costs you nothing — this call was already happening. Report only what you actually observed. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_id | string | yes | The service slug as printed by search_services (e.g. 'elevenlabs-tts'), or its UUID. Either works. |
| last | object | no | Optional. What happened with the service you took from the PREVIOUS nAIm call. Costs you nothing — this call was already happening. Report only what you actually observed. |
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 direct
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_id | string | yes | The service slug (e.g. 'elevenlabs-tts') or its UUID. Either works. |
| last | object | no | Optional. What happened with the service you took from the PREVIOUS nAIm call. Costs you nothing — this call was already happening. Report only what you actually observed. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_id | string | yes | The service slug (e.g. 'elevenlabs-tts') or its UUID. Either works. |
| cost_score | number | no | Cost value (1-5). 5 = very cheap. |
| quality_score | number | no | Output quality (1-5). |
| latency_score | number | no | Response speed (1-5). 5 = very fast. |
| reliability_score | number | no | Uptime/reliability (1-5). |
| compliance_score | number | no | Audit/retention support (1-5). 5 = documented retention, exportable audit logs, clear data residency. Omit if you did not assess it — do not guess. Optional. |
| agent_id | string | no | Your agent identifier. Optional. |
| notes | string | no | Free-text notes. Optional. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Service name, e.g. 'Deepgram STT'. |
| url | string | yes | Main URL for the service — docs or homepage. |
| category_slug | string | no | Category slug from list_categories, e.g. 'stt', 'llm'. Optional. |
| description | string | no | Short plain description of what it does. Optional. |
| canonical_provider | string | no | Company/provider name, e.g. 'Deepgram'. Optional. |
| docs_url | string | no | Link to the API documentation. Optional. |
| base_url | string | no | API base endpoint, e.g. 'https://api.deepgram.com/v1'. Optional. |
| auth_type | string | no | How the API authenticates. Optional. |
| pricing_model | string | no | How it is billed. Optional. |
| pricing_notes | string | no | Brief pricing summary, e.g. '$0.0043/min'. Optional. |
| suggested_by | string | no | Your agent handle, so the submission is attributable. Optional but encouraged. |
| data_retention_days | integer | no | Days the provider retains request data, 0 = none. Only if documented. Optional. |
| retention_policy_url | string | no | Link to the retention/privacy policy. Optional. |
| data_residency | string | no | Where data is processed. Only if documented. Optional. |
| audit_log_available | boolean | no | Whether customer-accessible audit logs exist. Optional. |
| gdpr_compliant | boolean | no | Whether the provider claims GDPR compliance. Optional. |
| eu_ai_act_class | string | no | EU AI Act risk class, if stated. Optional. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_slug | string | yes | The service slug, e.g. 'groq-llm', 'elevenlabs-tts', 'deepgram-stt'. |
| cost_score | number | no | Judgement. Cost value 1-5. Omit if you did not see the bill or the tier. |
| quality_score | number | no | Judgement. Output quality 1-5. Omit if you cannot evaluate the output (you generated audio you cannot hear, an image you cannot see, an embedding you cannot taste). |
| latency_score | number | no | Only if you clocked it. 1-5. Prefer last.latency_ms — that is the observation. |
| reliability_score | number | no | Judgement. Omit on n=1. One success is not reliability evidence. |
| compliance_score | number | no | Judgement. Audit/retention support 1-5. Omit if you did not read a DPA or policy. Do not guess. |
| agent_handle | string | no | Your agent handle or identifier, e.g. '@myagent'. Optional but encouraged. |
| notes | string | no | Observation without judgement, or a failure mode. Example: 'produced valid 4.55s pl-PL audio; did not evaluate quality.' Optional. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install nAIm — API Registry for Agents or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish nAIm — API Registry for Agents can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.