# io.usefulapi/nomic-atlas (remote · nomic-atlas.usefulapi.io)

Semantic nearest-neighbour search over your datasets, plus indices and projections.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `nomic-atlas.usefulapi.io`: 79/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-nomic-atlas/nomic-atlas.md), [page](https://verifymcp.io/servers/io-usefulapi-nomic-atlas/nomic-atlas)

## Channel facts

- Endpoint: `https://nomic-atlas.usefulapi.io/mcp`
- Transports: `streamable-http`
- 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-10-03.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 650 tokens (~72/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http io-usefulapi-nomic-atlas 'https://nomic-atlas.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-nomic-atlas": {
      "url": "https://nomic-atlas.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-nomic-atlas": {
      "type": "http",
      "url": "https://nomic-atlas.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-nomic-atlas]
url = "https://nomic-atlas.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-nomic-atlas": {
      "type": "remote",
      "url": "https://nomic-atlas.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-nomic-atlas --url 'https://nomic-atlas.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-nomic-atlas:
    url: "https://nomic-atlas.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-nomic-atlas": {
      "Transport": "http",
      "Url": "https://nomic-atlas.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-nomic-atlas -t streamable-http -u 'https://nomic-atlas.usefulapi.io/mcp'
```

### Other

```json
{
  "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.

## 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-10-03 (score 79, +61)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07
- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-02 (score 18, −56)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-01 (score 74, +46)

- [security regression] Authorization: unverified → fail
- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-09-30 (score 28, +10)

- [security improvement] 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.

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (9)

### `nomic_get_user` (~45 tokens)

Get the current user

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.

### `nomic_get_organization` (~51 tokens)

Get an organisation

Fetch an organisation by slug, with the datasets it holds. Atlas: GET /v1/organization/{slug}.

Input parameters:

- `slug` (string, required): The organisation's slug, from nomic_get_user.

### `nomic_get_dataset` (~57 tokens)

Get a dataset by id

Fetch a dataset (Atlas calls it a project) by id — its schema, size, indices and projections. Atlas: GET /v1/project/{id}.

Input parameters:

- `dataset_id` (string, required): The dataset's id (a UUID).

### `nomic_get_dataset_by_slug` (~73 tokens)

Get a dataset by name

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

Input parameters:

- `dataset_slug` (string, required): The dataset's slug.
- `organization_slug` (string, required): The organisation's slug.

### `nomic_nearest_neighbors_by_id` (~158 tokens)

Find similar records

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.

Input parameters:

- `atlas_index_id` (string, required): The index to search. Read it from the dataset returned by nomic_get_dataset.
- `datum_ids` (array, required): Ids of the seed records to find neighbours of.
- `k` (integer, required): How many neighbours to return per seed, 1-100.

### `nomic_get_index_job` (~73 tokens)

Get an index job

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

Input parameters:

- `job_id` (string, required): The index job's id.

### `nomic_get_projection_schema` (~53 tokens)

Get a projection's schema

Fetch the field schema of one projection — the columns available on its records. Atlas: GET /v1/project/projection/{projection_id}/schema.

Input parameters:

- `projection_id` (string, required): The projection's id.

### `nomic_list_tags` (~66 tokens)

List a projection's tags

List the tags defined on one projection — the labelled selections a person made on the map. Atlas: GET /v1/project/projection/tags/get/all.

Input parameters:

- `dataset_id` (string, required): The dataset's id.
- `projection_id` (string, required): The projection's id.

### `nomic_get_tag_status` (~74 tokens)

Get a tag's status

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.

Input parameters:

- `dataset_id` (string, required): The dataset's id.
- `tag_id` (string, required): The tag's id, from nomic_list_tags.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-nomic-atlas/nomic-atlas#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 18
- 2026-10-01: 74
- 2026-09-30: 28
- 2026-09-29: 18

## Common questions

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

## Links

- Remote endpoint: https://nomic-atlas.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-nomic-atlas/nomic-atlas.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-nomic-atlas/nomic-atlas.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-nomic-atlas/nomic-atlas