Pathmark
NPM · PATHMARK · SCANNED SEP 20
Local-first intent and provenance for Codex, Claude Code, Cursor, Gemini CLI, and MCP agents.
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 → 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hacksurvivor/pathmark). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1657 tokens (~66/item across 25 items; 25 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 19% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_memory" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 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
How do I install the Pathmark MCP server?
Pathmark runs locally as an npm package, launched with npx -y pathmark. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pathmark
claude mcp add hacksurvivor-pathmark -- npx -y pathmark
{
"mcpServers": {
"hacksurvivor-pathmark": {
"command": "npx",
"args": [
"-y",
"pathmark"
]
}
}
} {
"servers": {
"hacksurvivor-pathmark": {
"command": "npx",
"args": [
"-y",
"pathmark"
]
}
}
} codex mcp add hacksurvivor-pathmark -- npx -y pathmark
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hacksurvivor-pathmark": {
"type": "local",
"command": [
"npx",
"-y",
"pathmark"
],
"enabled": true
}
}
} openclaw mcp add hacksurvivor-pathmark --command npx --arg -y --arg pathmark
mcp_servers:
hacksurvivor-pathmark:
command: "npx"
args: ["-y", "pathmark"] {
"McpServers": {
"hacksurvivor-pathmark": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pathmark"
]
}
}
} assistant mcp add hacksurvivor-pathmark -t stdio -c npx -a -y pathmark
{
"mcpServers": {
"hacksurvivor-pathmark": {
"command": "npx",
"args": [
"-y",
"pathmark"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
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/pathmark@0.1.15
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | hacksurvivor/pathmark |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hacksurvivor/pathmark/.github/workflows/publish.yml@refs/tags/v0.1.15 |
| Rekor log index | 2708438796 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:478f68d40f5dcb124bc5489a0e10c605f47de06ff71bb8db4b3e93f9637424f5b6d0b34379a862c2efd05ec1d4f63e1dc5710f6348a5fbc6be610d715 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
approve_conclusion Approve conclusion ~73
Approve one pending conclusion, optionally correcting its text or tags. The transition is atomic and auditable.
| Name | Type | Req | Description |
|---|---|---|---|
| decidedBy | string | – | – |
| id | string | yes | – |
| namespace | string | – | – |
| note | string | – | – |
| tags | array | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
ask_memory Ask memory ~70
Ask approved conclusions first, then scoped or explicitly requested raw evidence. Returns an answer, exact provenance, and a recallId for feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| namespace | string | – | – |
| question | string | yes | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
audit_memory Audit memory value ~57
Measure capture-to-recall behavior, unused records, recall age, duplicate rate, stale raw hits, and available precision evidence without changing memory.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| namespace | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
backup_memory Back up memory store ~29
Create a point-in-time copy of the canonical local JSONL store.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | – |
No output schema declared.
No examples provided.
chat Chat ~69
Chat with Pathmark using approved conclusions first and only scoped or explicitly requested raw fallback. Returns an answer, provenance, and recallId.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| namespace | string | – | – |
| question | string | yes | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
compact_memory Compact memory store ~65
Preview or apply exact deduplication, expired-record removal, retention, and deleted-record purging. Applied runs create a backup.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| dedupe | boolean | – | – |
| dropDeleted | boolean | – | – |
| retentionDays | integer | – | – |
No output schema declared.
No examples provided.
consolidate_memory Consolidate raw evidence ~108
Prepare a bounded unsynthesized evidence batch and, when server synthesis is configured, preview or stage evidence-backed conclusion proposals. Proposals are never auto-approved.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | Stage generated proposals as pending conclusions. |
| cursor | string | – | Continue after the last record id from a prior bounded batch. |
| days | integer | – | – |
| evidenceLimit | integer | – | – |
| maxProposals | integer | – | – |
| namespace | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
create_conclusion Create conclusion ~90
Propose a durable higher-signal conclusion. Approval is required by default before it can be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceIds | array | – | Raw memory IDs supporting this conclusion. Used for provenance and consolidation coverage. |
| expiresAt | string | – | – |
| namespace | string | – | – |
| source | string | – | – |
| tags | array | – | – |
| text | string | yes | Conclusion text to save. |
No output schema declared.
No examples provided.
delete_memory Delete memory ~25
Soft-delete a saved memory or conclusion by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
doctor_memory Diagnose memory store ~28
Report duplicate, deleted, expired, conclusion, invalid-record, and index health counts without changing data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
export_memory Export memory ~78
Export a scoped, mergeable JSONL bundle for another Pathmark installation or trusted sync transport.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| encrypted | boolean | – | Encrypt the export with PATHMARK_EXPORT_KEY. |
| includeDeleted | boolean | – | – |
| kind | string | – | – |
| namespace | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
get_config Get Pathmark configuration ~21
Show the local Pathmark Memory store location and enabled optional features.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_context Get context ~61
Return compact local memory context for a task or question.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| namespace | string | – | – |
| query | string | – | Task or question to retrieve context for. |
| tags | array | – | – |
No output schema declared.
No examples provided.
get_memory_snapshot Get approved memory snapshot ~47
Generate a bounded USER/PROJECT/AGENT snapshot from approved canonical conclusions only.
| Name | Type | Req | Description |
|---|---|---|---|
| charLimit | integer | – | – |
| namespace | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
list_conclusions List conclusions ~35
List saved durable conclusions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| namespace | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
list_pending_conclusions List pending conclusions ~56
List bounded approval-gated conclusion proposals. Pending records are never returned by normal memory search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| namespace | string | – | – |
| offset | integer | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
purge_memory Hard purge memory ~82
Preview or permanently remove matching records from the canonical store. A backup is created before an applied purge.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | – |
| confirm | boolean | – | False previews the purge; true applies it and creates a backup. |
| id | string | – | – |
| namespace | string | – | – |
| source | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
rate_recall Rate recalled memories ~67
Attach explicit relevance labels to one exact Pathmark recall so audit_memory can report measured precision.
| Name | Type | Req | Description |
|---|---|---|---|
| irrelevantIds | array | – | – |
| note | string | – | – |
| recallId | string | yes | The recallId returned by chat or ask_memory. |
| relevantIds | array | – | – |
No output schema declared.
No examples provided.
recall_memory Recall memory ~176
Transparent recall for any MCP-capable harness. Use this at task start or before answering to show exactly which memories were used.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Exact memory IDs from a prior Pathmark context block. Preserves the original visible-recall set. |
| includeRecords | boolean | – | Include a second, untruncated full-record copy alongside usedMemories. Defaults to false: it duplicates data already in context/usedMemories and is unbounded in size. Set true only when full record b… |
| kind | string | – | – |
| limit | integer | – | – |
| namespace | string | – | – |
| query | string | – | Task, repo, or question to retrieve memory for. Empty query returns recent records. |
| tags | array | – | Optional tags to scope visible recall, such as the current workspace tag. |
No output schema declared.
No examples provided.
reject_conclusion Reject conclusion ~49
Reject one pending conclusion while retaining it in the canonical audit trail and excluding it from recall.
| Name | Type | Req | Description |
|---|---|---|---|
| decidedBy | string | – | – |
| id | string | yes | – |
| note | string | – | – |
No output schema declared.
No examples provided.
remember Save raw evidence ~100
Save raw searchable evidence. Durable intent should use the approval-gated conclusion workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | – | Optional ISO timestamp after which recall excludes this memory. |
| namespace | string | – | Optional project, user, or client namespace. |
| source | string | – | Optional source label, such as repo, thread, or tool name. |
| tags | array | – | Optional lowercase-ish tags for later filtering. |
| text | string | yes | Memory text to save. |
No output schema declared.
No examples provided.
search_memory Search memory ~58
Search saved local memories and conclusions.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| namespace | string | – | – |
| query | string | – | Search query. Empty query returns recent records. |
| tags | array | – | – |
No output schema declared.
No examples provided.
session_trace Session trace ~76
Show a bounded chronological audit trail for one captured session: prompts, exact injected memory IDs, redacted tool inputs/results, and answers.
| Name | Type | Req | Description |
|---|---|---|---|
| includeOutputs | boolean | – | Include redacted bounded tool output previews. Defaults to true. |
| limit | integer | – | – |
| sessionId | string | yes | Exact Codex or harness session ID. |
No output schema declared.
No examples provided.
supersede_memory Supersede memory ~72
Replace an outdated memory with a linked current record while preserving history.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | – | – |
| id | string | yes | – |
| kind | string | – | – |
| namespace | string | – | – |
| source | string | – | – |
| tags | array | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
update_memory Update memory ~65
Correct an existing memory while preserving its prior versions in local history.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string|null | – | – |
| id | string | yes | – |
| namespace | string | – | – |
| source | string | – | – |
| tags | array | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
What is the Pathmark MCP server?
Pathmark is an MCP server listed in the public MCP registry as io.github.hacksurvivor/pathmark. Local-first intent and provenance for Codex, Claude Code, Cursor, Gemini CLI, and MCP agents. This page covers its npm package (pathmark).
Is the Pathmark MCP server safe to use?
Pathmark scores 87 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. Its build provenance is signed and verified. 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 Pathmark MCP server expose?
Pathmark exposes 25 tools: get_config, remember, create_conclusion, search_memory, get_context, and 20 more. Their descriptions and schemas cost roughly 1,657 tokens of context every time the server is loaded.
Is the Pathmark MCP server still maintained?
Pathmark 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 Pathmark MCP server under?
Pathmark declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.