io.github.lchampz/heimdall
NPM · @LCHAMPZ/MCP-HEIMDALL · SCANNED SEP 20
🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.
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 → 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
- 31 of 95 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 235 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 79 tokens (~15/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the io.github.lchampz/heimdall MCP server?
io.github.lchampz/heimdall runs locally as an npm package, launched with npx -y @lchampz/mcp-heimdall. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @lchampz/mcp-heimdall
claude mcp add lchampz-heimdall -- npx -y @lchampz/mcp-heimdall
{
"mcpServers": {
"lchampz-heimdall": {
"command": "npx",
"args": [
"-y",
"@lchampz/mcp-heimdall"
]
}
}
} {
"servers": {
"lchampz-heimdall": {
"command": "npx",
"args": [
"-y",
"@lchampz/mcp-heimdall"
]
}
}
} codex mcp add lchampz-heimdall -- npx -y @lchampz/mcp-heimdall
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lchampz-heimdall": {
"type": "local",
"command": [
"npx",
"-y",
"@lchampz/mcp-heimdall"
],
"enabled": true
}
}
} openclaw mcp add lchampz-heimdall --command npx --arg -y --arg @lchampz/mcp-heimdall
mcp_servers:
lchampz-heimdall:
command: "npx"
args: ["-y", "@lchampz/mcp-heimdall"] {
"McpServers": {
"lchampz-heimdall": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@lchampz/mcp-heimdall"
]
}
}
} assistant mcp add lchampz-heimdall -t stdio -c npx -a -y @lchampz/mcp-heimdall
{
"mcpServers": {
"lchampz-heimdall": {
"command": "npx",
"args": [
"-y",
"@lchampz/mcp-heimdall"
]
}
}
} 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.
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@lchampz/mcp-heimdall@1.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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
audit_dependencies ~13
Check for missing packages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
audit_env ~15
Check .env file against template.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_runtimes ~18
Check Node, Python version and config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
suggest_corrections ~19
Run all diagnostics and get prioritized fix suggestions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
system_info ~14
Get OS and architecture details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.lchampz/heimdall MCP server?
io.github.lchampz/heimdall is an MCP server listed in the public MCP registry as io.github.lchampz/heimdall. 🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool. This page covers its npm package (@lchampz/mcp-heimdall).
Is the io.github.lchampz/heimdall MCP server safe to use?
io.github.lchampz/heimdall scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.lchampz/heimdall MCP server expose?
io.github.lchampz/heimdall exposes 5 tools: system_info, inspect_runtimes, audit_dependencies, audit_env, suggest_corrections. Their descriptions and schemas cost roughly 79 tokens of context every time the server is loaded.
Is the io.github.lchampz/heimdall MCP server still maintained?
io.github.lchampz/heimdall is still listed as active in the MCP registry. We last reached this channel on 20 September 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.lchampz/heimdall MCP server under?
io.github.lchampz/heimdall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.