Skip to content

BRAINIAC Crypto Payments MCP server

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

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

2 tools: 2 do something that can't be undone.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. 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 Crypto Payments MCP server can do

The BRAINIAC Crypto Payments MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (crypto-payments_stablecoin-payment-reconcile and crypto-payments_invoice-match-score), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (crypto-payments_stablecoin-payment-reconcile and crypto-payments_invoice-match-score).

The fixed checks matched 2 findings (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.

2 tools

Can't be undone 2Claude Code: ask
  • crypto-payments_invoice-match-scoreMatch caller-supplied payments to invoice amounts, due dates, and fee rates in basis points.Reads text others write1 finding

    Why it is in this group

    • The name "crypto-payments_invoice-match-score" says "payment": a word that usually means money moves, which cannot be taken back.
    • 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 "crypto-payments_invoice-match-score" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "crypto-payments_invoice-match-score" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Match caller-supplied payments to invoice amounts, due dates, and fee rates in basis points. Accuracy gives 60 points to the amount, 20 to paying on time, and 20 to the fee. The discrepancy is the invoice total minus the linked payments. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-payments/invoice-match-score. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Score invoice payment match
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • crypto-payments_stablecoin-payment-reconcileReconcile caller-supplied stablecoin payment records against invoices.Reads text others write1 finding

    Why it is in this group

    • The name "crypto-payments_stablecoin-payment-reconcile" says "payment": a word that usually means money moves, which cannot be taken back.
    • 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 "crypto-payments_stablecoin-payment-reconcile" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "crypto-payments_stablecoin-payment-reconcile" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Reconcile caller-supplied stablecoin payment records against invoices. Compares amounts, token, recipient, and chain ID, and reports underpayments, overpayments, duplicate transaction hashes, and payments that are not linked to an invoice. reconciliation_status is matched, underpaid, overpaid, duplicate, mismatched, or incomplete. Amounts are integers in smallest units. No chain is queried, and a transaction hash is not treated as confirmation that funds arrived. Price $0.05 USDC. POST /api/v1/crypto-payments/stablecoin-payment-reconcile. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Reconcile stablecoin payment
    • 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.

Tools listed without sign-in

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 (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.brainiac.software/mcp/crypto-payments: tools/list returned 2 tools to an anonymous client, including crypto-payments_stablecoin-payment-reconcile (irreversible), crypto-payments_invoice-match-score (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "crypto-payments_stablecoin-payment-reconcile" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "crypto-payments_stablecoin-payment-reconcile" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "crypto-payments_invoice-match-score" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "crypto-payments_invoice-match-score" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for

History

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

  1. Tools2 changed.~2 changedView diff

Install

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

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

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__crypto-payments__crypto-payments_stablecoin-payment-reconcile",
      "mcp__crypto-payments__crypto-payments_invoice-match-score"
    ],
    "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-payments. Review it before you use it.

Capability tags behind 2 rules
  • mcp__crypto-payments__crypto-payments_stablecoin-payment-reconcile untrusted-input
  • mcp__crypto-payments__crypto-payments_invoice-match-score 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-payments/verify?hash=1e4c191224985fcc605cf92eb7b75b1dcb964bc7b2cd91f7fe188abaf30473ba" | jq -e '.changed == false'

Pinned hash 1e4c19122498, 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-payments/changes.xml

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

Badge

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

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

BRAINIAC Crypto Payments MCP server: questions and answers

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

Is the BRAINIAC Crypto Payments MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 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 Payments 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 Payments MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: crypto-payments_stablecoin-payment-reconcile and crypto-payments_invoice-match-score.

What tools does the BRAINIAC Crypto Payments MCP server have?

2 tools: 2 irreversible. crypto-payments_stablecoin-payment-reconcile and crypto-payments_invoice-match-score.

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

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

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