BRAINIAC Crypto Operations MCP server
software.brainiac/crypto-operationsbrainiac.softwarestreamable-httpv1.0.1Scanned
Paid Crypto Operations API via x402. Unpaid tool calls return 402.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Operations MCP server can do
The BRAINIAC Crypto Operations MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: crypto-operations_bridge-leg-consistency), but cannot delete data. 1 tool only reads.
2 tools bring in text other people can write (crypto-operations_bridge-partial-failure-audit and crypto-operations_bridge-leg-consistency).
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.
2 tools
Changes things 1Claude Code: ask
crypto-operations_bridge-leg-consistencyGroup caller-supplied source and destination legs by message id.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 Group caller-supplied source and destination legs by message id. A message is consistent when both legs succeeded for the same amount. The recovery index is the hardest leg: a pending destination after a successful source scores lower than two matching successes. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-operations/bridge-leg-consistency. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Score bridge leg consistency
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
crypto-operations_bridge-partial-failure-auditCompare caller-supplied source and destination records for a cross-chain bridge.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 caller-supplied source and destination records for a cross-chain bridge. Operations are matched only by message identifier, or by the log field named in fieldMapping. Amounts are scaled with the supplied decimals, fee, and optional conversion rate. consistency_status is consistent, inconsistent, incomplete, or indeterminate. risk_level is low, medium, high, or critical. A missing record is incomplete evidence, not proof that the bridge failed. No chain is queried, and no transaction is treated as final. Price $0.05 USDC. POST /api/v1/crypto-operations/bridge-partial-failure-audit. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Audit bridge partial failure
- 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 write2
- 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.
Looked at Nov 20, 2026, 19:30 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
- 2
- 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 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.brainiac.software/mcp/crypto-operations: tools/list returned 2 tools to an anonymous client, including crypto-operations_bridge-partial-failure-audit (irreversible), crypto-operations_bridge-leg-consistency (write)
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.
Tools2 changed.~2 changedView diff
- Changed:crypto-operations_bridge-leg-consistencyChanges thingsinputSchemaannotations
- Changed:crypto-operations_bridge-partial-failure-auditOnly readsinputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http crypto-operations https://www.brainiac.software/mcp/crypto-operationsclaude mcp add --transport http crypto-operations https://www.brainiac.software/mcp/crypto-operationsRun 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.
{
"permissions": {
"allow": [
"mcp__crypto-operations__crypto-operations_bridge-partial-failure-audit"
],
"ask": [
"mcp__crypto-operations__crypto-operations_bridge-leg-consistency"
],
"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-operations. Review it before you use it.
Capability tags behind 2 rules
- mcp__crypto-operations__crypto-operations_bridge-partial-failure-audit untrusted-input
- mcp__crypto-operations__crypto-operations_bridge-leg-consistency 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-operations/verify?hash=4b671ba8158bc1ea542274044b21c9625ede708924a67d688a2b9f38d4ece423" | jq -e '.changed == false'Pinned hash 4b671ba8158b, from Nov 20, 2026, 01:18 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-operations/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/software.brainiac/crypto-operations)Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.
BRAINIAC Crypto Operations MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BRAINIAC Crypto Operations MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings 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 Crypto 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 Crypto 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 Crypto Operations MCP server have?
- 2 tools: 1 write, 1 read. crypto-operations_bridge-leg-consistency and crypto-operations_bridge-partial-failure-audit.
Does the BRAINIAC Crypto Operations MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BRAINIAC Crypto 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 Crypto 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.