Skip to content

BRAINIAC Config Hardening & Release Operations MCP server

software.brainiac/devopsbrainiac.softwarestreamable-httpv1.0.1Scanned

Paid Config Hardening & Release Operations API via x402. Unpaid tool calls return 402.

4 tools: 4 change things.

Tools: 0 delete, 0 irreversible, 4 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BRAINIAC Config Hardening & Release Operations MCP server can do

The BRAINIAC Config Hardening & Release Operations MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: devops_config-hardening-grade, devops_deployment-blast-radius, devops_rollback-feasibility-check and devops_release-readiness-audit), but cannot delete data. None of its tools only reads.

4 tools bring in text other people can write (devops_config-hardening-grade, devops_deployment-blast-radius, devops_rollback-feasibility-check and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 4Claude Code: ask
  • devops_config-hardening-gradeGrade a caller-supplied Dockerfile, Kubernetes YAML document, or Terraform JSON file for root execution, exposed ports, missing resource limits, and insecure defaults.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Grade a caller-supplied Dockerfile, Kubernetes YAML document, or Terraform JSON file for root execution, exposed ports, missing resource limits, and insecure defaults. Parsing stays in memory. The file is not applied, fetched, or stored. Price $0.04 USDC. POST /api/v1/devops/config-hardening-grade. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Grade infrastructure config hardening
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • devops_deployment-blast-radiusWalk a caller-supplied service dependency graph from proposed changes and list upstream and downstream services that may be affected.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Walk a caller-supplied service dependency graph from proposed changes and list upstream and downstream services that may be affected. No CI/CD system is contacted. Price $0.04 USDC. POST /api/v1/devops/deployment-blast-radius. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Calculate deployment blast radius
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • devops_release-readiness-auditCheck whether a release meets supplied operational requirements: prerequisites, monitoring coverage, rollback plans, and unresolved blockers.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check whether a release meets supplied operational requirements: prerequisites, monitoring coverage, rollback plans, and unresolved blockers. Returns concrete gaps rather than a generic risk score. Price $0.04 USDC. POST /api/v1/devops/release-readiness-audit. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Audit release readiness
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • devops_rollback-feasibility-checkEvaluate whether a proposed deployment can be rolled back using supplied versions, migration reversibility, compatibility constraints, and recovery procedures.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "devops_rollback-feasibility-check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Evaluate whether a proposed deployment can be rolled back using supplied versions, migration reversibility, compatibility constraints, and recovery procedures. No deployment platform is queried. Price $0.04 USDC. POST /api/v1/devops/rollback-feasibility-check. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Check rollback feasibility
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:31 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.brainiac.software/mcp/devops: tools/list returned 4 tools to an anonymous client, including devops_config-hardening-grade (write), devops_deployment-blast-radius (write), devops_rollback-feasibility-check (write), devops_release-readiness-audit (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "devops_rollback-feasibility-check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "evaluate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http devops https://www.brainiac.software/mcp/devops
claude mcp add --transport http devops https://www.brainiac.software/mcp/devops

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__devops__devops_config-hardening-grade",
      "mcp__devops__devops_deployment-blast-radius",
      "mcp__devops__devops_rollback-feasibility-check",
      "mcp__devops__devops_release-readiness-audit"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as devops. Review it before you use it.

Capability tags behind 4 rules
  • mcp__devops__devops_config-hardening-grade untrusted-input
  • mcp__devops__devops_deployment-blast-radius untrusted-input
  • mcp__devops__devops_rollback-feasibility-check untrusted-input
  • mcp__devops__devops_release-readiness-audit untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/software.brainiac/devops/verify?hash=f25953c7745de044a256ac557e8a9c712f6632e77240deb12035617756ed7750" | jq -e '.changed == false'

Pinned hash f25953c7745d, from Nov 20, 2026, 01:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/software.brainiac/devops/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for software.brainiac/devops
[![Anlyon Radar](https://radar.anlyon.com/badge/software.brainiac/devops.svg)](https://radar.anlyon.com/servers/software.brainiac/devops)

Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.

BRAINIAC Config Hardening & Release Operations MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BRAINIAC Config Hardening & Release Operations MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BRAINIAC Config Hardening & Release Operations MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BRAINIAC Config Hardening & Release Operations MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BRAINIAC Config Hardening & Release Operations MCP server have?

4 tools: 4 write. devops_config-hardening-grade, devops_deployment-blast-radius, devops_rollback-feasibility-check and devops_release-readiness-audit.

Does the BRAINIAC Config Hardening & Release Operations MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BRAINIAC Config Hardening & Release Operations MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BRAINIAC Config Hardening & Release Operations MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.