io.github.pathmodeio/mcp-server
NPM · @PATHMODE/MCP-SERVER · SCANNED AUG 3
Build intent specs via Socratic AI conversation. Connect to your Intent Layer for context.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 42 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- 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
- Tool/resource definitions use about 1759 tokens (~76/item across 23 items; 20 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @pathmode/mcp-server
claude mcp add pathmodeio-mcp-server -- npx -y @pathmode/mcp-server
codex mcp add pathmodeio-mcp-server -- npx -y @pathmode/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pathmodeio-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@pathmode/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add pathmodeio-mcp-server --command npx --arg -y --arg @pathmode/mcp-server
mcp_servers:
pathmodeio-mcp-server:
command: "npx"
args: ["-y", "@pathmode/mcp-server"] {
"mcpServers": {
"pathmodeio-mcp-server": {
"command": "npx",
"args": [
"-y",
"@pathmode/mcp-server"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +41
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 63 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 +17
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −43
- Malware scan: pass → unverified ▼ security
- Schema quality: 63 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Jul 26 49
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@pathmode/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 105 packages
105 packages in the resolved dependency tree · 105 deprecated · 37 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_intent_graph Analyze Intent Graph ~65
Analyze the intent dependency graph for risks and strategic insights. Returns critical path, cycles, bottlenecks, orphans, status mismatches, and stalled intents.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | string | — | Type of analysis: full (default), critical-path, risks, or status distribution |
No output schema declared.
No examples provided.
create_evidence Create Evidence ~190
Create a new evidence item (e.g., a discovered bug, user feedback quote, behavioral observation, or feature request). Evidence can later be linked to intents to support prioritization.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The evidence content — a finding, quote, or observation |
| productId | string | yes | Product (Space) ID this evidence belongs to |
| sentiment | string | — | Emotional sentiment |
| severity | string | — | Severity level (required for friction type) |
| source | string | — | Where this evidence came from (e.g., "User interview", "Bug report", "Support ticket") |
| sourceUrl | string | — | URL to the original source |
| stage | string | — | Workflow stage (e.g., "Discovery", "Checkout") |
| tags | array | — | Category tags (e.g., ["Onboarding", "Performance"]) |
| type | string | yes | Type of evidence |
No output schema declared.
No examples provided.
create_intent Create Intent ~190
Create a new intent spec in the workspace. Requires at minimum a title, objective, and productId. Returns the created intent with its ID. Use list_intents first to see existing intents and avoid duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | — | Hard limits the implementation must respect |
| edgeCases | array | — | Failure modes and boundary conditions |
| healthMetrics | array | — | What to monitor after shipping |
| objective | string | yes | Why this matters — the problem and who has it |
| outcomes | array | — | Observable, testable state changes |
| problemSeverity | string | — | How severe the problem is |
| productId | string | yes | Product (Space) ID this intent belongs to. Use get_workspace to find product IDs. |
| title | string | yes | Short name for the intent (e.g., "Improve onboarding flow") |
| verification | object | — | How to confirm it works |
No output schema declared.
No examples provided.
export_context Export Context ~193
Export workspace context as a formatted file. Use "claude-md" for CLAUDE.md (full workspace context), "cursorrules" for Cursor AI rules, "intent-md" for a single intent specification file, or "outcome-rubric" for a Claude Managed Agents Outcomes rubric (writer description + evidence-forcing grader rubric) derived from the resolved intent, its implementation context, and the workspace constitution. For cursorrules/intent-md/outcome-rubric, product context is always derived from the resolved intent. For claude-md, pass productId to select a specific product, otherwise the first active product is used.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Export format |
| intentId | string | — | Intent ID (optional, for cursorrules and intent-md) |
| productId | string | — | Product ID (optional, only used for claude-md format to select a specific product) |
No output schema declared.
No examples provided.
get_agent_prompt Get Agent Prompt ~72
Get a formatted execution prompt for a specific intent. This is the full structured prompt including objective, outcomes, constraints, edge cases, and verification steps.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | yes | The intent ID to generate a prompt for |
| mode | string | — | draft = critique the spec, execute = implement it |
No output schema declared.
No examples provided.
get_constitution Get Constitution ~26
Get the workspace constitution rules. These are mandatory constraints that all implementations must respect.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_current_intent Get Current Intent ~67
Get the currently active intent, preferring approved intents with real objective/outcome content over empty stubs. Returns the full IntentSpec with objective, outcomes, constraints, and edge cases.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | — | Filter by status: draft, validated, approved, shipped, verified |
No output schema declared.
No examples provided.
get_intent Get Intent ~44
Get a single intent by ID with full details including objective, outcomes, constraints, edge cases, and relations.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | yes | The intent ID to fetch |
No output schema declared.
No examples provided.
get_intent_relations Get Intent Relations ~46
Get the dependency graph for a specific intent. Shows what it depends on, enables, or blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | yes | The intent ID to get relations for |
No output schema declared.
No examples provided.
get_workspace Get Workspace ~31
Get workspace details including strategy (vision, non-negotiables, architecture principles), active products, and constitution rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
intent_export ~77
Export an intent spec as .cursorrules, a CLAUDE.md section, or a Claude Managed Agents Outcomes rubric for AI agent consumption.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Export format |
| path | string | — | Output file path. Defaults to .cursorrules or CLAUDE.md |
| spec | object | yes | — |
No output schema declared.
No examples provided.
intent_save ~52
Save an intent spec to intent.md in the project root. Called after building a spec through conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | — | File path relative to cwd. Defaults to intent.md |
| spec | object | yes | — |
No output schema declared.
No examples provided.
link_evidence Link Evidence to Intent ~76
Link or unlink evidence items to/from an intent. Linking evidence to intents establishes traceability between user problems and planned solutions.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | yes | The intent ID to link evidence to |
| link | array | — | Evidence IDs to link to this intent |
| unlink | array | — | Evidence IDs to unlink from this intent |
No output schema declared.
No examples provided.
list_intents List Intents ~51
List all intents in the workspace. Returns an array of IntentSpecs with their status, objectives, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | — | Filter by status: draft, validated, approved, shipped, verified |
No output schema declared.
No examples provided.
log_implementation_note Log Implementation Note ~61
Record a technical decision or implementation note for an intent. Use this to document why you chose a specific approach.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | yes | The intent ID to attach the note to |
| note | string | yes | The implementation note or technical decision |
No output schema declared.
No examples provided.
query_evidence Query Evidence ~128
Search evidence items (friction points, user quotes, observations, metrics, feature requests) by product, type, severity, or text. Returns matching evidence with IDs that can be linked to intents.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results (default 50, max 200) |
| productId | string | — | Filter by product (Space) ID |
| search | string | — | Text search across evidence content |
| severity | string | — | Filter by severity |
| tags | string | — | Comma-separated tags to filter by |
| type | string | — | Filter by evidence type |
No output schema declared.
No examples provided.
search_intents Search Intents ~57
Search intents by keyword. Searches across user goals, objectives, outcomes, and constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keyword or phrase |
| status | string | — | Filter by status: draft, validated, approved, shipped, verified |
No output schema declared.
No examples provided.
update_intent Update Intent ~132
Update an existing intent's content. Provide only the fields you want to change. Does NOT change intent status (use update_intent_status for that).
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | — | Replace all constraints |
| edgeCases | array | — | Replace all edge cases |
| healthMetrics | array | — | Replace all health metrics |
| intentId | string | yes | The intent ID to update |
| objective | string | — | Updated objective |
| outcomes | array | — | Replace all outcomes |
| problemSeverity | string | — | — |
| title | string | — | New title |
| verification | object | — | Replace verification plan |
No output schema declared.
No examples provided.
update_intent_status Update Intent Status ~82
Update the status of an intent. Use this to mark an intent as shipped after implementation, or verified after testing. For shipped/verified transitions, the response includes a verification checklist of outcomes, constitution rules, and health metrics that should be confirmed.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | yes | The intent ID to update |
| status | string | yes | The new status |
No output schema declared.
No examples provided.
verify_implementation Verify Implementation ~99
AI-grade your implementation against the intent spec. Checks each outcome, constraint, constitution rule, and edge case. Returns pass/fail per item with reasoning and an overall score. Also logs the result as an implementation note.
| Name | Type | Req | Description |
|---|---|---|---|
| codeChanges | string | — | Summary of code changes (file list, key modifications) |
| intentId | string | yes | The intent ID to verify against |
| summary | string | yes | Description of what was implemented and how |
No output schema declared.
No examples provided.