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

Generate Random IBAN

https://generaterandomiban.com

Registry code: 7c8dc046bb6c6be3

api record

Tools to generate and validate structurally valid test IBANs (ISO 13616 / MOD-97), with correct national check digits where the country has them. generate_iban is realistic by default (real bank codes of major banks, digits only, random account numbers); pass realistic: false for fully random IBANs. Generated IBANs were not issued by any bank: never use them for payments.

endpoint
https://generaterandomiban.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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
106ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
1 open 2 never probed 1 of 3 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.

  • list_countries open 19h ago

    List all countries supported for IBAN generation, with code, name and IBAN length.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • validate_iban unknown never probed

    Validate an IBAN: MOD-97 checksum, expected length and country support.

    mcp-tool

    {
  "type": "object",
  "required": [
    "iban"
  ],
  "properties": {
    "iban": {
      "type": "string",
      "description": "The IBAN to validate (spaces are ignored)."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • generate_iban unknown never probed

    Generate one or more random, structurally valid (ISO 13616 / MOD-97) test IBANs for a country, with correct national check digits where the country has them. Generated IBANs were not issued by any bank: never use them for payments.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "count": {
      "type": "integer",
      "default": 1,
      "maximum": 100,
      "minimum": 1
    },
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2 country code, e.g. DE, FR, IT."
    },
    "realistic": {
      "type": "boolean",
      "default": true,
      "description": "Realistic mode (default true): digits only in alphanumeric fields (except real bank codes that contain letters), and a real bank code of a major bank (where curated data exists for the country) with a random account number. Pass false for fully random bank codes and accounts (letters where the format allows them). Such an IBAN was not issued by any bank but could match a real account by chance, so never use it for payments."
    }
  },
  "additionalProperties": false
}
    arguments 24 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 7c8dc046bb6c6be3.

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

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.