Do design work with Agentic Atlas over hosted MCP at agentic-atlas.dev/mcp/.
Three skills — audit an existing agent artifact, design a new agent system, apply one named pattern — over two read-only agents; no SDK, CLI, local server, or content bundle is installed.
https://agentic-atlas.dev/mcp/Consult one active Agentic Atlas Release. Every tool addresses its payload directly: call with the canonical ids you already know, for any exact canonical address, and only when you do not yet have an identity. Node discovery keeps its leading lexical matches and adds neighbors sharing query terms through inbound and outbound references. A candidate's via identifies its seed, reference direction, and source Section; an absent via means a direct match. Judge every candidate against the task before requesting its Card; total counts the candidates. For a broad design or review, query each distinct concern and check for missing concepts as well as mechanisms. Empty listings, exact id/title lookups, Decisions, and terms do not expand. A complete Node from is prose alone; its relationships come from . Carry the coherence marker each payload returns as expected_revision on every later call, so a promotion is refused rather than silently crossed. Use for the canonical tree or the publisher-curated tour. Every payload's scope.omitted_fact_classes names what it withheld; each class has one fixed recovery: claims via , sections via , and links via , each addressed at the subject in hand; provenance via with the subject id and provenance=true; decisions via with query='' and kind='decision', then a single decision via at the returned 'decision:<decision-id>' address; terms via with kind='term', then optionally at the returned 'term:<key>' address. A definition read names that term: subject and declares no omitted fact classes. A truncated collection returns scope.next_cursor; continue it by repeating the same call with cursor.
3 in the Claude listing