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.

io.github.pathmodeio/mcp-server

NPM · @PATHMODE/MCP-SERVER · SCANNED SEP 20

Deterministic intent preflight before your agent builds: six gates, keyless, no model call.

0 this week 71 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 39 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • 63% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2020 tokens (~168/item across 12 items; 9 tools + 3 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 Management20
  • Stability check failed: the tool surface changed between 1.6.0 and 1.31.2: 14 tool removals, 0 breaking changes, 3 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
Install

How do I install the io.github.pathmodeio/mcp-server server?

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

npm · @pathmode/mcp-server

# add to Claude Code
claude mcp add pathmodeio-mcp-server -- npx -y @pathmode/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "pathmodeio-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@pathmode/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pathmodeio-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@pathmode/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add pathmodeio-mcp-server -- npx -y @pathmode/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pathmodeio-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pathmode/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pathmodeio-mcp-server --command npx --arg -y --arg @pathmode/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  pathmodeio-mcp-server:
    command: "npx"
    args: ["-y", "@pathmode/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pathmodeio-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pathmode/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add pathmodeio-mcp-server -t stdio -c npx -a -y @pathmode/mcp-server
// mcp.json
{
  "mcpServers": {
    "pathmodeio-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@pathmode/mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1
    • Stability: fail → unverified security
    • Tool safety: pass → unverified security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 63 → unverified functional
    • Package version: 1.31.1 → 1.31.2 functional
  • 19 Sept 26 0
    • Stability: fail → unverified security
    • Tool safety: pass → unverified security
    • Schema quality: 149 → 168 functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 63 → unverified functional
    • Package version: 1.30.0 → 1.31.1 functional
    • Package version: 1.30.0 → 1.31.0 functional
  • 18 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: fail → unverified security
    • Tool safety: pass → unverified security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 63 → unverified functional
    • Package version: 1.28.0 → 1.30.0 functional
  • 15 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 +15
    • Malware scan: unverified → pass security
  • 12 Sept 26 +11
    • Stability: fail → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: unverified → pass security
    • Known CVEs: unverified → pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 63 → unverified functional
    • Dependency health: unverified → 0.81 functional
    • Package version: 1.27.4 → 1.28.0 functional
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 20 Sept 2026 · Analysed npm/@pathmode/mcp-server@1.31.2

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 →

Dependencies 105 packages
Packages resolved 105
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,667 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
check_intent_readiness ~242

Run the deterministic preflight on an intent spec before handing it to an implementation agent. Six calibrated checks — title, objective, outcomes, constraints, edge cases, verification — computed by pure functions: no model call, no network, the same spec always gets the same verdict. Pass a spec inline to check before saving, pass intentId to check a specific saved intent, or pass nothing to resolve the repo-bound intent.md from MCP workspace roots or the launch directory. When the repository has no intent.md, or cannot be identified, it refuses rather than grading an unrelated intent; pass intentId to check a specific saved one. A failing verdict names the exact blockers; repair the fields and re-run. This is the gate that runs at preflight.pathmode.io.

NameTypeReqDescription
intentIdstringCheck a specific saved intent by id. Ignored when spec is passed.
specobjectCheck this spec directly (before saving). When omitted, resolve the repo-bound intent.md from MCP roots or cwd. A repository with no intent.md is refused, not answered with the workspace current inte…

No output schema declared.

No examples provided.

confirm_intent_dimension ~408

Resolve an "unconfirmed" readiness dimension, in a local intent.md or in a connected workspace. Use this when check_intent_readiness reports that it READ your objective or outcomes but could not confirm them: the gate matches a fixed English vocabulary and misses valid phrasing, including other languages. confirm: state who is affected and what goes wrong for them, in your own words, and the dimension passes. waive: mark the dimension as not applicable to this change (a pure refactor has no product outcome). A waiver is a HUMAN decision, so set humanApproved only after the user has explicitly agreed. Waivers are local-mode only: a workspace will not accept one over an API key, which authenticates as a machine. The confirmation is bound to the exact text it was made against and dies automatically if that text is edited. You cannot confirm a dimension the gate read nothing for; write the field first, save, then confirm.

NameTypeReqDescription
actionstringyesconfirm: vouch that the text names what the gate could not find. waive: this dimension does not apply to this change.
actorstringconfirm + objective: who is affected, in your words.
dimensionstringyesOnly these two are confirmable. Title and verification are never waivable.
humanApprovedbooleanwaive only. Set ONLY after the user has explicitly approved the waiver. Recorded as a human decision that this environment cannot verify.
intentIdstringCloud mode: confirm on a specific saved intent. Defaults to the current intent.
observablestringconfirm + outcomes: how you would see it.
outcomestringconfirm + outcomes: the observable change.
pathstringLocal mode only: path to the intent file. Defaults to intent.md.
problemstringconfirm + objective: what goes wrong for them today.
reasonstringwaive: why this dimension does not apply.

No output schema declared.

No examples provided.

get_current_intent ~183

Get the currently active intent, preferring approved intents with real objective/outcome content over empty stubs. Returns the full IntentSpec plus an evidenceSummary (how many evidence items it cites by ID, across all trust tiers; tier counts come with include_evidence=true). Evidence is referenced by ID; pass include_evidence=true to inline the evidence content grouped by trust tier (backing, unreviewed, assumption) with per-tier counts, or call get_agent_prompt for the full evidence-backed execution prompt.

NameTypeReqDescription
include_evidencebooleanInline the actual evidence items (truncated) this intent cites, grouped by trust tier with an evidenceTiers count. Default false — the default response carries only a fetch-free evidenceSummary to ke…
statusstringFilter by status: draft, validated, approved, shipped, verified

No output schema declared.

No examples provided.

get_intent ~62

Get a single intent by ID with full details including objective, outcomes, constraints, edge cases, and relations. Evidence is referenced by ID; call get_agent_prompt for the full evidence-backed execution prompt.

NameTypeReqDescription
intentIdstringyesThe intent ID to fetch

No output schema declared.

No examples provided.

intent_export ~179

Export an intent spec as .cursorrules, a CLAUDE.md or AGENTS.md section, a Claude Managed Agents Outcomes rubric, or an OpenSpec change folder. Use agents-md for Codex, Cursor, and other AGENTS.md-aware agents. Use openspec to hand the intent to an OpenSpec workflow: it writes proposal.md, a spec delta, and the verification contract in tasks.md, placed where the preflight reader finds them, and never writes into an existing change.

NameTypeReqDescription
formatstringyesExport format
pathstringOutput file path relative to the project root. Must stay inside the project (absolute paths and ".." are rejected). Defaults to .cursorrules, CLAUDE.md, AGENTS.md, or openspec/changes/<change-id>
specobjectyes

No output schema declared.

No examples provided.

intent_import ~217

Adopt an existing OpenSpec change as the Pathmode intent record. Reads the change folder exactly as the preflight does (proposal.md, spec deltas, design non-goals, verification in tasks.md) and saves it as intent.md — with a workspace key, also as a workspace intent. The change folder is NEVER modified, and field text travels verbatim, so never retype fields from the change yourself. After importing, resolve any unconfirmed dimensions with confirm_intent_dimension.

NameTypeReqDescription
intentPathstringWhere the intent file is written. Defaults to intent.md.
overwritebooleanReplace the intent file even when it already holds a DIFFERENT intent. Default false — refused instead.
pathstringOpenSpec change directory, e.g. openspec/changes/add-export. When omitted the repo is scanned: exactly one active change imports directly; several returns the list to pick from.
productIdstringCloud mode: the product this intent belongs to, when the workspace asks for one.

No output schema declared.

No examples provided.

intent_save ~268

Save an intent spec to intent.md in the project root — the default choice when you are working inside a repository. With a Pathmode API key set it ALSO creates or updates the intent in the workspace and records the sync in the file, so the file is the projection of the record rather than a second copy of it. Re-saving the same intent bumps its version and preserves its status; it never silently replaces a different intent. Use create_intent instead when there is no repository to write into.

NameTypeReqDescription
baseRepoBodyRevisionstringExact base revision carried by the change request. Requires changeRequestId.
changeRequestIdstringStructured PM request this save deliberately applies. Requires baseRepoBodyRevision.
localDraftbooleanSave an unconnected local draft, even with an API key. Use before repository adoption. Cannot detach an already connected file or apply a change request.
overwritebooleanReplace the file even when it already holds a DIFFERENT intent. Default false — the save is refused instead, so an unrelated spec is never clobbered.
pathstringFile path relative to the project root. Must stay inside the project (absolute paths and ".." are rejected). Defaults to intent.md
specobjectyes

No output schema declared.

No examples provided.

list_intents ~51

List all intents in the workspace. Returns an array of IntentSpecs with their status, objectives, and metadata.

NameTypeReqDescription
statusstringFilter by status: draft, validated, approved, shipped, verified

No output schema declared.

No examples provided.

search_intents ~57

Search intents by keyword. Searches across user goals, objectives, outcomes, and constraints.

NameTypeReqDescription
querystringyesSearch keyword or phrase
statusstringFilter by status: draft, validated, approved, shipped, verified

No output schema declared.

No examples provided.

Common questions

What is the io.github.pathmodeio/mcp-server server?

io.github.pathmodeio/mcp-server is listed in the public MCP registry as io.github.pathmodeio/mcp-server. Deterministic intent preflight before your agent builds: six gates, keyless, no model call. This page covers its npm package (@pathmode/mcp-server).

Is the io.github.pathmodeio/mcp-server server safe to use?

io.github.pathmodeio/mcp-server scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.pathmodeio/mcp-server server expose?

io.github.pathmodeio/mcp-server exposes 9 tools: get_current_intent, list_intents, get_intent, search_intents, check_intent_readiness, and 4 more. Their descriptions and schemas cost roughly 1,667 tokens of context every time the server is loaded.

Is the io.github.pathmodeio/mcp-server server still maintained?

io.github.pathmodeio/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.pathmodeio/mcp-server server under?

io.github.pathmodeio/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.