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

identifier-validator-peg-verdict

https://identifier-validator-api.yuechenxi-importexport.workers.dev

Registry code: 19d380ce0c7ca1d4

api record

Offline validators for IBAN, BIC, EU VAT, card (Luhn), ISBN and GTIN, plus a live stablecoin peg-health verdict. Structural checks only. All tools are read-only.

endpoint
https://identifier-validator-api.yuechenxi-importexport.workers.dev/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 identifier-validator-peg-verdict live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is identifier-validator-peg-verdict free to use?
Yes — the hub reached it with no key and no payment.
What tools does identifier-validator-peg-verdict have?
8 tools: validate_iban, validate_vat, validate_card, validate_isbn, validate_gtin, stablecoin_peg_verdict, validate_batch, validate_bic.
Is identifier-validator-peg-verdict 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
778ms

last good check

priced tools
0

of 8 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 8 tools
8 never probed 0 of 8 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_iban unknown never probed

    Validate an IBAN offline: country rules, length, BBAN structure, mod-97 checksum. Returns validity, country, SEPA flag and formatted IBAN. Structural check only: cannot tell whether the account exists.

    mcp-tool

    {
  "type": "object",
  "required": [
    "iban"
  ],
  "properties": {
    "iban": {
      "type": "string",
      "description": "The IBAN, spaces allowed. e.g. DE89370400440532013000"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • validate_vat unknown never probed

    Validate an EU/EEA (plus GB, NO, CH and more) VAT number format and checksum offline. Does not check VIES registration status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "vat"
  ],
  "properties": {
    "vat": {
      "type": "string",
      "description": "The VAT number, with or without country prefix. e.g. DE811569869"
    },
    "country": {
      "type": "string",
      "description": "Optional ISO country code if the number has no prefix."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • validate_card unknown never probed

    Luhn check and network detection (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay, Maestro, Mir). Returns masked output only; nothing is stored.

    mcp-tool

    {
  "type": "object",
  "required": [
    "number"
  ],
  "properties": {
    "number": {
      "type": "string",
      "description": "The card number (use test numbers). e.g. 4111111111111111"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • validate_isbn unknown never probed

    Validate ISBN-10 or ISBN-13 check digit and convert between the two.

    mcp-tool

    {
  "type": "object",
  "required": [
    "isbn"
  ],
  "properties": {
    "isbn": {
      "type": "string",
      "description": "The ISBN. e.g. 9780306406157"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • validate_gtin unknown never probed

    Validate GTIN-8/12/13/14 (EAN/UPC barcode) check digit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The barcode digits. e.g. 4006381333931"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • stablecoin_peg_verdict unknown 1h ago

    Live peg-health verdict for USD stablecoins: PEGGED / WATCH / DEPEG_RISK / DEPEGGED, 0-100 risk score, price deviation in bps, 1d/7d/30d supply change and per-chain liquidity, computed from DefiLlama (cached 5 min). Free tier: 30 calls/hour per client; for unlimited use pay per call via x402 (USDC on Base, $0.005): https://identifier-validator-api.yuechenxi-importexport.workers.dev/x402/v1/stablecoin-peg. Informational only, not financial advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "USD stablecoin symbol, name, DefiLlama id or CoinGecko id, e.g. USDC. Up to 10 comma-separated."
    },
    "chain": {
      "type": "string",
      "description": "Optional chain name (e.g. Base) to add on-chain supply/liquidity checks."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • validate_batch unknown 1h ago

    Validate up to 25 mixed identifiers (iban, bic, vat, card, isbn, gtin) in one call.

    mcp-tool

    {
  "type": "object",
  "required": [
    "items"
  ],
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type",
          "value"
        ],
        "properties": {
          "type": {
            "enum": [
              "iban",
              "bic",
              "vat",
              "card",
              "isbn",
              "gtin"
            ],
            "type": "string"
          },
          "value": {
            "type": "string"
          },
          "country": {
            "type": "string"
          }
        }
      },
      "maxItems": 25
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • validate_bic unknown 1h ago

    Validate a BIC/SWIFT code structure (8 or 11 chars), country, location and branch code.

    mcp-tool

    {
  "type": "object",
  "required": [
    "bic"
  ],
  "properties": {
    "bic": {
      "type": "string",
      "description": "The BIC/SWIFT code. e.g. DEUTDEFF"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 19d380ce0c7ca1d4.

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

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.