io.github.stabgan/steelmind
NPM · @STABGAN/STEELMIND-MCP
Structured thinking + steel-manning verification for AI agents. Backed by 43+ papers.
Available components
Last scanned (7 hours ago)
Scores higher than 90% of npm servers
Category AI and Machine Learning
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. 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 221 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 25 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
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 5 Nov 2026 · Analysed npm/@stabgan/steelmind-mcp@2.0.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
think ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nextThoughtNeeded | boolean | yes | Whether another thinking step is needed after this one. |
| thought | string | yes | Your current thinking step. |
| thoughtNumber | integer | yes | Current thought number in the sequence. |
| totalThoughts | integer | yes | Estimated total thoughts needed. Can be adjusted up or down as you progress. |
No output schema declared.
No examples provided.
verify ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| concern | string | yes | Your critical assessment or concern to verify. |
No output schema declared.
No examples provided.
How do I install the io.github.stabgan/steelmind MCP server?
io.github.stabgan/steelmind runs locally as an npm package, launched with npx -y @stabgan/steelmind-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @stabgan/steelmind-mcp
claude mcp add stabgan-steelmind -- npx -y @stabgan/steelmind-mcp
What is the io.github.stabgan/steelmind MCP server?
io.github.stabgan/steelmind is an MCP server listed in the public MCP registry as io.github.stabgan/steelmind. Structured thinking + steel-manning verification for AI agents. Backed by 43+ papers. This page covers its npm package (@stabgan/steelmind-mcp).
Is the io.github.stabgan/steelmind MCP server safe to use?
io.github.stabgan/steelmind scores 86 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.stabgan/steelmind MCP server expose?
io.github.stabgan/steelmind exposes 2 tools: think, verify. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.
Is the io.github.stabgan/steelmind MCP server still maintained?
io.github.stabgan/steelmind 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.stabgan/steelmind MCP server under?
io.github.stabgan/steelmind declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.