Skip to content

Nomic Atlas MCP by usefulapi

io.usefulapi/nomic-atlasusefulapi.iostreamable-httpv1.40.4Scanned

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

9 tools: 1 change things and 8 only read.

Tools: 0 delete, 0 irreversible, 1 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Nomic Atlas MCP by usefulapi can do

The Nomic Atlas MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 9 tools. It can create or change data (1 tool: nomic_nearest_neighbors_by_id), but cannot delete data. 8 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 1Claude Code: ask
  • nomic_nearest_neighbors_by_idSemantic search: given the ids of records already in a dataset, return their nearest neighbours in embedding space, with distances.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find similar records
    • readOnlyHint: true
Only reads 8Show 8 read-only tools
  • nomic_get_datasetFetch a dataset (Atlas calls it a project) by id — its schema, size, indices and projections.No findings

    Why it is in this group

    • The name "nomic_get_dataset" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a dataset (Atlas calls it a project) by id — its schema, size, indices and projections. Atlas: GET /v1/project/{id}.

    Annotations the server declares

    • title: Get a dataset by id
    • readOnlyHint: true
  • nomic_get_dataset_by_slugFetch a dataset by organisation slug and dataset slug — the human-readable path, and usually easier than finding the UUID.No findings

    Why it is in this group

    • The name "nomic_get_dataset_by_slug" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get a dataset by name
    • readOnlyHint: true
  • nomic_get_index_jobFetch the status of an index-building job.No findings

    Why it is in this group

    • The name "nomic_get_index_job" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get an index job
    • readOnlyHint: true
  • nomic_get_organizationFetch an organisation by slug, with the datasets it holds.No findings

    Why it is in this group

    • The name "nomic_get_organization" says "get": a word for reading.
    Description, as the server wrote it
    Fetch an organisation by slug, with the datasets it holds. Atlas: GET /v1/organization/{slug}.

    Annotations the server declares

    • title: Get an organisation
    • readOnlyHint: true
  • nomic_get_projection_schemaFetch the field schema of one projection — the columns available on its records.No findings

    Why it is in this group

    • The name "nomic_get_projection_schema" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the field schema of one projection — the columns available on its records. Atlas: GET /v1/project/projection/{projection_id}/schema.

    Annotations the server declares

    • title: Get a projection's schema
    • readOnlyHint: true
  • nomic_get_tag_statusCheck whether a tag has finished computing its membership.No findings

    Why it is in this group

    • The name "nomic_get_tag_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a tag's status
    • readOnlyHint: true
  • nomic_get_userFetch the account the API key belongs to, including the organisations it can access.No findings

    Why it is in this group

    • The name "nomic_get_user" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get the current user
    • readOnlyHint: true
  • nomic_list_tagsList the tags defined on one projection — the labelled selections a person made on the map.No findings

    Why it is in this group

    • The name "nomic_list_tags" says "list": a word for reading.
    Description, as the server wrote it
    List the tags defined on one projection — the labelled selections a person made on the map. Atlas: GET /v1/project/projection/tags/get/all.

    Annotations the server declares

    • title: List a projection's tags
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://nomic-atlas.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://nomic-atlas.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://nomic-atlas.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://nomic-atlas.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nomic-atlas__nomic_get_user",
      "mcp__nomic-atlas__nomic_get_organization",
      "mcp__nomic-atlas__nomic_get_dataset",
      "mcp__nomic-atlas__nomic_get_dataset_by_slug",
      "mcp__nomic-atlas__nomic_get_index_job",
      "mcp__nomic-atlas__nomic_get_projection_schema",
      "mcp__nomic-atlas__nomic_list_tags",
      "mcp__nomic-atlas__nomic_get_tag_status"
    ],
    "ask": [
      "mcp__nomic-atlas__nomic_nearest_neighbors_by_id"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nomic-atlas. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/nomic-atlas/verify?hash=c12a012b44c18b6a44e69ae0a311f4deffb21950b0de4346e6f91614b7ff2f91" | jq -e '.changed == false'

Pinned hash c12a012b44c1, from Oct 25, 2026, 23:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/nomic-atlas/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/nomic-atlas
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/nomic-atlas.svg)](https://radar.anlyon.com/servers/io.usefulapi/nomic-atlas)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Nomic Atlas MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Nomic Atlas MCP by usefulapi safe?

No scan can promise that. What its definitions show: 9 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nomic Atlas MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Nomic Atlas MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Nomic Atlas MCP by usefulapi have?

9 tools: 1 write, 8 read. nomic_nearest_neighbors_by_id, nomic_get_user, nomic_get_organization, nomic_get_dataset, nomic_get_dataset_by_slug, nomic_get_index_job, nomic_get_projection_schema, nomic_list_tags and 1 more.

Does the Nomic Atlas MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Nomic Atlas MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Nomic Atlas MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.