io.github.sairam0424/mindforge
NPM · MINDFORGE-MCP-SERVER · SCANNED AUG 3
Read the MindForge engine over MCP: knowledge graph, project health, and audit log.
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 (95 of 99), 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 (95 of 99), 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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 649 tokens (~92/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 · mindforge-mcp-server
claude mcp add sairam0424-mindforge -- npx -y mindforge-mcp-server
codex mcp add sairam0424-mindforge -- npx -y mindforge-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sairam0424-mindforge": {
"type": "local",
"command": [
"npx",
"-y",
"mindforge-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add sairam0424-mindforge --command npx --arg -y --arg mindforge-mcp-server
mcp_servers:
sairam0424-mindforge:
command: "npx"
args: ["-y", "mindforge-mcp-server"] {
"mcpServers": {
"sairam0424-mindforge": {
"command": "npx",
"args": [
"-y",
"mindforge-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 +15
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +8
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 1 Aug 26 −11
- Known CVEs: partial → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 31 Jul 26 +8
- 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 +22
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 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.
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_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.