bank-risk-metrics
https://bank-risk-api.culturehub-kash.workers.dev
Registry code: f4d724303490040b
US bank risk metrics from FDIC Call Reports. search_banks/get_sample/get_methodology are free; get_bank_metrics and screen_banks are paid per call with x402 (USDC on Base): call once, read the PaymentRequired in structuredContent, retry with params._meta['x402/payment'].
- endpoint
- https://bank-risk-api.culturehub-kash.workers.dev/mcp
- door code
- dbef0819811e316c
- 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 bank-risk-metrics live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is bank-risk-metrics free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does bank-risk-metrics have?
- 5 tools: screen_banks, get_methodology, search_banks, get_sample, get_bank_metrics.
- Is bank-risk-metrics 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.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
- unknown → live
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.
through this hub
successful
what callers paid
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_bank_metrics 0.01 USDC paid 1h ago
Paid ($0.01 USDC on Base via x402). Full risk metrics for one bank with raw FDIC inputs, source URL and 5-quarter history.
{ "type": "object", "required": [ "cert" ], "properties": { "cert": { "type": "string", "description": "FDIC certificate number, e.g. 628" } } }arguments 12 linesget_sample open 1h ago
Free. Full sample responses for 3 large banks, to check the data before paying.
{ "type": "object", "properties": {} }arguments 4 linesscreen_banks unknown never probed
Paid ($0.02 USDC on Base via x402). Rank all US banks by a metric.
{ "type": "object", "required": [ "metric" ], "properties": { "top": { "type": "number" }, "order": { "enum": [ "desc", "asc" ], "type": "string" }, "state": { "type": "string" }, "metric": { "enum": [ "risk_score", "uninsured_deposit_share", "cre_concentration", "construction_concentration", "unrealized_loss_to_tangible_equity", "htm_adjusted_tangible_equity_ratio", "loan_to_deposit", "noncurrent_loan_ratio", "npa_to_assets", "nim", "roa", "total_rbc_ratio", "leverage_ratio", "total_assets_usd" ], "type": "string" }, "min_assets_usd": { "type": "number" } } }arguments 43 linesget_methodology unknown never probed
Free. Exact formulas, sources and version of every metric.
{ "type": "object", "properties": {} }arguments 4 linessearch_banks unknown 1h ago
Free. Find FDIC-insured US banks by name; returns FDIC cert numbers.
{ "type": "object", "required": [ "q" ], "properties": { "q": { "type": "string", "description": "Bank name fragment" } } }arguments 12 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf4d724303490040b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f4d724303490040b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f4d724303490040b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 243ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 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.