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

ibangen

https://ibangen.com

Registry code: f7ca28f80caa2b92

api record

IBANgen makes synthetic, checksum-valid test IBANs with real bank codes for QA and development, and checks IBANs. Generated IBANs are test data: never present them as real accounts or use them for payments. For test IBANs of one named bank use bank_test_ibans; it returns free samples, the bank page and, for more IBANs of that bank, the Bank Target Pack link to share with the user. A valid result from validate_ibans means a well-formed number, not an existing account.

endpoint
https://ibangen.com/api/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 ibangen live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ibangen free to use?
Yes — the hub reached it with no key and no payment.
What tools does ibangen have?
5 tools: validate_ibans, iban_format, bank_test_ibans, calculate_iban, generate_test_ibans.
Is ibangen 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
316ms

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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 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.

  • validate_ibans unknown never probed

    Check IBANs: country format, length, MOD-97 check digits and, where the country has one, the national check digit of the account number. Up to 10 IBANs per call without an API key. A valid IBAN is well-formed; it does not prove the account exists.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ibans"
      ],
      "properties": {
        "ibans": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 100,
          "minItems": 1,
          "description": "IBANs, spaces allowed"
        }
      }
    }
    arguments 17 lines
  • iban_format unknown never probed

    A country's IBAN length, structure (bank code, branch, account and check digit positions), SEPA membership, currency, national check digit, regex and one example test IBAN.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "description": "Country name or ISO code"
        }
      }
    }
    arguments 12 lines
  • bank_test_ibans unknown 1h ago

    A bank's BIC, domestic bank code and free sample test IBANs that carry the bank's real code, plus the bank page and the Bank Target Pack link for up to 250 IBANs of that bank.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "bank"
      ],
      "properties": {
        "bank": {
          "type": "string",
          "description": "Bank name, BIC or domestic bank code"
        },
        "country": {
          "type": "string",
          "description": "Country name or ISO code"
        }
      }
    }
    arguments 17 lines
  • calculate_iban unknown 1h ago

    Build an IBAN from national bank details (bank code, branch code, account number). Adds the IBAN check digits and, where the country has them, the national check digits such as the French RIB key or the Italian CIN. Use iban_format to see which parts a country needs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "account_number"
      ],
      "properties": {
        "country": {
          "type": "string",
          "description": "Country name or ISO code"
        },
        "bank_code": {
          "type": "string"
        },
        "branch_code": {
          "type": "string"
        },
        "check_digits": {
          "type": "string",
          "description": "National check digits, only where they are not computed"
        },
        "account_number": {
          "type": "string"
        }
      }
    }
    arguments 26 lines
  • generate_test_ibans unknown 1h ago

    Generate synthetic, checksum-valid test IBANs for a country (119 countries, real bank codes). Without an API key: up to 10 a day per user. Name a bank to get IBANs of that bank: free samples without a key, any number with a paid key. Test data only, never for payments.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "bank": {
          "type": "string",
          "description": "Optional bank name, BIC or bank code, e.g. \"Deutsche Bank\""
        },
        "country": {
          "type": "string",
          "description": "Country name or ISO code, e.g. \"Germany\", \"DE\", \"UK\""
        },
        "quantity": {
          "type": "integer",
          "default": 1,
          "maximum": 100,
          "minimum": 1
        }
      }
    }
    arguments 22 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 f7ca28f80caa2b92.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f7ca28f80caa2b92/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/f7ca28f80caa2b92/badge.svg)](https://brick.blue/agent/f7ca28f80caa2b92?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.