dev.agentic-atlas/atlas
REMOTE · AGENTIC-ATLAS.DEV
Agent-design pattern guidance via 5 hosted read-only tools; Streamable HTTP, no auth, one Release.
Available components
Last scanned (4 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 6 Nov 2026.
Category AI and Machine Learning
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2006 tokens (~182/item across 11 items; 5 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- 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 →
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.
- 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
- 22 Oct 26 −6
- HTTPS: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- 21 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “atlas_orient” rewrote its description, which is the text the model reads security
- Server version: 1.0.13 → 1.1.0 functional
- “atlas_orient” reworded the description of “query” cosmetic
- 19 Oct 26 +1
- Server version: 1.0.11 → 1.0.13 functional
- “atlas_orient” dropped the optional parameter “status” cosmetic
- 17 Oct 26 −1
- Tool “atlas_cards” rewrote its description, which is the text the model reads security
- Tool “atlas_links” rewrote its description, which is the text the model reads security
- Tool “atlas_navigate” rewrote its description, which is the text the model reads security
- Tool “atlas_orient” rewrote its description, which is the text the model reads security
- Tool “atlas_read” rewrote its description, which is the text the model reads security
- Schema quality: 145 → 182 ▼ functional
- Resource “Consultation contract” was removed ▼ functional
- New resource “Agentic Atlas consultation contract” functional
- “atlas_cards” reworded the description of “expected_revision” cosmetic
- “atlas_cards” reworded the description of “ids” cosmetic
- “atlas_cards” reworded the description of “provenance” cosmetic
- “atlas_links” reworded the description of “bound” cosmetic
- “atlas_links” reworded the description of “expected_revision” cosmetic
- “atlas_links” reworded the description of “subject” cosmetic
- “atlas_navigate” reworded the description of “expected_revision” cosmetic
- “atlas_navigate” reworded the description of “view” cosmetic
- “atlas_orient” reworded the description of “bound” cosmetic
- “atlas_orient” reworded the description of “expected_revision” cosmetic
- “atlas_orient” reworded the description of “kind” cosmetic
- “atlas_orient” reworded the description of “query” cosmetic
- “atlas_orient” reworded the description of “status” cosmetic
- “atlas_read” reworded the description of “address” cosmetic
- “atlas_read” reworded the description of “expected_revision” cosmetic
- Tool “atlas_cards” changed its title: Read Atlas Cards → Get Atlas Summary Cards by ID cosmetic
- Tool “atlas_links” changed its title: Read Atlas Links → List an Atlas Node's Relationships cosmetic
- Tool “atlas_navigate” changed its title: Navigate the Atlas → Browse the Atlas Tree or Guided Tour cosmetic
- Tool “atlas_orient” changed its title: Orient in the Atlas → Search Atlas Nodes, Decisions, and Terms cosmetic
- Tool “atlas_read” changed its title: Read an Atlas Node or Section → Read an Atlas Node, Section, Decision, or Term cosmetic
- 10 Oct 26 +5
- Stability: fail → pass ▲ security
- 1 Oct 26 0
- Tool “atlas_cards” rewrote its description, which is the text the model reads security
- “atlas_cards” reworded the description of “ids” cosmetic
- “atlas_orient” made “query” optional cosmetic
- 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
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 6 Nov 2026 · Probed https://agentic-atlas.dev/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentic-atlas.dev | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6f6cf2a2004df7bf0e0de2c1318eb0d3 |
| SANs: agentic-atlas.dev, *.agentic-atlas.dev | ||||||
| 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 agentic-atlas.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| agentic-atlas.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentic-atlas.dev/mcp/ | Verified | 200 | |
| http (plaintext) | http://agentic-atlas.dev/mcp/ | Served over HTTP | 200 |
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 →
atlas_cards Get Atlas Summary Cards by ID ~219
Get one summary Card per Atlas Node id: its Hook (one-line summary) and the publisher's claims (thesis, law, when-to-reach, or claim), each citing its source Sections. Use when you hold ids and want their guidance without full text, such as to compare entries. Cards return in request order. Atomic: one unknown or Roadmap-only (unpublished) id refuses the whole batch as batch_not_atomic, naming the rejected ids.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_revision | – | – | Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release. |
| ids | array | yes | The Nodes to summarize, as bare ids (no '#section') such as atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order. |
| provenance | boolean | – | true also returns each cited source's content digest and publisher attestation (who, when), plus the Release's digests: a larger response. |
| Name | Type | Req | Description |
|---|---|---|---|
| coherence | string | yes | – |
| data | object | yes | cards, one per requested id in request order: id, title, kind, hook, and claims (id, text, field, sources as 'node-id#section-slug'). With provenance=true, also provenance: release (version and diges… |
| projection | – | yes | – |
| scope | object | yes | – |
No examples provided.
atlas_links List an Atlas Node's Relationships ~239
List where one Atlas Node references other entries (outbound) and where they reference it (inbound), outbound first. Use to find related entries or what points at this one. Each occurrence gives direction, class, source Section, and the far end's Hook (one-line summary), plus its id and title unless the class is 'undisclosed' (unpublished and unannounced). Results are paged: follow the cursor to the end before concluding nothing points here. An unknown or Roadmap-only (unpublished) subject is refused as invalid_argument.
| Name | Type | Req | Description |
|---|---|---|---|
| bound | integer | – | How many relationship occurrences this call returns; continue with cursor until the page is no longer truncated. |
| cursor | – | – | scope.next_cursor from a prior atlas_links page; repeat the same other arguments. |
| expected_revision | – | – | Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release. |
| subject | string | yes | A bare Node id (no '#section'), e.g. an atlas_orient candidate id or a Card id. |
| Name | Type | Req | Description |
|---|---|---|---|
| coherence | string | yes | – |
| data | object | yes | links: per occurrence, class ('in-slice', 'roadmap-disclosed', 'undisclosed'), direction, occurrence (section slug, ordinal), the far end's target id and title unless undisclosed, and its hook. |
| projection | – | yes | – |
| scope | object | yes | – |
No examples provided.
atlas_navigate Browse the Atlas Tree or Guided Tour ~151
Browse the whole Atlas in the publisher's order: the canonical tree of every published Node, or the guided first learning path, an introduction then steps each naming a Node id with narration. Use to survey what exists or to start learning with no topic in mind. Neither view carries entry text or claims; the tour is null if none is published.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_revision | – | – | Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release. |
| view | string | – | Choose tree to survey every published Node in canonical order, or tour to follow the publisher's guided first learning path. |
| Name | Type | Req | Description |
|---|---|---|---|
| coherence | string | yes | – |
| data | object | yes | tree: tree entries (id, title, depth). tour: path (id, title, intro, steps of node id, narration), or null when the Release seals no tour. |
| projection | – | yes | – |
| scope | object | yes | – |
No examples provided.
atlas_orient Search Atlas Nodes, Decisions, and Terms ~410
Find Atlas entries by topic when you hold no id; an id you already hold can be read directly. Searches Nodes (patterns, concepts, examples) and Roadmap entries (announced, unpublished); kind narrows it to one Node kind, Decisions, or glossary terms. Node discovery preserves leading lexical matches and adds related entries with task vocabulary, using references in either direction. Related candidates explain their connection; direct matches have no via. Empty listings and exact id/title lookups stay lexical. Returns ranked ids with Hooks (one-line summaries; a term's is its whole definition), paged with a cursor. A miss is an empty page; invalid arguments are refused as invalid_argument.
| Name | Type | Req | Description |
|---|---|---|---|
| bound | integer | – | How many ranked candidates this call returns; raise it to compare more matches at once, and continue past it with cursor. |
| cursor | – | – | scope.next_cursor from a prior atlas_orient page; repeat the same other arguments. |
| expected_revision | – | – | Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release. |
| kind | – | – | Narrows the search to one Node kind, to Decision records, or to glossary terms. Omit it to search every Node kind plus Roadmap entries (announced, unpublished); setting it leaves Roadmap entries out. |
| query | – | – | A topic or question in ordinary design vocabulary. Lexical matches use canonical ids, titles, Hooks, claims, then Section headings and bodies, with rarer words weighing more; a word of four or more c… |
| Name | Type | Req | Description |
|---|---|---|---|
| coherence | string | yes | – |
| data | object | yes | candidates, ranked. A Node candidate has id, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook. A related Node… |
| projection | – | yes | – |
| scope | object | yes | – |
No examples provided.
atlas_read Read an Atlas Node, Section, Decision, or Term ~199
Read the full text at one exact Atlas address. A bare Node id returns the whole entry: identity, tree position, Hook (one-line summary), and every Section; relationship occurrences are omitted. A Section, Decision, or glossary term address returns that one item. Use when a summary is not enough or you need exact wording to cite. An unknown or malformed address is refused as invalid_argument; a wrong slug's refusal lists the real ones.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A bare Node id, 'node-id#section-slug', 'decision:<decision-id>', or 'term:<key>'. Slugs are not guessable: read them off a Node's sections, a Card claim's sources, or a Link's occurrence. |
| expected_revision | – | – | Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release. |
| Name | Type | Req | Description |
|---|---|---|---|
| coherence | string | yes | – |
| data | object | yes | node: identity (id, title, kind), hierarchy (ancestors, sibling_position, sibling_count), hook, and sections (slug, heading, position, content). section: section. decision: decision (id, title, conte… |
| projection | – | yes | – |
| scope | object | yes | – |
No examples provided.
How do I install the dev.agentic-atlas/atlas MCP server?
dev.agentic-atlas/atlas is a hosted endpoint at https://agentic-atlas.dev/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 · agentic-atlas.dev
claude mcp add --transport http dev-agentic-atlas-atlas 'https://agentic-atlas.dev/mcp/'
What is the dev.agentic-atlas/atlas MCP server?
dev.agentic-atlas/atlas is an MCP server listed in the public MCP registry as dev.agentic-atlas/atlas. Agent-design pattern guidance via 5 hosted read-only tools; Streamable HTTP, no auth, one Release. This page covers its hosted endpoint (https://agentic-atlas.dev/mcp/).
Is the dev.agentic-atlas/atlas MCP server safe to use?
dev.agentic-atlas/atlas scores 82 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 dev.agentic-atlas/atlas MCP server expose?
dev.agentic-atlas/atlas exposes 5 tools: atlas_orient, atlas_cards, atlas_read, atlas_links, atlas_navigate. Their descriptions and schemas cost roughly 1,218 tokens of context every time the server is loaded.
Does the dev.agentic-atlas/atlas MCP server require authentication?
No. We connected to dev.agentic-atlas/atlas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.agentic-atlas/atlas MCP server still maintained?
dev.agentic-atlas/atlas is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the dev.agentic-atlas/atlas MCP server?
VerifyMCP ran 14 checks on dev.agentic-atlas/atlas, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.