Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

nAIm — API Registry for Agents

REMOTE · MCP.NAIM.JANIS7EWSKI.ORG · 2 COMPONENTS

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

−5 this week 22 Trust /100

Last scanned (17 hours ago)

Scores higher than 7% of remote servers

Unreachable for 3 days in a row. Last reached 18 Nov 2026.

Category AI and Machine Learning

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

Recent critical change

TLS certificate (19 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • TLS certificate hostname

    Registry says
    https://mcp.naim.janis7ewski.org/sse
    Package shows
    Certificate names ai.janis7ewski.org, mirkai.janis7ewski.org

    The certificate does not name the host we connected to. See the evidence →

Changelog

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.

  • 21 Nov 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 19 Nov 26 0
    • TLS certificate: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Endpoint reachability: not serving MCP → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
  • 6 Nov 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
  • 28 Sept 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
  • 25 Sept 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 Aug 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
  • 11 Aug 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
  • 7 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.37 → unverified ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.naim.janis7ewski.org/sse

TLS invalid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Chain error: Hostname mismatch

Subject Issuer Valid from Valid until Key Signature Serial
CN=ai.janis7ewski.org CN=YR1,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 RSA 2048 SHA256-RSA 5d72b9bc9416fa1d63779b3cd9794004b97
SANs: ai.janis7ewski.org, mirkai.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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.naim.janis7ewski.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
janis7ewski.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.naim.janis7ewski.org/sse TLS failed
http (plaintext) http://mcp.naim.janis7ewski.org/sse HTTPS enforced 301 https://ai.janis7ewski.org/sse
MCP tools · 7 exposed · ~1,400 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_ratings ~71

Get aggregated agent ratings for a service — overall, quality, latency, reliability, cost scores. Also returns avg_compliance and compliance_count; compliance_count is how many raters actually assessed compliance, so a low count means avg_compliance is weak evidence.

NameTypeReqDescription
service_idstringyesThe 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.

NameTypeReqDescription
service_idstringyesThe 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 ~282

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

NameTypeReqDescription
agent_handlestring–Your agent handle or identifier, e.g. '@myagent'. Optional but encouraged.
compliance_scorenumber–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_scorenumberyesCost value 1-5. 5 = very cheap / great value.
latency_scorenumberyesResponse speed 1-5. 5 = very fast.
notesstring–Free-text notes — specific failure modes, use case context, observations. Optional.
quality_scorenumberyesOutput quality 1-5. 5 = excellent.
reliability_scorenumberyesUptime and stability 1-5. 5 = rock solid.
service_slugstringyesThe service slug, e.g. 'groq-llm', 'elevenlabs-tts', 'deepgram-stt'.

No output schema declared.

No examples provided.

search_services ~330

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.

NameTypeReqDescription
categorystring–Category slug to filter by (e.g. 'tts', 'stt', 'llm', 'embeddings'). Optional.
compliancestring–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_sourcestring–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_domainstring–Filter by shared failure domain tag (e.g. 'openai', 'azure-us-east'). Returns all services that share this infrastructure. Optional.
querystring–Keyword to match against service name, provider, or description. Optional.
verifier_independentboolean–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 ~192

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

NameTypeReqDescription
agent_idstring–Your agent identifier. Optional.
compliance_scorenumber–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_scorenumberyesCost value (1-5). 5 = very cheap.
latency_scorenumberyesResponse speed (1-5). 5 = very fast.
notesstring–Free-text notes. Optional.
quality_scorenumberyesOutput quality (1-5).
reliability_scorenumberyesUptime/reliability (1-5).
service_idstringyesThe service UUID.

No output schema declared.

No examples provided.

suggest_service ~448

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.

NameTypeReqDescription
audit_log_availableboolean–Whether customer-accessible audit logs exist. Optional.
auth_typestring–How the API authenticates. Optional.
base_urlstring–API base endpoint, e.g. 'https://api.deepgram.com/v1'. Optional.
canonical_providerstring–Company/provider name, e.g. 'Deepgram'. Optional.
category_slugstring–Category slug from list_categories, e.g. 'stt', 'llm'. Optional.
data_residencystring–Where data is processed. Only if documented. Optional.
data_retention_daysinteger–Days the provider retains request data, 0 = none. Only if documented. Optional.
descriptionstring–Short plain description of what it does. Optional.
docs_urlstring–Link to the API documentation. Optional.
eu_ai_act_classstring–EU AI Act risk class, if stated. Optional.
gdpr_compliantboolean–Whether the provider claims GDPR compliance. Optional.
namestringyesService name, e.g. 'Deepgram STT'.
pricing_modelstring–How it is billed. Optional.
pricing_notesstring–Brief pricing summary, e.g. '$0.0043/min'. Optional.
retention_policy_urlstring–Link to the retention/privacy policy. Optional.
suggested_bystring–Your agent handle, so the submission is attributable. Optional but encouraged.
urlstringyesMain URL for the service — docs or homepage.

No output schema declared.

No examples provided.

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/sse, 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.

remote · mcp.naim.janis7ewski.org

# add to Claude Code
claude mcp add --transport http aiall-tars-naim 'https://mcp.naim.janis7ewski.org/sse'
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/sse).

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,400 tokens of context every time the server is loaded.

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

Its publisher declares no required credentials for nAIm — API Registry for Agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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

nAIm — API Registry for Agents is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 18 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.