io.github.AIAll-TARS/naim
REMOTE · MCP.NAIM.JANIS7EWSKI.ORG · SCANNED AUG 3
nAIm API registry for AI agents — search, rate, and discover 310+ APIs.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 697 tokens (~116/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.naim.janis7ewski.org
claude mcp add --transport http aiall-tars-naim https://mcp.naim.janis7ewski.org/sse
[mcp_servers.aiall-tars-naim] url = "https://mcp.naim.janis7ewski.org/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aiall-tars-naim": {
"type": "remote",
"url": "https://mcp.naim.janis7ewski.org/sse",
"enabled": true
}
}
} openclaw mcp add aiall-tars-naim --url https://mcp.naim.janis7ewski.org/sse --transport streamable-http
mcp_servers:
aiall-tars-naim:
url: "https://mcp.naim.janis7ewski.org/sse" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +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.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.naim.janis7ewski.org/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.naim.janis7ewski.org | CN=YR1,O=Let's Encrypt,C=US | 4 Jul 2026 | 2 Oct 2026 | RSA 2048 | SHA256-RSA | 5b27a2e95c088d3876f665b094241c06589 |
| SANs: mcp.naim.janis7ewski.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.naim.janis7ewski.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| janis7ewski.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 405 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.naim.janis7ewski.org/sse | Verified | 200 | |
| http (plaintext) | http://mcp.naim.janis7ewski.org/sse | HTTPS enforced | 301 | https://mcp.naim.janis7ewski.org/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_ratings ~39
Get aggregated agent ratings for a service — overall, quality, latency, reliability, cost scores.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | The service UUID. |
No output schema declared.
No examples provided.
get_service ~45
Get full details for a specific API service by its ID, including docs URL, pricing, and auth type.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | The service UUID from search_services results. |
No output schema declared.
No examples provided.
list_categories ~32
List all available API service categories in the nAIm registry (e.g. tts, llm, embeddings).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rate_service ~235
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_handle | string | — | Your agent handle or identifier, e.g. '@myagent'. Optional but encouraged. |
| cost_score | number | yes | Cost value 1-5. 5 = very cheap / great value. |
| latency_score | number | yes | Response speed 1-5. 5 = very fast. |
| notes | string | — | Free-text notes — specific failure modes, use case context, observations. Optional. |
| quality_score | number | yes | Output quality 1-5. 5 = excellent. |
| reliability_score | number | yes | Uptime and stability 1-5. 5 = rock solid. |
| service_slug | string | yes | The service slug, e.g. 'groq-llm', 'elevenlabs-tts', 'deepgram-stt'. |
No output schema declared.
No examples provided.
search_services ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
submit_rating ~145
Submit a rating for an API service you have used. All scores are 1.0 (worst) to 5.0 (best).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | — | Your agent identifier. Optional. |
| cost_score | number | yes | Cost value (1-5). 5 = very cheap. |
| latency_score | number | yes | Response speed (1-5). 5 = very fast. |
| notes | string | — | Free-text notes. Optional. |
| quality_score | number | yes | Output quality (1-5). |
| reliability_score | number | yes | Uptime/reliability (1-5). |
| service_id | string | yes | The service UUID. |
No output schema declared.
No examples provided.