Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Athenode

NPM · @ATHENODE/CLI

Spec-driven development for AI coding agents: specs, skills, agents, rules and MCP servers.

Available components

+4 this week 71 Trust /100

Last scanned (15 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 39 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 15625 tokens (~248/item across 63 items; 63 tools + 0 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
Tool Safety98
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "library_merge_preview" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +5
    • Stability: fail → pass ▲ security
  • 19 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 75 to 69.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 55 to 58.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 38 to 42.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 32 to 35.

Diagnostics

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 21 Nov 2026 · Analysed npm/@athenode/cli@0.10.7

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 115 packages
Packages resolved 115
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 63 exposed · ~15,161 tokens

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 →

Tool Tokens
specs_qa_add ~56

Add a question to a specification. `question` is a single string, so put any answer options inside it as Markdown.

NameTypeReqDescription
questionstringyesQuestion text (Markdown).
specificationIdstringyesSpecification id.

No output schema declared.

No examples provided.

specs_qa_answer ~49

Answer a question previously added to a specification.

NameTypeReqDescription
answerstringyesThe answer text.
questionIdstringyesQuestion id.
specificationIdstringyesSpecification id.

No output schema declared.

No examples provided.

specs_qa_list ~48

List the questions and answers of a specification; an unanswered question has a null `answer`. Returns an array ({items} in structuredContent).

NameTypeReqDescription
specificationIdstringyesSpecification id.

No output schema declared.

No examples provided.

specs_search ~89

Flat search over the project's specifications: matches only, without ancestors or filters. The query must not be empty. Each match's `snippet` holds the matched text when the server found the match by meaning, and is otherwise null or absent. Prefer specs_tree with `query` for matches nested with their ancestors. Returns an array ({items} in structuredContent).

NameTypeReqDescription
querystringyesSearch text.

No output schema declared.

No examples provided.

specs_set_plan ~67

Set the implementation plan of a specification; this overwrites any previous plan, and `plan: null` clears it (CLI: --plan / --clear-plan).

NameTypeReqDescription
idstringyesSpecification id.
planstring|nullyesPlan text, or null to clear it.

No output schema declared.

No examples provided.

specs_set_status ~42

Set the status of a specification (draft | prepared | processing | completed).

NameTypeReqDescription
idstringyesSpecification id.
statusstringyesNew status.

No output schema declared.

No examples provided.

specs_tree ~419

Fetch specifications as a tree, in one of four modes. Default: the subtree rooted at `id`. `branch`: a single chain from the top-level ancestor down to `id`, which is the deepest node. `query`: ranked search matches (at most 20) nested with their ancestors in one call, so there is no need to walk specs_list; `id` optionally scopes matches to its direct children; a match's `snippet` holds the matched text when the server found the match by meaning, and is otherwise null or absent; if a query finds little, retry with other wording. `executionOrder`: the unfiltered subtree under `id` plus the order in which its leaves can be implemented and the blockers holding them back. Only prepared/processing leaves are planned; draft leaves count as unprepared blockers. A root without children is its own only candidate, so call it on a leaf to get that leaf's blockers. Leaves inherit blockers from their ancestors up to and including the root. A cycle yields an empty order instead of an error. The result is a consistent one-time snapshot. `status` (draft | prepared | processing | completed) prunes branches without a matching node. Mode rules (errors use CLI flags): --execution-order requires an id and cannot combine with --branch, --query or --status; --query and --branch are exclusive and the query must not be empty; --branch cannot combine with --status. Returns an array of nodes, or `{tree, plan}` with executionOrder.

NameTypeReqDescription
branchboolean–Ancestor chain mode (CLI: --branch).
executionOrderboolean–Execution order mode (CLI: --execution-order).
idstring–Root specification id (optional only in query mode).
includeContentboolean–Include each node's content (CLI: --include-content).
querystring–Search mode (CLI: --query).
statusstring–Keep nodes with this status or a matching descendant (CLI: --status).

No output schema declared.

No examples provided.

specs_update ~243

Update a specification; only supplied fields change, and `null` clears `summary`, `content` or `parentId` (CLI: --clear-summary, --clear-content, --clear-parent). `blockedBy` adds to the existing blockers, never replacing them; it is a second request, and its failure reports in `patchApplied` whether the field update was saved. Adding is all-or-nothing. A blocker that is missing, in another project, the spec itself, already completed, or an ancestor or descendant is rejected with 400; a link that already exists or would create a cycle with 409, so remove wrong links before adding new ones. Children inherit their ancestors' blockers.

NameTypeReqDescription
blockedByarray–Ids to add as blockers (CLI: --blocked-by, repeatable).
contentstring|null–New content; null clears it.
idstringyesSpecification id.
parentIdstring|null–New parent id; null clears it (CLI: --parent / --clear-parent).
summarystring|null–New summary; null clears it.
titlestring–New title.

No output schema declared.

No examples provided.

todos_create ~369

Create a ToDo card. Every card starts `open` (a project token creates it with source `agent`), so there is no status parameter. `type` defaults to `idea` and `priority` to `medium`. `questions` gives the card up to 3 open questions, and only when a decision that only the user can make blocks the card; this is the only way for an agent to add a question, since there is no tool to add one to an existing card. The Free plan's card limit is reported as a plan-limit error.

NameTypeReqDescription
descriptionstring–Card description, at most 10000 characters.
originSpecificationIdstring–Specification whose work the card came out of (CLI: --origin-specification).
prioritystring–Card priority (low | medium | high); default medium.
questionsarray–Open questions of the card, at most 3; each is one string, Markdown, with its answer options inside the text (CLI: --question, repeatable). A card's open questions are decisions to make before it is…
titlestringyesCard title, at most 200 characters.
typestring–Card type (follow-up | tech-debt | bug | idea); default idea.

No output schema declared.

No examples provided.

todos_get ~84

Get one ToDo card by id, with its `status`, its `resultingSpecificationId` (null until the card is converted into a specification) and its `questions`: the card's open questions, each with its `answer` (null while unanswered). A 403 can also mean that no such card exists.

NameTypeReqDescription
idstringyesToDo card id.

No output schema declared.

No examples provided.

todos_list ~152

List the project's ToDo cards. Without `status` only `open` cards are returned; closed cards (`done`, `dismissed`) only when asked for. `specificationId` keeps the cards whose origin or resulting specification is that one. Rows are full cards including `description` and `questions` (each card's open questions with their answers), ordered by priority, then newest. Returns an array ({items} in structuredContent).

NameTypeReqDescription
specificationIdstring–Only cards whose origin or resulting specification is this id (CLI: --specification).
statusarray–Statuses to return (open | done | dismissed); omitted or empty means open (CLI: --status, repeatable).

No output schema declared.

No examples provided.

todos_qa_answer ~124

Record the answer to one unanswered open question of a ToDo card; the question ids come with the card (`questions` of `todos_get` and `todos_list`). A project token cannot change an existing answer: answering a question that already has one is refused with 403. A question id that does not belong to the card is a 404. A 403 can also mean that no such card exists.

NameTypeReqDescription
answerstringyesThe answer text.
idstringyesToDo card id.
questionIdstringyesQuestion id.

No output schema declared.

No examples provided.

todos_set_status ~144

Set the status of a ToDo card (open | done | dismissed). A project token may only close an `open` card, as `done` (carried out, with or without a resulting specification) or `dismissed` (closed without being carried out); reopening a card and moving it between `done` and `dismissed` are refused with 403. Repeating the closed status a card already has succeeds unchanged. A 403 can also mean that no such card exists.

NameTypeReqDescription
idstringyesToDo card id.
statusstringyesNew status; a project token may only set done or dismissed, on an open card.

No output schema declared.

No examples provided.

Install

How do I install the Athenode MCP server?

Athenode runs locally as an npm package, launched with npx -y @athenode/cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @athenode/cli

# add to Claude Code
claude mcp add com-athenode-cli -- npx -y @athenode/cli mcp
Common questions

What is the Athenode MCP server?

Athenode is an MCP server listed in the public MCP registry as com.athenode/cli. Spec-driven development for AI coding agents: specs, skills, agents, rules and MCP servers. This page covers its npm package (@athenode/cli).

Is the Athenode MCP server safe to use?

Athenode scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 Athenode MCP server expose?

Athenode exposes 63 tools: specs_list, specs_search, specs_tree, specs_get, specs_create, and 58 more. Their descriptions and schemas cost roughly 15,161 tokens of context every time the server is loaded.

Is the Athenode MCP server still maintained?

Athenode is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Athenode MCP server under?

Athenode declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Athenode MCP server?

VerifyMCP ran 15 checks on Athenode, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Athenode: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.