Skip to content

Zovo Bank Insurance Check MCP server

io.github.theluckystrike/bank-checktheluckystrikestreamable-httpv1.0.0Scanned

FDIC bank lookup and coverage

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Zovo Bank Insurance Check MCP server can do

The Zovo Bank Insurance Check MCP server is published by the GitHub account theluckystrike. It has 3 tools. It can create or change data (2 tools: bank_history and estimate_deposit_coverage), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (find_bank, bank_history and estimate_deposit_coverage).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • bank_historyUse 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Show a bank's FDIC history
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • estimate_deposit_coverageUse this when the user wants to know how much of their bank deposits are FDIC insured.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Estimate FDIC deposit coverage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • find_bankUse 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.Reads text others writeNo findings

    Why it is in this group

    • The name "find_bank" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Find an FDIC-insured bank
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:23 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bank-check.zovo.one/mcp: tools/list returned 3 tools to an anonymous client, including bank_history (write), estimate_deposit_coverage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bank-check https://bank-check.zovo.one/mcp
claude mcp add --transport http bank-check https://bank-check.zovo.one/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bank-check__find_bank"
    ],
    "ask": [
      "mcp__bank-check__bank_history",
      "mcp__bank-check__estimate_deposit_coverage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bank-check. Review it before you use it.

Capability tags behind 3 rules
  • mcp__bank-check__find_bank untrusted-input
  • mcp__bank-check__bank_history untrusted-input
  • mcp__bank-check__estimate_deposit_coverage untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/bank-check/verify?hash=1d1d403979409da2413add54466f61cc34708874dbb82b0a2406b18d974cc9ba" | jq -e '.changed == false'

Pinned hash 1d1d40397940, from Nov 8, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/bank-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/bank-check
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/bank-check.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/bank-check)

Source: MCP Registry. Synced Nov 8, 2026, 03:17 UTC.

Zovo Bank Insurance Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zovo Bank Insurance Check MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Zovo Bank Insurance Check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Zovo Bank Insurance Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Zovo Bank Insurance Check MCP server have?

3 tools: 2 write, 1 read. bank_history, estimate_deposit_coverage and find_bank.

Does the Zovo Bank Insurance Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Zovo Bank Insurance Check MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Zovo Bank Insurance Check MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.