# io.github.ronmiz/infernoflow (npm · infernoflow)

Git-native memory for coding agents: gotchas, decisions and bookmarks as plain text in your repo.

- Trust score: 70/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `infernoflow`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow.md), [page](https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow)

## Channel facts

- Registry: `npm`
- Package: `infernoflow`
- Version: `0.50.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 914 tokens (~101/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 18% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ronmiz-infernoflow -- npx -y infernoflow mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ronmiz-infernoflow": {
      "command": "npx",
      "args": [
        "-y",
        "infernoflow",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ronmiz-infernoflow": {
      "command": "npx",
      "args": [
        "-y",
        "infernoflow",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ronmiz-infernoflow -- npx -y infernoflow mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ronmiz-infernoflow": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "infernoflow",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ronmiz-infernoflow --command npx --arg -y --arg infernoflow --arg mcp
```

### Hermes

```yaml
mcp_servers:
  ronmiz-infernoflow:
    command: "npx"
    args: ["-y", "infernoflow", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ronmiz-infernoflow": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "infernoflow",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ronmiz-infernoflow -t stdio -c npx -a -y infernoflow mcp
```

### Other

```json
{
  "mcpServers": {
    "ronmiz-infernoflow": {
      "command": "npx",
      "args": [
        "-y",
        "infernoflow",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +27)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-03 (score 43, +1)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional regression] Schema quality: 80 → 101
- [functional improvement] Dependency health: unverified → pass
- [functional] Package version: 0.49.0 → 0.50.0

### 2026-11-02 (score 42, −22)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 68 → 80
- [functional regression] Dependency health: pass → unverified
- [functional improvement] 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

### 2026-10-24 (score 64, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-23 (score 52)

First indexed and scored.

## MCP tools (9)

### `amp_read` (~46 tokens)

AMP: read session memory entries with optional filters.

Input parameters:

- `file` (string)
- `limit` (integer)
- `query` (string)
- `type` (string)

### `amp_write` (~265 tokens)

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.

Input parameters:

- `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, required)
- `tags` (array)
- `type` (string, required)

### `amp_search` (~33 tokens)

AMP: search entries by keyword. Optional type filter.

Input parameters:

- `query` (string, required)
- `type` (string)

### `amp_bookmark` (~156 tokens)

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.

Input parameters:

- `label` (string, required)
- `note` (string): Optional explicit context. Omit to auto-capture the session transcript instead. Stored in a sidecar; not injected into rule files.

### `amp_resume` (~81 tokens)

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).

Input parameters:

- `file` (string)

### `amp_handoff` (~39 tokens)

AMP: generate the handoff document for the next AI session. format=markdown|json (default: markdown).

Input parameters:

- `format` (string)

### `amp_health` (~24 tokens)

AMP: get the session health score (0-100, A-F grade).

### `infernoflow_status` (~20 tokens)

Show project memory + contract health at a glance.

### `infernoflow_git_drift` (~57 tokens)

Detect which capabilities may be affected by recent code changes — useful when memory needs branch-aware revalidation.

Input parameters:

- `sinceCommits` (integer): How many commits back to check (default: 1, max: 100)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 43
- 2026-11-02: 42
- 2026-11-01: 64
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 64
- 2026-10-28: 64
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 64
- 2026-10-23: 52

## Common questions

### 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 5 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 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.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.

### What did VerifyMCP test on the io.github.ronmiz/infernoflow MCP server?

VerifyMCP ran 16 checks on io.github.ronmiz/infernoflow, 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.

## Links

- npm package: https://www.npmjs.com/package/infernoflow
- Socket report: https://socket.dev/npm/package/infernoflow
- Repository: https://github.com/ronmiz/infernoflow
- Changelog RSS feed: https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow.xml
- Changelog JSON feed: https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow.json
- HTML version of this page: https://verifymcp.io/servers/ronmiz-infernoflow/infernoflow