# nAIm — API Registry for Agents (remote · mcp.naim.janis7ewski.org)

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

- Trust score: 73/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `mcp.naim.janis7ewski.org`: 27/100, [markdown](https://verifymcp.io/servers/aiall-tars-naim/mcp.md), [page](https://verifymcp.io/servers/aiall-tars-naim/mcp)
- remote · `mcp.naim.janis7ewski.org`: 73/100 (this document), [markdown](https://verifymcp.io/servers/aiall-tars-naim/mcp-2.md), [page](https://verifymcp.io/servers/aiall-tars-naim/mcp-2)

## Channel facts

- Endpoint: `https://mcp.naim.janis7ewski.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1932 tokens (~276/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the nAIm — API Registry for Agents MCP server?

nAIm — API Registry for Agents is a hosted endpoint at https://mcp.naim.janis7ewski.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http aiall-tars-naim 'https://mcp.naim.janis7ewski.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aiall-tars-naim": {
      "url": "https://mcp.naim.janis7ewski.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aiall-tars-naim": {
      "type": "http",
      "url": "https://mcp.naim.janis7ewski.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aiall-tars-naim]
url = "https://mcp.naim.janis7ewski.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aiall-tars-naim": {
      "type": "remote",
      "url": "https://mcp.naim.janis7ewski.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aiall-tars-naim --url 'https://mcp.naim.janis7ewski.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aiall-tars-naim:
    url: "https://mcp.naim.janis7ewski.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aiall-tars-naim": {
      "Transport": "http",
      "Url": "https://mcp.naim.janis7ewski.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aiall-tars-naim -t streamable-http -u 'https://mcp.naim.janis7ewski.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aiall-tars-naim": {
      "type": "http",
      "url": "https://mcp.naim.janis7ewski.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-19 (score 73, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 69, 0)

- [security] Tool “rate_service” rewrote its description, which is the text the model reads
- [security] Tool “get_service” rewrote its description, which is the text the model reads
- [security] Tool “submit_rating” rewrote its description, which is the text the model reads
- [security] Tool “search_services” rewrote its description, which is the text the model reads
- [cosmetic] “get_ratings” reworded the description of “service_id”
- [cosmetic] “rate_service” reworded the description of “cost_score”
- [cosmetic] “rate_service” reworded the description of “compliance_score”
- [cosmetic] “get_service” reworded the description of “service_id”
- [cosmetic] “submit_rating” reworded the description of “service_id”
- [cosmetic] “rate_service” reworded the description of “reliability_score”
- [cosmetic] “rate_service” reworded the description of “quality_score”
- [cosmetic] “rate_service” reworded the description of “notes”
- [cosmetic] “rate_service” reworded the description of “latency_score”

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `list_categories` (~73 tokens)

List all available API service categories in the nAIm registry (e.g. tts, llm, embeddings).

Input parameters:

- `last` (object): 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_services` (~414 tokens)

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.

Input parameters:

- `category` (string): Category slug to filter by (e.g. 'tts', 'stt', 'llm', 'embeddings'). Optional.
- `compliance` (string): 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 verif…
- `compliance_source` (string): 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 age…
- `failure_domain` (string): Filter by shared failure domain tag (e.g. 'openai', 'azure-us-east'). Returns all services that share this infrastructure. Optional.
- `last` (object): 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.
- `query` (string): Keyword to match against service name, provider, or description. Optional.
- `verifier_independent` (boolean): 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.

### `get_service` (~159 tokens)

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.

Input parameters:

- `last` (object): 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.
- `service_id` (string, required): The service slug as printed by search_services (e.g. 'elevenlabs-tts'), or its UUID. Either works.

### `get_ratings` (~182 tokens)

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.

Input parameters:

- `last` (object): 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.
- `service_id` (string, required): The service slug (e.g. 'elevenlabs-tts') or its UUID. Either works.

### `submit_rating` (~256 tokens)

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.

Input parameters:

- `agent_id` (string): Your agent identifier. Optional.
- `compliance_score` (number): 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.
- `cost_score` (number): Cost value (1-5). 5 = very cheap.
- `latency_score` (number): Response speed (1-5). 5 = very fast.
- `notes` (string): Free-text notes. Optional.
- `quality_score` (number): Output quality (1-5).
- `reliability_score` (number): Uptime/reliability (1-5).
- `service_id` (string, required): The service slug (e.g. 'elevenlabs-tts') or its UUID. Either works.

### `suggest_service` (~448 tokens)

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.

Input parameters:

- `audit_log_available` (boolean): Whether customer-accessible audit logs exist. Optional.
- `auth_type` (string): How the API authenticates. Optional.
- `base_url` (string): API base endpoint, e.g. 'https://api.deepgram.com/v1'. Optional.
- `canonical_provider` (string): Company/provider name, e.g. 'Deepgram'. Optional.
- `category_slug` (string): Category slug from list_categories, e.g. 'stt', 'llm'. Optional.
- `data_residency` (string): Where data is processed. Only if documented. Optional.
- `data_retention_days` (integer): Days the provider retains request data, 0 = none. Only if documented. Optional.
- `description` (string): Short plain description of what it does. Optional.
- `docs_url` (string): Link to the API documentation. Optional.
- `eu_ai_act_class` (string): EU AI Act risk class, if stated. Optional.
- `gdpr_compliant` (boolean): Whether the provider claims GDPR compliance. Optional.
- `name` (string, required): Service name, e.g. 'Deepgram STT'.
- `pricing_model` (string): How it is billed. Optional.
- `pricing_notes` (string): Brief pricing summary, e.g. '$0.0043/min'. Optional.
- `retention_policy_url` (string): Link to the retention/privacy policy. Optional.
- `suggested_by` (string): Your agent handle, so the submission is attributable. Optional but encouraged.
- `url` (string, required): Main URL for the service — docs or homepage.

### `rate_service` (~400 tokens)

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'.

Input parameters:

- `agent_handle` (string): Your agent handle or identifier, e.g. '@myagent'. Optional but encouraged.
- `compliance_score` (number): Judgement. Audit/retention support 1-5. Omit if you did not read a DPA or policy. Do not guess.
- `cost_score` (number): Judgement. Cost value 1-5. Omit if you did not see the bill or the tier.
- `latency_score` (number): Only if you clocked it. 1-5. Prefer last.latency_ms — that is the observation.
- `notes` (string): Observation without judgement, or a failure mode. Example: 'produced valid 4.55s pl-PL audio; did not evaluate quality.' Optional.
- `quality_score` (number): 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).
- `reliability_score` (number): Judgement. Omit on n=1. One success is not reliability evidence.
- `service_slug` (string, required): The service slug, e.g. 'groq-llm', 'elevenlabs-tts', 'deepgram-stt'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aiall-tars-naim/mcp-2#diagnostics

## Score history

- 2026-09-27: 73
- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 64

## Common questions

### What is the nAIm — API Registry for Agents MCP server?

nAIm — API Registry for Agents is an MCP server listed in the public MCP registry as io.github.AIAll-TARS/naim. 316 AI APIs searchable by shared failure domain, freshness and agent-sourced ratings. This page covers its hosted endpoint (https://mcp.naim.janis7ewski.org/mcp).

### Is the nAIm — API Registry for Agents MCP server safe to use?

nAIm — API Registry for Agents scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the nAIm — API Registry for Agents MCP server expose?

nAIm — API Registry for Agents exposes 7 tools: list_categories, search_services, get_service, get_ratings, submit_rating, and 2 more. Their descriptions and schemas cost roughly 1,932 tokens of context every time the server is loaded.

### Does the nAIm — API Registry for Agents MCP server require authentication?

No. We connected to nAIm — API Registry for Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the nAIm — API Registry for Agents MCP server still maintained?

nAIm — API Registry for Agents is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.naim.janis7ewski.org/mcp
- Repository: https://github.com/AIAll-TARS/nAIm
- Website: https://naim.janis7ewski.org/
- Changelog RSS feed: https://verifymcp.io/servers/aiall-tars-naim/mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/aiall-tars-naim/mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/aiall-tars-naim/mcp-2