io.github.lchampz/heimdall
NPM · @LCHAMPZ/MCP-HEIMDALL · SCANNED AUG 3
🛡️ 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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 187 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability46
- AI-judged instruction clarity (poor).Fail
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @lchampz/mcp-heimdall
claude mcp add lchampz-heimdall -- npx -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": {
"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.
- 2 Aug 26 +38
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → poor ▲ functional
- Licence: MIT functional
- 31 Jul 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- 28 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Schema quality: unverified functional
- 27 Jul 26 24
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 3 Aug 2026 · Analysed npm/@lchampz/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.