Server data from the Official MCP Registry
Self Healing Infrastructure MCP Server by MEOK AI Labs
About
Self Healing Infrastructure MCP Server by MEOK AI Labs
Security Report
This server exhibits multiple critical security concerns that outweigh its legitimate infrastructure monitoring purpose. The code contains confirmed dangerous patterns (external metering calls with api_key exfiltration, network requests to unverified endpoints), suspicious monetization layers with fail-open security, incomplete/truncated auth middleware, and misleading claims about cryptographic governance that are not actually implemented. While the 28-domain compliance framework and BFT Council concepts are sound, the actual implementation is underdeveloped, and the real risk comes from the external metering infrastructure that phones home with user credentials. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 5 high severity). Package verification found 1 issue (1 critical, 0 high severity).
6 files analyzed · 18 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-csoai-org-self-healing-infrastructure-mcp": {
"args": [
"-y",
"self-healing-infrastructure-mcp"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Sovereign Self-Healing MCP
The only self-healing infrastructure MCP with cryptographic governance.
Every remediation is Ed25519-signed, BFT Council-approved, and EU AI Act compliant.
What Makes This Sovereign
| Feature | What It Means |
|---|---|
| Sigil Bus (Ed25519) | Every remediation action is cryptographically signed. Tamper-proof audit trail. |
| BFT Council | Critical decisions require 3-of-5 Byzantine Fault Tolerant consensus. No single point of failure. |
| 28-Domain Compliance | Auto-remediation rules vary by industry domain (Finance, Healthcare, Energy, etc.). |
| EU AI Act Built-In | Articles 9, 13, 15, 26, 50 — risk management, transparency, bias, FRIA, watermarking. |
| NIST AI RMF | Govern, Map, Measure, Manage — all four functions implemented. |
| ISO 42001 | AI management system controls mapped to auto-remediation policies. |
🚀 Quick Start
# Install via pip
pip install sovereign-self-healing-mcp
# Or via Smithery
npx -y @smithery/cli@latest install sovereign-self-healing-mcp --client claude
# Or via uvx (fastest)
uvx sovereign-self-healing-mcp
✨ Tools
| Tool | Description | Governance |
|---|---|---|
node_health_check | Check CPU, memory, disk, GPU | Auto + attested |
cluster_health_check | Check all 9 nodes | Auto + attested |
restart_service | Restart failed service | Auto if safe, council if critical |
auto_remediate | Fix common issues | 28-domain compliance check first |
gpu_orchestration | Allocate GPU across cluster | Auto + attested |
failover_decision | Determine failover action | BFT Council vote |
cost_report | Infrastructure cost breakdown | Read-only |
compliance_check | Check if issue is auto-remediable | 28-domain rules |
council_propose | Propose critical action to BFT Council | Governance layer |
council_vote | Cast vote on pending proposal | Governance layer |
council_status | Check proposal status | Governance layer |
verify_attestation | Verify Ed25519 sigil on any action | Cryptographic proof |
🛡️ Compliance by Design
Every tool call goes through the Sovereign Governance Layer:
Issue Detected → Domain Classification → Compliance Check → [Auto | Council | Block] → Sigil Sign → Log
- Finance domain:
disk_full→ Auto-remediate.data_loss→ BFT Council. - Healthcare domain:
backup_verify→ Auto.phi_exposure→ BFT Council + manual review. - Energy domain:
load_balancer_shift→ Auto.grid_disconnect→ BFT Council + safety isolation.
🏛️ Part of the Sovereign Temple
This MCP server is part of CSOAI Sovereign Temple — the open-source sovereign AI governance infrastructure.
| Component | Purpose |
|---|---|
| Sigil Bus | Ed25519 attestation chain for every agent action |
| BFT Council | Byzantine Fault Tolerant consensus for governance |
| 28-Domain Engine | 280 data sources, 28 industry domains, $0 cost |
| Horus Intel | Weekly competitive intelligence for AI governance |
| HIVE 1 | Enterprise compliance attestation (51 MCP servers) |
📜 License
MIT © CSOAI-ORG · UK Companies House 16939677
Built with 💜 by CSOAI Labs · Sovereign AI Governance
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.