io.github.ronmiz/infernoflow
NPM · INFERNOFLOW
Git-native memory for coding agents: gotchas, decisions and bookmarks as plain text in your repo.
Available components
Last scanned (22 hours ago)
Scores higher than 39% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 914 tokens (~101/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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
- 18% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 +27
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 3 Nov 26 +1
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Schema quality: 80 → 101 ▼ functional
- Dependency health: unverified → pass ▲ functional
- Package version: 0.49.0 → 0.50.0 functional
- 2 Nov 26 −22
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Schema quality: 68 → 80 ▼ functional
- Dependency health: pass → unverified ▼ functional
- Stability: unverified → 0.33 ▲ functional
- Package version: 0.46.5 → 0.49.0 functional
- Package version: 0.46.5 → 0.48.0 functional
- Package version: 0.46.5 → 0.47.0 functional
- 24 Oct 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 23 Oct 26 52
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 4 Nov 2026 · Analysed npm/infernoflow@0.50.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
amp_bookmark ~156
AMP: drop a named session bookmark — a resume point. Required: label (short name). Optional: note. If note is OMITTED, the current session transcript is auto-captured as the bookmark's context (the 'save everything here' resume point). Use when the user says 'bookmark this' / 'mark this point', or before a risky change / when the context window is filling up, so the exact state can be recalled later and appears in the next session's handoff. Bookmarks are never auto-pruned.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | – |
| note | string | – | Optional explicit context. Omit to auto-capture the session transcript instead. Stored in a sidecar; not injected into rule files. |
No output schema declared.
No examples provided.
amp_handoff ~39
AMP: generate the handoff document for the next AI session. format=markdown|json (default: markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
No output schema declared.
No examples provided.
amp_health ~24
AMP: get the session health score (0-100, A-F grade).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
amp_read ~46
AMP: read session memory entries with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
amp_resume ~81
AMP: 'where were we?' in one call — the latest resume point with its note, open dead ends (don't repeat them), recent decisions/notes, uncommitted changes, and which memory store this is. Call it at the start of work in a session. Optional: file (rank entries about that file first).
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | – |
No output schema declared.
No examples provided.
amp_search ~33
AMP: search entries by keyword. Optional type filter.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
amp_write ~265
AMP: log a new entry. Required: type + msg (one sentence). Optional: file, line, tags, detail. Call it without being asked when: the user is stuck ('!!', 'not working', 'same error', 'retry' → type attempt: what was tried and how it failed); the user asks you to remember something (save the fact in your own words); a decision is made (type decision: X over Y because Z); you learn something non-obvious (type gotcha, with file/line). These apply in any language the user writes in. Don't log what can be re-derived from the code. Use 'detail' for a rich multi-paragraph body (repro steps, code, full reasoning, or a session snapshot) — it's stored in a sidecar and loaded on demand, so it never bloats the always-on memory index.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Optional rich body (Tier-2). Stored in the consolidated details store; NOT injected into rule files. Put the long-form context here; keep 'msg' to one summary sentence. |
| file | string | – | – |
| line | integer | – | – |
| msg | string | yes | – |
| tags | array | – | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
infernoflow_git_drift ~57
Detect which capabilities may be affected by recent code changes — useful when memory needs branch-aware revalidation.
| Name | Type | Req | Description |
|---|---|---|---|
| sinceCommits | integer | – | How many commits back to check (default: 1, max: 100) |
No output schema declared.
No examples provided.
infernoflow_status ~20
Show project memory + contract health at a glance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.ronmiz/infernoflow MCP server?
io.github.ronmiz/infernoflow runs locally as an npm package, launched with npx -y infernoflow. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · infernoflow
claude mcp add ronmiz-infernoflow -- npx -y infernoflow
What is the io.github.ronmiz/infernoflow MCP server?
io.github.ronmiz/infernoflow is an MCP server listed in the public MCP registry as io.github.ronmiz/infernoflow. Git-native memory for coding agents: gotchas, decisions and bookmarks as plain text in your repo. This page covers its npm package (infernoflow).
Is the io.github.ronmiz/infernoflow MCP server safe to use?
io.github.ronmiz/infernoflow scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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.ronmiz/infernoflow MCP server expose?
io.github.ronmiz/infernoflow exposes 9 tools: amp_read, amp_write, amp_search, amp_bookmark, amp_resume, and 4 more. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.
Is the io.github.ronmiz/infernoflow MCP server still maintained?
io.github.ronmiz/infernoflow is still listed as active in the MCP registry. We last reached this channel on 4 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.ronmiz/infernoflow MCP server under?
io.github.ronmiz/infernoflow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.