dev.agentic-atlas/atlas

Est-ce que dev.agentic-atlas/atlas est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.agentic-atlas/atlas » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• atlas_cards≈ 534 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • ids · array · requis
    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 · optionnel
    true also returns each cited source's content digest and publisher attestation (who, when), plus the Release's digests: a larger response.
  • expected_revision · ? · optionnel
    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.

  Exemple d'appel

  {"name": "atlas_cards", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "scope": {}, "coherence": "texte", "projection": "texte"}}

• atlas_links≈ 545 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • bound · integer · optionnel
    How many relationship occurrences this call returns; continue with cursor until the page is no longer truncated.
  • cursor · ? · optionnel
    scope.next_cursor from a prior atlas_links page; repeat the same other arguments.
  • subject · string · requis
    A bare Node id (no '#section'), e.g. an atlas_orient candidate id or a Card id.
  • expected_revision · ? · optionnel
    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.

  Exemple d'appel

  {"name": "atlas_links", "arguments": {"subject": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "scope": {}, "coherence": "texte", "projection": "texte"}}

• atlas_navigate≈ 407 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • view · string · optionnel · tree | tour
    Choose tree to survey every published Node in canonical order, or tour to follow the publisher's guided first learning path.
  • expected_revision · ? · optionnel
    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.

  Exemple d'appel

  {"name": "atlas_navigate", "arguments": {"view": "tree", "expected_revision": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "scope": {}, "coherence": "texte", "projection": "texte"}}

• atlas_orient≈ 864 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • kind · ? · optionnel
    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.
  • bound · integer · optionnel
    How many ranked candidates this call returns; raise it to compare more matches at once, and continue past it with cursor.
  • query · ? · optionnel
    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 characters also matches longer tokens it begins. Section text supplies direct candidates only when no subject matches an identity field. Node discovery also includes neighbors matching query terms through references in either direction; via explains the connection, and total counts the candidates. kind='decision' searches Decision ids, titles, and bodies; kind='term', keys and definitions. Empty lists every subject of the kind.
  • cursor · ? · optionnel
    scope.next_cursor from a prior atlas_orient page; repeat the same other arguments.
  • expected_revision · ? · optionnel
    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.

  Exemple d'appel

  {"name": "atlas_orient", "arguments": {"kind": "texte", "bound": 1, "query": "texte", "cursor": "texte", "expected_revision": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "scope": {}, "coherence": "texte", "projection": "texte"}}

• atlas_read≈ 471 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • address · string · requis
    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 · ? · optionnel
    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.

  Exemple d'appel

  {"name": "atlas_read", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "scope": {}, "coherence": "texte", "projection": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://agentic-atlas.dev/mcp/