io.github.dcostenco/prism-coder
NPM · PRISM-MCP-SERVER
Session memory for coding agents: local-first recall, drift detection, on-device inference.
Available components
Last scanned (5 hours ago)
Scores higher than 93% of npm servers
Category Memory and Knowledge
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 Security86
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 47 of 227 dependencies flagged as unhealthy (4 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dcostenco/prism-coder). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13308 tokens (~251/item across 53 items; 53 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (2% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deep_storage_purge" implies "purge" 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 54 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −2
- Stability: pass → 0.83 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 20.22.3 → 20.22.4 functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Package version: 20.22.2 → 20.22.3 functional
- 19 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Oct 26 +11
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.92 ▲ functional
- First check of Tool coverage: 2 functional
- Package version: 20.21.27 → 20.22.2 functional
- Package version: 20.21.27 → 20.22.0 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 5 Nov 2026 · Analysed npm/prism-mcp-server@20.22.4
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 | dcostenco/prism-coder |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dcostenco/prism-coder/.github/workflows/publish.yml@refs/tags/v20.22.4 |
| Rekor log index | 3405819876 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:89ed5ac9b03fed79e7e2de008f3e1aa26e8578f753b6c996a834f66f193b642457db66801cbdfe433d7803615fd335b33a089d0ee146752082c0bd014 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | node -e "import('./dist/postinstall.js').catch(()=>{})" |
Background: Why install scripts are a supply-chain risk →
Dependencies 227 packages
| Packages resolved | 227 |
|---|---|
| Deprecated | 4 |
| Stale | 44 |
| 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 →
skill_save ~262
Save a skill at one of three scopes: local (this machine only, works signed out), user (your account — follows you to every machine), or team (a workspace — delivered to its members; owner/admin only, optionally targeted with assign_to). Default when signed in is USER; team is never a default. Content must be a SKILL.md body with frontmatter (name, description). To make the skill load automatically when a prompt matches, add prompt_triggers to the frontmatter — a list of up to 5 case-insensitive regexes. They stay as private as the skill itself (matching happens on-device; scoped skills cannot use the public routing table): prompt_triggers: - "\\binvoice\\b.{0,20}\\bsubmit\\b"
| Name | Type | Req | Description |
|---|---|---|---|
| assign_to | array | – | Team scope only (admin): deliver ONLY to these member user ids; omit for all members |
| content | string | yes | Full SKILL.md content including frontmatter |
| name | string | yes | Skill name (lowercase letters, digits, - and _) |
| scope | string | – | Where the skill lives. Omit to default: user when signed in, local otherwise. |
| workspace_id | string | – | Required for team scope |
No output schema declared.
No examples provided.
sync_pull_handoff ~102
Pulls this account's synced handoff for a project from the E2E relay and opens it with THIS machine's device key. The relay stores ciphertext only; a handoff is readable here only if it was sealed to this device. Requires handoff sync enabled (prism handoff enable), a paid plan, and a signed-in account. Push happens automatically on session_save_handoff.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project whose handoff to pull. |
No output schema declared.
No examples provided.
verify_behavior ~171
Call BEFORE editing behavioral source files (API routes, ordering logic, billing, auth, migrations). Returns a domain-specific scenario you must answer to demonstrate understanding of the end-user impact. Example: editing a KDS route returns 'A cook has a 3-item ticket. One item is voided. What should the cook see?' Answer the scenario concretely before proceeding with the edit. If the MCP transport is unavailable, use the packaged `prism verify-behavior` CLI fallback; never fabricate a replacement scenario.
| Name | Type | Req | Description |
|---|---|---|---|
| change_summary | string | yes | Brief description of the intended change. |
| file_path | string | yes | Path of the file about to be edited. |
| project | string | – | Optional project identifier for workspace-scoped scenarios. |
| workspace_id | string | – | Optional workspace ID for custom scenarios. |
No output schema declared.
No examples provided.
How do I install the io.github.dcostenco/prism-coder MCP server?
io.github.dcostenco/prism-coder runs locally as an npm package, launched with npx -y prism-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 · prism-mcp-server
claude mcp add dcostenco-prism-coder -- npx -y prism-mcp-server
What is the io.github.dcostenco/prism-coder MCP server?
io.github.dcostenco/prism-coder is an MCP server listed in the public MCP registry as io.github.dcostenco/prism-coder. Session memory for coding agents: local-first recall, drift detection, on-device inference. This page covers its npm package (prism-mcp-server).
Is the io.github.dcostenco/prism-coder MCP server safe to use?
io.github.dcostenco/prism-coder scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares an install script we flagged as high risk. 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 io.github.dcostenco/prism-coder MCP server expose?
io.github.dcostenco/prism-coder exposes 53 tools: brave_web_search, brave_web_search_code_mode, brave_local_search, brave_local_search_code_mode, code_mode_transform, and 48 more. Their descriptions and schemas cost roughly 12,279 tokens of context every time the server is loaded.
Is the io.github.dcostenco/prism-coder MCP server still maintained?
io.github.dcostenco/prism-coder is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.dcostenco/prism-coder MCP server under?
io.github.dcostenco/prism-coder 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.