MCP.Market

Heimdall MCP server

by lchampz·io.github.lchampz/heimdall·v1.0.1

🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Heimdall yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Heimdall tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_dependencies

    Check for missing packages.

  • audit_env

    Check .env file against template.

  • inspect_runtimes

    Check Node, Python version and config.

  • suggest_correctionswrite action

    Run all diagnostics and get prioritized fix suggestions.

  • system_info

    Get OS and architecture details.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 11 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Heimdall compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
35
more than 25% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 change

Install Heimdall in Claude Code, Cursor or VS Code

Runs npx -y @lchampz/mcp-heimdall on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add heimdall -- npx -y @lchampz/mcp-heimdall
Add to Cursor

What the publisher says

From the Heimdall repository's README, as published. We do not edit it. Read it on GitHub

🛡️ MCP Heimdall

Advanced Environment Architect & Diagnostic Tool for Model Context Protocol (MCP).

Heimdall helps AI agents understand, verify, and fix their execution environment. It provides detailed insights into system architecture, runtime versions, dependencies, and environment variables, along with actionable correction suggestions.

✨ Features

  • Workspace Janitor: Find large files (>50MB) and temporary directories (dist, build, etc.) for cleanup.
  • Path Inspector: Audit the PATH variable and verify versions of critical dev tools (git, brew, make).
  • Process Explorer: Identify top CPU/Memory consumers and potential orphan Node/Python processes.
  • Docker Sight: Check Docker daemon status, list containers and images.
  • Connectivity Check: Ping essential services (GitHub, NPM, Docker Hub) to verify internet status.
  • Project Doctor: Scan Project for NPM vulnerabilities and outdated packages.
  • Resource Watcher: Monitor CPU load, memory usage, and disk space.
  • Port Manager: List active listening ports and kill processes blocking specific ports.
  • Runtime Inspector: Verify Node.js, Python, Java, and Kotlin versions against project requirements.
  • Dependency Guard: detects missing node_modules or virtual environments.
  • Environment Audit: Compares .env against templates and flags missing keys.
  • Intelligent Advisor: consolidated tool that suggests specific commands to fix environment issues.

🛠️ Tools

🚀 Installation

Quick Integration

Run this command to automatically configure Heimdall in your current workspace:

npx @lchampz/mcp-heimdall integrate

This will create a .vscode/mcp.json file with the correct configuration.

For Users (via MCP Registry)

Add to your mcp.json or editor settings:

{
  "servers": {
    "heimdall": {
      "command": "node",
      "args": ["path/to/mcp-heimdall/build/index.js"]
    }
  }
}

For Developers

  1. Clone the repository
  2. Install dependencies: npm install
  3. Build the project: npm run build
  4. Run in dev mode: npm run dev

📄 License

MIT

Nothing above is checked by us. What we check is on the safety report.

Heimdall: common questions

Is Heimdall MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Heimdall safety report
How do I install Heimdall?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Heimdall need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Heimdall maintained?
The last commit was 48 days ago (2026-09-17). The latest release is v1.0.1.
How does Heimdall compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.