Skip to content

BRAINIAC Bank Account Identifiers & Payment Files MCP server

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

Paid Bank Account Identifiers & Payment Files API via x402. Unpaid tool calls return 402.

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

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

Tools listed without sign-in. Remote posture

With Anlyon

8 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 Bank Account Identifiers & Payment Files MCP server can do

The BRAINIAC Bank Account Identifiers & Payment Files MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (bank-payments_uk-modulus-check, bank-payments_sepa-creditor-id-validate, bank-payments_iban-from-bban, bank-payments_uetr-validate and 4 more), but cannot delete data. None of its tools only reads.

8 tools bring in text other people can write (bank-payments_uk-modulus-check, bank-payments_sepa-creditor-id-validate, bank-payments_iban-from-bban and 5 more).

The fixed checks matched 8 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.

8 tools

Can't be undone 8Claude Code: ask
  • bank-payments_camt053-parseParse an ISO 20022 bank-to-customer statement or report into normalised JSON with balance reconciliation checks.Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_camt053-parse" 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 "bank-payments_camt053-parse" 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 "bank-payments_camt053-parse" 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
    Parse an ISO 20022 bank-to-customer statement or report into normalised JSON with balance reconciliation checks. Price $0.03 USDC. POST /api/v1/bank-payments/camt053-parse. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Parse camt.052/053/054 statements
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_iban-from-bbanCompute ISO 13616 check digits for a country code and domestic BBAN, then validate the resulting IBAN structure.Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_iban-from-bban" 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 "bank-payments_iban-from-bban" 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 "bank-payments_iban-from-bban" 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
    Compute ISO 13616 check digits for a country code and domestic BBAN, then validate the resulting IBAN structure. Price $0.01 USDC. POST /api/v1/bank-payments/iban-from-bban. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Build an IBAN from a BBAN
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_nacha-file-buildGenerate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL) with batch hashes, totals and blocking-factor padding from JSON entries.Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_nacha-file-build" 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 "bank-payments_nacha-file-build" 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 "bank-payments_nacha-file-build" 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
    Generate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL) with batch hashes, totals and blocking-factor padding from JSON entries. Price $0.04 USDC. POST /api/v1/bank-payments/nacha-file-build. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Build a NACHA ACH file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_nacha-file-validateValidate NACHA record order, lengths, ABA checksums, batch/file hashes and totals, reporting every structural error by line.Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_nacha-file-validate" 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 "bank-payments_nacha-file-validate" 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 "bank-payments_nacha-file-validate" 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
    Validate NACHA record order, lengths, ABA checksums, batch/file hashes and totals, reporting every structural error by line. Price $0.03 USDC. POST /api/v1/bank-payments/nacha-file-validate. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Validate a NACHA ACH file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_postal-address-checkClassify an ISO 20022 PostalAddress as structured, hybrid or unstructured and check Swift CBPR+ town/country/AdrLine rules.Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_postal-address-check" 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 "bank-payments_postal-address-check" 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 "bank-payments_postal-address-check" 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
    Classify an ISO 20022 PostalAddress as structured, hybrid or unstructured and check Swift CBPR+ town/country/AdrLine rules. Price $0.02 USDC. POST /api/v1/bank-payments/postal-address-check. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: CBPR+ postal address format check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_sepa-creditor-id-validateParse a SEPA Direct Debit Creditor Identifier and recompute ISO 7064 Mod 97-10 check digits (business code excluded).Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_sepa-creditor-id-validate" 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 "bank-payments_sepa-creditor-id-validate" 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 "bank-payments_sepa-creditor-id-validate" 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
    Parse a SEPA Direct Debit Creditor Identifier and recompute ISO 7064 Mod 97-10 check digits (business code excluded). Price $0.01 USDC. POST /api/v1/bank-payments/sepa-creditor-id-validate. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Validate a SEPA Creditor Identifier
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_uetr-validateValidate an ISO 20022 UETR as a UUID version 4, or generate one or more UETRs with crypto.randomUUID().Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_uetr-validate" 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 "bank-payments_uetr-validate" 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 "bank-payments_uetr-validate" 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
    Validate an ISO 20022 UETR as a UUID version 4, or generate one or more UETRs with crypto.randomUUID(). Price $0.01 USDC. POST /api/v1/bank-payments/uetr-validate. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Validate or generate a UETR
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bank-payments_uk-modulus-checkCheck whether a UK sort code and account number pair can be valid using Vocalink modulus weights (valacdos/scsubtab) and exceptions 1–14.Reads text others write1 finding

    Why it is in this group

    • The name "bank-payments_uk-modulus-check" 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 "bank-payments_uk-modulus-check" 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 "bank-payments_uk-modulus-check" 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
    Check whether a UK sort code and account number pair can be valid using Vocalink modulus weights (valacdos/scsubtab) and exceptions 1–14. Price $0.02 USDC. POST /api/v1/bank-payments/uk-modulus-check. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: UK sort code + account modulus check
    • 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.
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:27 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
8
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 8 tools that change things (8 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.brainiac.software/mcp/bank-payments: tools/list returned 8 tools to an anonymous client, including bank-payments_uk-modulus-check (irreversible), bank-payments_sepa-creditor-id-validate (irreversible), bank-payments_iban-from-bban (irreversible), bank-payments_uetr-validate (irreversible), bank-payments_postal-address-check (irreversible) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

8 warn
  • The server marks "bank-payments_uk-modulus-check" 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 "bank-payments_uk-modulus-check" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bank-payments_sepa-creditor-id-validate" 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 "bank-payments_sepa-creditor-id-validate" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bank-payments_iban-from-bban" 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 "bank-payments_iban-from-bban" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bank-payments_uetr-validate" 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 "bank-payments_uetr-validate" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bank-payments_postal-address-check" 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 "bank-payments_postal-address-check" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bank-payments_nacha-file-build" 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 "bank-payments_nacha-file-build" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
Show 2 more findings
  • The server marks "bank-payments_nacha-file-validate" 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 "bank-payments_nacha-file-validate" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bank-payments_camt053-parse" 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 "bank-payments_camt053-parse" 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. Tools8 changed.~8 changedView diff

Install

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

claude mcp add --transport http bank-payments https://www.brainiac.software/mcp/bank-payments
claude mcp add --transport http bank-payments https://www.brainiac.software/mcp/bank-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__bank-payments__bank-payments_uk-modulus-check",
      "mcp__bank-payments__bank-payments_sepa-creditor-id-validate",
      "mcp__bank-payments__bank-payments_iban-from-bban",
      "mcp__bank-payments__bank-payments_uetr-validate",
      "mcp__bank-payments__bank-payments_postal-address-check",
      "mcp__bank-payments__bank-payments_nacha-file-build",
      "mcp__bank-payments__bank-payments_nacha-file-validate",
      "mcp__bank-payments__bank-payments_camt053-parse"
    ],
    "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 bank-payments. Review it before you use it.

