Skip to content

BRAINIAC Crypto Security MCP server

software.brainiac/crypto-securitybrainiac.softwarestreamable-httpv1.0.1Scanned

Paid Crypto Security API via x402. Unpaid tool calls return 402.

4 tools: 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 Crypto Security MCP server can do

The BRAINIAC Crypto Security MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (crypto-security_intent-safety); 4 tools bring in text other people can write (crypto-security_transaction-intent-verify, crypto-security_intent-safety, crypto-security_proxy-upgrade-storage-audit and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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

Only reads 4Show 4 read-only tools
  • crypto-security_intent-safetyRead a caller-supplied EVM transaction or an EIP-712 typed-data message and describe the transfer, approval, permit, or outer call it encodes.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Read a caller-supplied EVM transaction or an EIP-712 typed-data message and describe the transfer, approval, permit, or outer call it encodes. Known selectors are transfer, transferFrom, approve, increaseAllowance, setApprovalForAll, permit, multicall, aggregate, and execute. The score is a local penalty count. It does not simulate the call or read a chain. Price $0.04 USDC. POST /api/v1/crypto-security/intent-safety. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Score transaction intent safety
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • crypto-security_proxy-upgrade-storage-auditCompare the Solidity storage layout of an upgradeable implementation with a proposed replacement.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.

    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
    Compare the Solidity storage layout of an upgradeable implementation with a proposed replacement. Variables are matched by slot and offset, not by name. The types map is used for structs, mappings, dynamic arrays, and byte sizes. compatibility_status is compatible, incompatible, warnings, or indeterminate. risk_level is low, medium, high, or critical. A compatible result is not a claim that the upgrade is safe. No chain is queried. Price $0.05 USDC. POST /api/v1/crypto-security/proxy-upgrade-storage-audit. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Audit proxy upgrade storage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • crypto-security_storage-slot-gradeCompare two caller-supplied storage layouts by slot, offset, and size.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.

    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
    Compare two caller-supplied storage layouts by slot, offset, and size. A name that moves is a shift. Different names that occupy the same bytes are a collision. The grade and the collision score come from those counts. A variable is one slice of a single slot. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-security/storage-slot-grade. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Grade proxy storage slot changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • crypto-security_transaction-intent-verifyCompare an EVM transaction's calldata and native value with the action declared in the request.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.

    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
    Compare an EVM transaction's calldata and native value with the action declared in the request. Decoding uses the ABI in the request, or the standard ERC-20 transfer, transferFrom, approve, and increaseAllowance encodings when that selector matches. intent_match is true, false, or the string indeterminate when a declared field cannot be checked. risk_level is low, medium, high, or critical. This is static analysis: it does not read chain state, simulate the call, or decide that a contract is malicious or that the transaction will succeed. Price $0.04 USDC. POST /api/v1/crypto-security/transaction-intent-verify. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Verify transaction intent
    • 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 outbound.

Reads private data1
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
1
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
  • HighThe whole server

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

    Matched text

    https://www.brainiac.software/mcp/crypto-security: tools/list returned 4 tools to an anonymous client, including crypto-security_transaction-intent-verify (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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 crypto-security https://www.brainiac.software/mcp/crypto-security
claude mcp add --transport http crypto-security https://www.brainiac.software/mcp/crypto-security

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": [
      "mcp__crypto-security__crypto-security_transaction-intent-verify",
      "mcp__crypto-security__crypto-security_intent-safety",
      "mcp__crypto-security__crypto-security_proxy-upgrade-storage-audit",
      "mcp__crypto-security__crypto-security_storage-slot-grade"
    ],
    "ask": [],
    "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 crypto-security. Review it before you use it.

Capability tags behind 4 rules
  • mcp__crypto-security__crypto-security_transaction-intent-verify untrusted-input
  • mcp__crypto-security__crypto-security_intent-safety private-data, untrusted-input
  • mcp__crypto-security__crypto-security_proxy-upgrade-storage-audit untrusted-input
  • mcp__crypto-security__crypto-security_storage-slot-grade 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/crypto-security/verify?hash=c6c9e2e016781390b824ef4952cfb2ac6f9a3d4b4537d73dd0228a6c4c6550d1" | jq -e '.changed == false'

Pinned hash c6c9e2e01678, 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/crypto-security/changes.xml

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

Badge

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

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

BRAINIAC Crypto Security MCP server: questions and answers

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

Is the BRAINIAC Crypto Security MCP server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the BRAINIAC Crypto Security 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 Crypto Security 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 Crypto Security MCP server have?

4 tools: 4 read. crypto-security_transaction-intent-verify, crypto-security_intent-safety, crypto-security_proxy-upgrade-storage-audit and crypto-security_storage-slot-grade.

Does the BRAINIAC Crypto Security MCP server need sign-in or OAuth?

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

Does the BRAINIAC Crypto Security 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 Crypto Security 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.