BRAINIAC Config Hardening & Release Operations
software.brainiac/devops · v1.0.1 · MCP 2025-11-25
Paid Config Hardening & Release Operations API via x402. Unpaid tool calls return 402.
Reachability
reachable
checked 2026-11-21 05:31 UTC
Registry status active
Tools pinned 4
18606edfc49e
Tools last changed
2026-11-21
Provenance
Registry namespace software.brainiac
(domain verified by the official registry)
Website
https://www.brainiac.software
Remote endpoints
https://www.brainiac.software/mcp/devops (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-21 05:31 | tools changed | 0 added, 0 removed, 4 changed |
| 2026-11-20 05:30 | first capture | 4 tools pinned |
Pinned tool definitions (4)
| Tool | Description |
|---|---|
| devops_config-hardening-grade | Grade a caller-supplied Dockerfile, Kubernetes YAML document, or Terraform JSON file for root execution, exposed ports, missing resource limits, and insecure defaults before you release or change production config. Parsing stays in... |
| devops_deployment-blast-radius | Walk a caller-supplied service dependency graph from proposed changes and list upstream and downstream services that may be affected before you release or change production config. No CI/CD system is contacted. Call with services,... |
| devops_rollback-feasibility-check | Evaluate whether a proposed deployment can be rolled back using supplied versions, migration reversibility, compatibility constraints, and recovery procedures before you release or change production config. No deployment platform is... |
| devops_release-readiness-audit | Check whether a release meets supplied operational requirements: prerequisites, monitoring coverage, rollback plans, and unresolved blockers before you release or change production config. Returns concrete gaps rather than a generic... |
Get alerted when this changes.
Email the moment software.brainiac/devops drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/software.brainiac/devops)
Maintain this server? Add the badge to your README. It links your users to this live status page.