About self-healing-infrastructure-mcp
self-healing-infrastructure-mcp is an infrastructure monitoring and remediation MCP server for operators managing governed environments. It routes remediation through domain-specific compliance checks and uses signed actions and BFT Council approval for critical decisions.
Key features
- 01Node and cluster health checks
- 02Service restart and auto-remediation
- 03GPU allocation and failover decisions
- 0428-domain compliance checks
- 05Ed25519-signed actions
- 06BFT Council governance
Use cases
- 01Checking node and cluster health
- 02Remediating common infrastructure issues
- 03Routing critical actions for council approval
- 04Verifying signed remediation records
MCP support
It exposes infrastructure health, remediation, cost, compliance, and council-governance tools to MCP clients, including `node_health_check` and `auto_remediate`.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMESovereign 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.