Capability tags behind 8 rules
  • mcp__bank-payments__bank-payments_uk-modulus-check untrusted-input
  • mcp__bank-payments__bank-payments_sepa-creditor-id-validate untrusted-input
  • mcp__bank-payments__bank-payments_iban-from-bban untrusted-input
  • mcp__bank-payments__bank-payments_uetr-validate untrusted-input
  • mcp__bank-payments__bank-payments_postal-address-check untrusted-input
  • mcp__bank-payments__bank-payments_nacha-file-build untrusted-input
  • mcp__bank-payments__bank-payments_nacha-file-validate untrusted-input
  • mcp__bank-payments__bank-payments_camt053-parse 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/bank-payments/verify?hash=ac2102d70515363479d90ddb994addd756aa18331768126f91d87927efef5ccf" | jq -e '.changed == false'

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

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

Badge

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

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

BRAINIAC Bank Account Identifiers & Payment Files MCP server: questions and answers

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

Is the BRAINIAC Bank Account Identifiers & Payment Files MCP server safe?

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

Yes. 8 tools can send, pay, publish or merge: bank-payments_uk-modulus-check, bank-payments_sepa-creditor-id-validate, bank-payments_iban-from-bban, bank-payments_uetr-validate, bank-payments_postal-address-check, bank-payments_nacha-file-build and 2 more.

What tools does the BRAINIAC Bank Account Identifiers & Payment Files MCP server have?

8 tools: 8 irreversible. bank-payments_uk-modulus-check, bank-payments_sepa-creditor-id-validate, bank-payments_iban-from-bban, bank-payments_uetr-validate, bank-payments_postal-address-check, bank-payments_nacha-file-build, bank-payments_nacha-file-validate and bank-payments_camt053-parse.

Does the BRAINIAC Bank Account Identifiers & Payment Files MCP server need sign-in or OAuth?

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

Does the BRAINIAC Bank Account Identifiers & Payment Files 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 Bank Account Identifiers & Payment Files 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.