io.usefulapi/nomic-atlas
REMOTE · NOMIC-ATLAS.USEFULAPI.IO · SCANNED OCT 3
Semantic nearest-neighbour search over your datasets, plus indices and projections.
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 → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 650 tokens (~72/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/nomic-atlas MCP server?
io.usefulapi/nomic-atlas is a hosted endpoint at https://nomic-atlas.usefulapi.io/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.
remote · nomic-atlas.usefulapi.io
claude mcp add --transport http io-usefulapi-nomic-atlas 'https://nomic-atlas.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-nomic-atlas": {
"url": "https://nomic-atlas.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-nomic-atlas": {
"type": "http",
"url": "https://nomic-atlas.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-nomic-atlas] url = "https://nomic-atlas.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-nomic-atlas": {
"type": "remote",
"url": "https://nomic-atlas.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-nomic-atlas --url 'https://nomic-atlas.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-nomic-atlas:
url: "https://nomic-atlas.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-nomic-atlas": {
"Transport": "http",
"Url": "https://nomic-atlas.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-nomic-atlas -t streamable-http -u 'https://nomic-atlas.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-nomic-atlas": {
"type": "http",
"url": "https://nomic-atlas.usefulapi.io/mcp"
}
}
} 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.
- 3 Oct 26 +61
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Server version: 1.3.0 → 1.5.1 functional
- 2 Oct 26 −56
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 +46
- Authorization: unverified → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 30 Sept 26 +10
- Transport: fail → pass ▲ 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
- 29 Sept 26 18
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 Oct 2026 · Probed https://nomic-atlas.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nomic-atlas.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://nomic-atlas.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://nomic-atlas.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://nomic-atlas.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://nomic-atlas.usefulapi.io/mcp |
| Authorisation server | https://nomic-atlas.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nomic-atlas.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://nomic-atlas.usefulapi.io/mcp | HTTPS enforced | 301 | https://nomic-atlas.usefulapi.io/mcp |
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 →
nomic_get_dataset Get a dataset by id ~57
Fetch a dataset (Atlas calls it a project) by id — its schema, size, indices and projections. Atlas: GET /v1/project/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | The dataset's id (a UUID). |
No output schema declared.
No examples provided.
nomic_get_dataset_by_slug Get a dataset by name ~73
Fetch a dataset by organisation slug and dataset slug — the human-readable path, and usually easier than finding the UUID. Atlas: GET /v1/project/{organization_slug}/{project_slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_slug | string | yes | The dataset's slug. |
| organization_slug | string | yes | The organisation's slug. |
No output schema declared.
No examples provided.
nomic_get_index_job Get an index job ~73
Fetch the status of an index-building job. Atlas indexes take time to build, and a vector search against an unbuilt map fails — this is how you tell which it is. Atlas: GET /v1/project/index/job/{job_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The index job's id. |
No output schema declared.
No examples provided.
nomic_get_organization Get an organisation ~51
Fetch an organisation by slug, with the datasets it holds. Atlas: GET /v1/organization/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The organisation's slug, from nomic_get_user. |
No output schema declared.
No examples provided.
nomic_get_projection_schema Get a projection's schema ~53
Fetch the field schema of one projection — the columns available on its records. Atlas: GET /v1/project/projection/{projection_id}/schema.
| Name | Type | Req | Description |
|---|---|---|---|
| projection_id | string | yes | The projection's id. |
No output schema declared.
No examples provided.
nomic_get_tag_status Get a tag's status ~74
Check whether a tag has finished computing its membership. A tag that is still building returns partial results. Atlas: GET /v1/project/projection/tags/status.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | The dataset's id. |
| tag_id | string | yes | The tag's id, from nomic_list_tags. |
No output schema declared.
No examples provided.
nomic_get_user Get the current user ~45
Fetch the account the API key belongs to, including the organisations it can access. Start here — the organisation slug feeds the other tools. Atlas: GET /v1/user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nomic_list_tags List a projection's tags ~66
List the tags defined on one projection — the labelled selections a person made on the map. Atlas: GET /v1/project/projection/tags/get/all.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | The dataset's id. |
| projection_id | string | yes | The projection's id. |
No output schema declared.
No examples provided.
nomic_nearest_neighbors_by_id Find similar records ~158
Semantic search: given the ids of records already in a dataset, return their nearest neighbours in embedding space, with distances. This is what Atlas is for — finding what resembles what across unstructured data. Needs a BUILT index; if the map is still building the call fails with a 500, so check nomic_get_index_job. Atlas: POST /v1/project/data/get/nearest_neighbors/by_id.
| Name | Type | Req | Description |
|---|---|---|---|
| atlas_index_id | string | yes | The index to search. Read it from the dataset returned by nomic_get_dataset. |
| datum_ids | array | yes | Ids of the seed records to find neighbours of. |
| k | integer | yes | How many neighbours to return per seed, 1-100. |
No output schema declared.
No examples provided.
What is the io.usefulapi/nomic-atlas MCP server?
io.usefulapi/nomic-atlas is an MCP server listed in the public MCP registry as io.usefulapi/nomic-atlas. Semantic nearest-neighbour search over your datasets, plus indices and projections. This page covers its hosted endpoint (https://nomic-atlas.usefulapi.io/mcp).
Is the io.usefulapi/nomic-atlas MCP server safe to use?
io.usefulapi/nomic-atlas scores 79 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 io.usefulapi/nomic-atlas MCP server expose?
io.usefulapi/nomic-atlas exposes 9 tools: nomic_get_user, nomic_get_organization, nomic_get_dataset, nomic_get_dataset_by_slug, nomic_nearest_neighbors_by_id, and 4 more. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.
Does the io.usefulapi/nomic-atlas MCP server require authentication?
Yes. io.usefulapi/nomic-atlas asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/nomic-atlas MCP server still maintained?
io.usefulapi/nomic-atlas is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.