mcpField
S
self-healing-infrastructure-mcp

self-healing-infrastructure-mcp

Local
github.com/CSOAI-ORGCloud & Infra0Updated 8w ago

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

  1. 01Node and cluster health checks
  2. 02Service restart and auto-remediation
  3. 03GPU allocation and failover decisions
  4. 0428-domain compliance checks
  5. 05Ed25519-signed actions
  6. 06BFT Council governance

Use cases

  1. 01Checking node and cluster health
  2. 02Remediating common infrastructure issues
  3. 03Routing critical actions for council approval
  4. 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.

mcp.json · Universal config
{
"mcpServers": {
"csoai-org-self-healing-infrastructure": {
"command": "uvx",
"args": [
"self-healing-infrastructure-mcp"
]
}
}
}
Run commanduvx self-healing-infrastructure-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiself-healing-infrastructure-mcp2.0.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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.

Sovereign EU AI Act Sigil License PyPI

What Makes This Sovereign

FeatureWhat It Means
Sigil Bus (Ed25519)Every remediation action is cryptographically signed. Tamper-proof audit trail.
BFT CouncilCritical decisions require 3-of-5 Byzantine Fault Tolerant consensus. No single point of failure.
28-Domain ComplianceAuto-remediation rules vary by industry domain (Finance, Healthcare, Energy, etc.).
EU AI Act Built-InArticles 9, 13, 15, 26, 50 — risk management, transparency, bias, FRIA, watermarking.
NIST AI RMFGovern, Map, Measure, Manage — all four functions implemented.
ISO 42001AI 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

ToolDescriptionGovernance
node_health_checkCheck CPU, memory, disk, GPUAuto + attested
cluster_health_checkCheck all 9 nodesAuto + attested
restart_serviceRestart failed serviceAuto if safe, council if critical
auto_remediateFix common issues28-domain compliance check first
gpu_orchestrationAllocate GPU across clusterAuto + attested
failover_decisionDetermine failover actionBFT Council vote
cost_reportInfrastructure cost breakdownRead-only
compliance_checkCheck if issue is auto-remediable28-domain rules
council_proposePropose critical action to BFT CouncilGovernance layer
council_voteCast vote on pending proposalGovernance layer
council_statusCheck proposal statusGovernance layer
verify_attestationVerify Ed25519 sigil on any actionCryptographic 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.

ComponentPurpose
Sigil BusEd25519 attestation chain for every agent action
BFT CouncilByzantine Fault Tolerant consensus for governance
28-Domain Engine280 data sources, 28 industry domains, $0 cost
Horus IntelWeekly competitive intelligence for AI governance
HIVE 1Enterprise compliance attestation (51 MCP servers)

📜 License

MIT © CSOAI-ORG · UK Companies House 16939677


Built with 💜 by CSOAI Labs · Sovereign AI Governance

Comments

Markdown supported

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.