Skip to content
Agentic Atlas logo

Agentic Atlas MCP server

Which servers in the official MCP registry are Agentic Atlas's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Agentic Atlas

Whose server it is
  • Registry namedev.agentic-atlas/atlasverified in the MCP registry

The registry name sits under agentic-atlas.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools5
  • Server calls itselfAgentic Atlas
  • Server version1.0.11
  • Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 146 ms.

Tools it offers5 tools · read 2026-10-14
  • atlas_orient

    Discover canonical identity from an ordinary-language query — the entry point when no canonical id is held. Ranked: identity fields and sealed claims decide candidacy, Section text only when no identity field matches; ordered by identity…

  • atlas_cards

    Read 1-8 canonical ids as one ordered Card per id: identity, Hook, and sealed claims with source addresses. Set provenance=true to expand every cited source's Release-bound audit facts in the same atomic response.

  • atlas_read

    Read a complete Node (bare id: identity, hierarchy, Hook, and every Section; relationship occurrences are omitted), one Section ('node-id#section-slug'), one Decision record ('decision:<decision-id>'), or one exact glossary definition…

  • atlas_links

    Page one subject's relationship occurrences, outbound then inbound, each with direction, reference class, source Section, and the far end's Hook, plus its identity unless the class is 'undisclosed'.

  • atlas_navigate

    Read 'tree', the canonical ordered traversal of every published node, or 'tour', the publisher-curated first learning path.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "atlas": {
      "type": "http",
      "url": "https://agentic-atlas.dev/mcp/"
    }
  }
}

OpenAPI spec

14 paths, read 2026-10-14. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.