io.github.sairam0424/mindforge
NPM · MINDFORGE-MCP-SERVER
Read the MindForge engine over MCP: knowledge graph, project health, and audit log.
Available components
Last scanned (16 hours ago)
Scores higher than 94% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 sairam0424/MindForge). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 869 tokens (~108/item across 8 items; 8 tools + 0 resources), lean.Pass
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.83 functional
- 15 Oct 26 +1
- Stability: 0.97 → pass security
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 7 Nov 2026 · Analysed npm/mindforge-mcp-server@11.9.8
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 | sairam0424/MindForge |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sairam0424/MindForge/.github/workflows/mindforge-release.yml@refs/tags/v11.9.8 |
| Rekor log index | 2903594115 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d6b5737f592484ed9c121232dc49053bb4db75a3563e5479f30b52500b821d445a1f2a9d80925ca951b571410626c8564f8d5c0c5e4b0e3af6896b2d6 |
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
mindforge_audit_log Read MindForge audit log ~106
Read entries from the MindForge audit log (.planning/AUDIT.jsonl), optionally filtered by event type or phase. Use to review what the framework has recorded for this project (task completions, security findings, decisions).
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | Filter by event type (e.g. task_completed, security_finding) |
| limit | integer | – | Max entries to return (default 50, newest last) |
| phase | integer | – | Filter by phase number |
No output schema declared.
No examples provided.
mindforge_browse Control the MindForge browser daemon ~220
Drive the persistent MindForge Playwright/Chromium daemon (the same one behind /mindforge:browse): check status, navigate, click, type, screenshot, or assert on the current page. The daemon binds to 127.0.0.1 only (ADR-024) and must already be running — start it with `/mindforge:browse --start` first; this tool never spawns it. Arbitrary JS evaluation and native-browser cookie import are intentionally NOT exposed here.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Browser action to perform |
| assertType | string | – | Assertion kind (action=assert) |
| expectedText | string | – | Expected value for the assertion (action=assert) |
| selector | string | – | CSS selector (action=click|type|assert) |
| session | string | – | Named browser session/context (default "default") |
| text | string | – | Text to type, or fallback click-by-text (action=click|type) |
| url | string | – | URL to navigate to (action=navigate) |
No output schema declared.
No examples provided.
mindforge_health MindForge project health ~54
Run a MindForge health check on the current project: verifies required planning/governance files exist, validates HANDOFF.json, and reports the audit-log size. Returns overallStatus (healthy|warning|error) with details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mindforge_memory_find_related Find related MindForge knowledge ~98
Given a free-text query, find related knowledge entries via keyword scoring plus graph traversal (multi-hop). Returns ranked entry ids with relevance scores. Use to surface connected decisions/patterns for a task description.
| Name | Type | Req | Description |
|---|---|---|---|
| maxHops | integer | – | Graph traversal depth (default 2) |
| query | string | yes | The task or topic to find related knowledge for |
| topK | integer | – | Max results (default 10) |
No output schema declared.
No examples provided.
mindforge_memory_query Query MindForge knowledge base ~147
Search the MindForge knowledge graph (architectural decisions, code/bug patterns, team preferences, domain knowledge) by topic text, tags, and type. Results are relevance-ranked. Use to recall prior decisions and patterns for the current project.
| Name | Type | Req | Description |
|---|---|---|---|
| includeGlobal | boolean | – | Include the cross-project global knowledge base |
| limit | integer | – | Max results (default 20) |
| minConfidence | number | – | Minimum confidence (0-1, default 0.3) |
| tags | array | – | Tags to match (boosts ranking) |
| topic | string | – | Free-text topic to match against entries |
| type | string | – | Restrict to one knowledge type |
No output schema declared.
No examples provided.
mindforge_memory_remember Store a MindForge knowledge entry ~132
Persist a new knowledge entry (decision, pattern, preference, or domain note) into the project knowledge graph so future sessions can recall it. Append-only and non-destructive — it never overwrites or deletes existing entries. Returns the new entry id.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | Confidence 0-1 (default 0.7) |
| content | string | yes | The knowledge content to remember |
| tags | array | – | Tags for later retrieval |
| topic | string | yes | Short topic/title (truncated to 80 chars) |
| type | string | yes | The kind of knowledge being stored |
No output schema declared.
No examples provided.
mindforge_memory_stats MindForge memory statistics ~57
Report statistics for the MindForge knowledge graph: total/active/deprecated entries, breakdown by type, average confidence, plus graph metrics (nodes, edges, edges by type, orphan ratio). Use to gauge how much project memory exists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mindforge_status MindForge project status ~55
Read the current MindForge project status: whether the project is initialized, the raw STATE.md, the HANDOFF.json contents, and the autonomous-run auto-state.json if present. Use to understand where a MindForge project currently stands.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.sairam0424/mindforge MCP server?
io.github.sairam0424/mindforge runs locally as an npm package, launched with npx -y mindforge-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 · mindforge-mcp-server
claude mcp add sairam0424-mindforge -- npx -y mindforge-mcp-server
What is the io.github.sairam0424/mindforge MCP server?
io.github.sairam0424/mindforge is an MCP server listed in the public MCP registry as io.github.sairam0424/mindforge. Read the MindForge engine over MCP: knowledge graph, project health, and audit log. This page covers its npm package (mindforge-mcp-server).
Is the io.github.sairam0424/mindforge MCP server safe to use?
io.github.sairam0424/mindforge scores 91 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 7 November 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 io.github.sairam0424/mindforge MCP server expose?
io.github.sairam0424/mindforge exposes 8 tools: mindforge_health, mindforge_status, mindforge_memory_query, mindforge_memory_stats, mindforge_memory_find_related, and 3 more. Their descriptions and schemas cost roughly 869 tokens of context every time the server is loaded.
Is the io.github.sairam0424/mindforge MCP server still maintained?
io.github.sairam0424/mindforge is still listed as active in the MCP registry. We last reached this channel on 7 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.sairam0424/mindforge MCP server under?
io.github.sairam0424/mindforge declares the MIT 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 io.github.sairam0424/mindforge MCP server?
VerifyMCP ran 16 checks on io.github.sairam0424/mindforge, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.