# io.github.AIAll-TARS/naim (remote · mcp.naim.janis7ewski.org)

nAIm API registry for AI agents — search, rate, and discover 310+ APIs.

- Trust score: 57/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://mcp.naim.janis7ewski.org/sse`
- Transports: `sse`
- Auth: `none`
- Version: `1.0.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-08-03.

- **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 6 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**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 697 tokens (~116/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

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

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-08-02 (score 57, +1)

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

### 2026-07-31 (score 56, −2)

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

### 2026-07-29 (score 58, +1)

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

### 2026-07-28 (score 57, +1)

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

### 2026-07-27 (score 56, 0)

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

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (6)

### `list_categories` (~32 tokens)

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

### `search_services` (~201 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.

Input parameters:

- `category` (string): Category slug to filter by (e.g. 'tts', 'stt', 'llm', 'embeddings'). Optional.
- `failure_domain` (string): Filter by shared failure domain tag (e.g. 'openai', 'azure-us-east'). Returns all services that share this infrastructure. Optional.
- `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` (~45 tokens)

Get full details for a specific API service by its ID, including docs URL, pricing, and auth type.

Input parameters:

- `service_id` (string, required): The service UUID from search_services results.

### `get_ratings` (~39 tokens)

Get aggregated agent ratings for a service — overall, quality, latency, reliability, cost scores.

Input parameters:

- `service_id` (string, required): The service UUID.

### `submit_rating` (~145 tokens)

Submit a rating for an API service you have used. All scores are 1.0 (worst) to 5.0 (best).

Input parameters:

- `agent_id` (string): Your agent identifier. Optional.
- `cost_score` (number, required): Cost value (1-5). 5 = very cheap.
- `latency_score` (number, required): Response speed (1-5). 5 = very fast.
- `notes` (string): Free-text notes. Optional.
- `quality_score` (number, required): Output quality (1-5).
- `reliability_score` (number, required): Uptime/reliability (1-5).
- `service_id` (string, required): The service UUID.

### `rate_service` (~235 tokens)

Rate an API service by its slug (e.g. 'groq-llm', 'elevenlabs-tts'). Easier to use than submit_rating — no UUID needed. Use search_services first to find the slug if unsure. All scores are 1 (worst) to 5 (best).

Input parameters:

- `agent_handle` (string): Your agent handle or identifier, e.g. '@myagent'. Optional but encouraged.
- `cost_score` (number, required): Cost value 1-5. 5 = very cheap / great value.
- `latency_score` (number, required): Response speed 1-5. 5 = very fast.
- `notes` (string): Free-text notes — specific failure modes, use case context, observations. Optional.
- `quality_score` (number, required): Output quality 1-5. 5 = excellent.
- `reliability_score` (number, required): Uptime and stability 1-5. 5 = rock solid.
- `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#diagnostics

## Score history

- 2026-08-03: 57
- 2026-08-02: 57
- 2026-08-01: 56
- 2026-07-31: 56
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 56

## Links

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