Zovo Bank Insurance Check
REMOTE · BANK-CHECK.ZOVO.ONE
FDIC bank lookup and coverage
Available components
Last scanned (17 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 504 tokens (~126/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://bank-check.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1a6be51dae225a780e14b5b59cd24fa3 |
| SANs: zovo.one, *.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bank-check.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| one. | DS published | 64939 | 8 | Verified |
| zovo.one. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bank-check.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://bank-check.zovo.one/mcp | HTTPS enforced | 301 | https://bank-check.zovo.one/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bank_history Show a bank's FDIC history ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cert | integer | yes | FDIC certificate number of the bank, e.g. 3511. Find it with find_bank. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| events | array | yes | – |
| events_count | object | – | – |
| events_total | number | yes | – |
| failure | – | yes | – |
| institution | object | yes | – |
| kind | string | yes | – |
| mergers_absorbed | number | yes | – |
| source | object | yes | – |
| status | string | yes | – |
| successor | – | yes | – |
No examples provided.
estimate_deposit_coverage Estimate FDIC deposit coverage ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | yes | Accounts to estimate, e.g. [{"cert":3511,"category":"single","balance":300000}]. Up to 30. |
| Name | Type | Req | Description |
|---|---|---|---|
| accounts_used | number | yes | – |
| bank_check | string | yes | – |
| banks | array | yes | – |
| banks_count | object | – | – |
| downloads | object | yes | – |
| edie_url | string | yes | – |
| errors | array | yes | – |
| errors_count | object | – | – |
| estimate_note | string | yes | – |
| kind | string | yes | – |
| rules_url | string | yes | – |
| source | object | yes | – |
| totals | object | yes | – |
No examples provided.
find_bank Find an FDIC-insured bank ~210
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).
| Name | Type | Req | Description |
|---|---|---|---|
| cert | integer | – | FDIC certificate number if known, e.g. 3511. |
| city | string | – | City of the bank's main office, e.g. Santa Clara. Use with state. |
| include_inactive | boolean | – | Also include closed, merged or failed institutions, e.g. true. Default false. |
| name | string | – | Bank name or part of it, e.g. Wells Fargo. |
| state | string | – | Two-letter state code to narrow the search, e.g. CA. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| institutions | array | yes | – |
| institutions_count | object | – | – |
| kind | string | yes | – |
| note | string | yes | – |
| query | object | yes | – |
| ranked | number | yes | – |
| source | object | yes | – |
| total_matches | number | yes | – |
No examples provided.
How do I install the Zovo Bank Insurance Check MCP server?
Zovo Bank Insurance Check is a hosted endpoint at https://bank-check.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bank-check.zovo.one
claude mcp add --transport http theluckystrike-bank-check 'https://bank-check.zovo.one/mcp'
What is the Zovo Bank Insurance Check MCP server?
Zovo Bank Insurance Check is an MCP server listed in the public MCP registry as io.github.theluckystrike/bank-check. FDIC bank lookup and coverage. This page covers its hosted endpoint (https://bank-check.zovo.one/mcp).
Is the Zovo Bank Insurance Check MCP server safe to use?
Zovo Bank Insurance Check scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zovo Bank Insurance Check MCP server expose?
Zovo Bank Insurance Check exposes 3 tools: find_bank, bank_history, estimate_deposit_coverage. Their descriptions and schemas cost roughly 489 tokens of context every time the server is loaded.
Does the Zovo Bank Insurance Check MCP server require authentication?
No. We connected to Zovo Bank Insurance Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Bank Insurance Check MCP server still maintained?
Zovo Bank Insurance Check is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Zovo Bank Insurance Check MCP server?
VerifyMCP ran 14 checks on Zovo Bank Insurance Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.