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

bank-check

https://bank-check.zovo.one

Registry code: 86e9efee897932a2

api record

FDIC bank lookup and coverage

from a public catalogue that lists it, not from the operator

endpoint
https://bank-check.zovo.one/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 bank-check live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is bank-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does bank-check have?
3 tools: estimate_deposit_coverage, find_bank, bank_history.
Is bank-check 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
471ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 3 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 3 tools
3 never probed 0 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.

  • estimate_deposit_coverage unknown never probed

    Use this when the user wants to know how much of their bank deposits are FDIC insured. Takes up to 30 accounts (FDIC cert, ownership category, balance, owners, trust beneficiaries), checks each bank in live FDIC records, and applies $250,000 per owner per bank per ownership category, joint shares, and the 2024 trust rule ($250,000 per beneficiary, up to 5). Returns insured and uninsured totals per bank and category, a PDF worksheet and a CSV. The result is an estimate; it does not replace FDIC EDIE and does not cover credit unions.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "accounts"
      ],
      "properties": {
        "accounts": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "cert",
              "category",
              "balance"
            ],
            "properties": {
              "cert": {
                "type": "integer",
                "maximum": 9007199254740991,
                "minimum": -9007199254740991,
                "description": "FDIC certificate number of the bank, e.g. 3511. Find it with find_bank."
              },
              "label": {
                "type": "string",
                "maxLength": 60,
                "description": "Optional nickname shown in the worksheet, e.g. Savings."
              },
              "owners": {
                "type": "array",
                "items": {
                  "type": "string",
                  "maxLength": 60
                },
                "maxItems": 10,
                "description": "Owner names or labels. One label for most categories (default \"you\"), e.g. [\"you\"]; 2 to 10 co-owners for joint, e.g. [\"you\", \"spouse\"]. Use the same label for the same person across accounts."
              },
              "balance": {
                "type": "number",
                "description": "Account balance in US dollars, e.g. 180000.50. Include accrued interest if known."
              },
              "category": {
                "enum": [
                  "single",
                  "joint",
                  "retirement",
                  "trust",
                  "business",
                  "employee_benefit_plan",
                  "government"
                ],
                "type": "string",
                "description": "FDIC ownership category, e.g. single. One of: single, joint, retirement (IRA and other self-directed retirement accounts), trust (revocable such as POD/living trust, or irrevocable), business (corporation, partnership, unincorporated association), employee_benefit_plan, government."
              },
              "beneficiaries": {
                "type": "integer",
                "maximum": 9007199254740991,
                "minimum": -9007199254740991,
                "description": "Trust accounts only: number of eligible beneficiaries named, e.g. 3 (0 to 50)."
              }
            }
          },
          "maxItems": 30,
          "description": "Accounts to estimate, e.g. [{\"cert\":3511,\"category\":\"single\",\"balance\":300000}]. Up to 30."
        }
      }
    }
    arguments 67 lines
  • find_bank unknown 14h ago

    Use this when the user asks whether a US bank is FDIC insured, or needs its FDIC certificate number, legal name, primary regulator, total assets, office count or website. Searches live FDIC BankFind records by name (optionally narrowed by state and city), by city and state, or by certificate number; returns up to 10 ranked matches and a CSV. Does not cover credit unions and does not estimate coverage (use estimate_deposit_coverage).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "cert": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991,
          "description": "FDIC certificate number if known, e.g. 3511."
        },
        "city": {
          "type": "string",
          "maxLength": 60,
          "description": "City of the bank's main office, e.g. Santa Clara. Use with state."
        },
        "name": {
          "type": "string",
          "maxLength": 80,
          "description": "Bank name or part of it, e.g. Wells Fargo."
        },
        "state": {
          "type": "string",
          "maxLength": 20,
          "description": "Two-letter state code to narrow the search, e.g. CA."
        },
        "include_inactive": {
          "type": "boolean",
          "description": "Also include closed, merged or failed institutions, e.g. true. Default false."
        }
      }
    }
    arguments 31 lines
  • bank_history unknown 14h ago

    Use this when the user wants a bank's structure history from FDIC records: when it was established, mergers it absorbed, whether it failed or was acquired, and its successor bank. Takes one FDIC certificate number; returns the profile, status, failure details if any, institution-level events and a CSV. Branch openings and moves are not listed. Does not show financial statements.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "cert"
      ],
      "properties": {
        "cert": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991,
          "description": "FDIC certificate number of the bank, e.g. 3511. Find it with find_bank."
        }
      }
    }
    arguments 15 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 86e9efee897932a2.

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

_ also on zovo.one 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.