# io.github.stabgan/steelmind (npm · @stabgan/steelmind-mcp)

Structured thinking + steel-manning verification for AI agents. Backed by 43+ papers.

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

## Components

- npm · `@stabgan/steelmind-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/stabgan-steelmind/stabgan-steelmind-mcp.md), [page](https://verifymcp.io/servers/stabgan-steelmind/stabgan-steelmind-mcp)

## Channel facts

- Registry: `npm`
- Package: `@stabgan/steelmind-mcp`
- Version: `2.0.1`
- 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-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/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 127 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 360 tokens (~180/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add stabgan-steelmind -- npx -y @stabgan/steelmind-mcp
```

### Codex

```bash
codex mcp add stabgan-steelmind -- npx -y @stabgan/steelmind-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add stabgan-steelmind --command npx --arg -y --arg @stabgan/steelmind-mcp
```

### Hermes

```yaml
mcp_servers:
  stabgan-steelmind:
    command: "npx"
    args: ["-y", "@stabgan/steelmind-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "stabgan-steelmind": {
      "command": "npx",
      "args": [
        "-y",
        "@stabgan/steelmind-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-08-03 (score 70, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 66, +61)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 5, −21)

- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified

### 2026-07-31 (score 26, −8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 34, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 52)

First indexed and scored.

## MCP tools (2)

### `think` (~217 tokens)

Use this tool to record a structured reasoning step. It will not obtain new information or change any state — it appends your thought to the log. Use it when you need to: process results from previous tool calls before acting, plan your approach to a multi-step task, analyze a complex situation before deciding, or navigate environments with detailed policies. Do NOT use for simple single-step tasks or restating without analysis. When thinking, ask yourself: What am I assuming? What evidence supports this? What's my plan, and what could go wrong? You can adjust totalThoughts up or down as your understanding deepens. When you set nextThoughtNeeded to false, use the verify tool to challenge your conclusion before acting.

Input parameters:

- `nextThoughtNeeded` (boolean, required): Whether another thinking step is needed after this one.
- `thought` (string, required): Your current thinking step.
- `thoughtNumber` (integer, required): Current thought number in the sequence.
- `totalThoughts` (integer, required): Estimated total thoughts needed. Can be adjusted up or down as you progress.

### `verify` (~143 tokens)

Use this tool to challenge and evaluate your reasoning before committing to an action. It will not obtain new information or change any state — it logs your critical self-assessment. Use it when you need to: check if your planned action complies with all requirements, validate reasoning before committing, assess edge cases, or evaluate tool results for correctness. Do NOT use to confirm what you are already confident about. When verifying, steel-man the opposition: What is the strongest argument that your conclusion is wrong? If you can't defeat it, reconsider. If your verification reveals a flaw, use the think tool to revise your approach.

Input parameters:

- `concern` (string, required): Your critical assessment or concern to verify.

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 66
- 2026-08-01: 5
- 2026-07-31: 26
- 2026-07-30: 34
- 2026-07-28: 52
- 2026-07-27: 52

## Links

- npm package: https://www.npmjs.com/package/@stabgan/steelmind-mcp
- Socket report: https://socket.dev/npm/package/@stabgan/steelmind-mcp
- Repository: https://github.com/stabgan/steelmind-mcp
- Changelog RSS feed: https://verifymcp.io/servers/stabgan-steelmind/stabgan-steelmind-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/stabgan-steelmind/stabgan-steelmind-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/stabgan-steelmind/stabgan-steelmind-mcp