_ registry / mcp streamable-http · checked 4h ago

iban-analyzer

https://iban-analyzer.com

Registry code: 16d7a221041a35de

api record

Resolves IBANs to the bank behind them: registered name, BIC/SWIFT code and address, from national bank registers and the SWIFT directory. Use it when a payment instruction needs a bank named, or when an IBAN has to be checked before it is used. Where no record is held the answer says so rather than guessing - a bank name that is wrong costs the user a misdirected payment, so an empty result is never to be filled in from memory. analyze_iban and validate_iban draw on a monthly allowance; get_allowance reports what is left.

endpoint
https://iban-analyzer.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is iban-analyzer live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is iban-analyzer free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does iban-analyzer have?
5 tools: get_allowance, list_supported_countries, get_country_iban_format, analyze_iban, validate_iban.
Is iban-analyzer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
105ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 auth-required 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_allowance auth-required 4h ago

    How much of the caller's monthly allowance is left, which plan it belongs to and when it resets. Check this before a long run of lookups. Free - costs no allowance.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • list_supported_countries auth-required 4h ago

    Every country this service knows, and for each one whether IBAN validation and bank lookup are available. Use it to find out in advance whether a country can be answered at all. Free - costs no allowance.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • get_country_iban_format auth-required 4h ago

    The IBAN length and SEPA status for one country, and whether its IBANs are approved for international use. Free - costs no allowance.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country_code"
      ],
      "properties": {
        "country_code": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter ISO country code, e.g. DE."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • analyze_iban auth-required never probed

    Look up which bank an IBAN belongs to. Returns the registered bank name, BIC/SWIFT code and address where it is published, plus whether the IBAN is structurally valid, the country and its SEPA status. Where no bank is returned the result says why: a bank code that was never issued reads differently from one we hold no record for, and neither is ever guessed at. This is the tool to use for a payment instruction. Costs one bank lookup from the caller's monthly allowance, whatever the batch size.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ibans"
      ],
      "properties": {
        "ibans": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "The IBANs to look up, as written. Spaces and lower case are fine. Up to 50 per call."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • validate_iban auth-required never probed

    Check whether IBANs are structurally valid - length, country, checksum - without looking up the bank behind them. Use this when the question is only 'is this typed correctly'; use analyze_iban when the answer needs to name a bank. Costs one validation from the caller's monthly allowance.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ibans"
      ],
      "properties": {
        "ibans": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "The IBANs to look up, as written. Spaces and lower case are fine. Up to 50 per call."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 16d7a221041a35de.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/16d7a221041a35de/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/16d7a221041a35de/badge.svg)](https://brick.blue/agent/16d7a221041a35de?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.