Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BankRegReports

REMOTE · API.BANKREGREPORTS.COM · 2 COMPONENTS

US bank and credit union data from call reports, UBPR, FDIC, NCUA, Fed NIC and SEC filings.

75 Trust /100

Last scanned (14 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security83
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 8445 tokens (~72/item across 116 items; 116 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 116 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 117 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1
    • Tool “prediction” rewrote its description, which is the text the model reads security
  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 72

    First indexed and scored.

Diagnostics

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://api.bankregreports.com/api/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bankregreports.com CN=YE1,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 67cd07710df930224bfef3bfc8db5c2484b
SANs: *.bankregreports.com, bankregreports.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.bankregreports.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
bankregreports.com. DS published 2371 13 Verified
api.bankregreports.com. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'nonce-JQnPbyINCqUlpYJp2DrMgg' 'strict-dynamic' https://challenges.cloudflare.com https://www.googletagmanager.com https://www.google-analytics.com https://www.clarity.ms; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: https://media.bankregreports.com https://files.stripe.com https://q.stripe.com https://www.google-analytics.com https://www.googletagmanager.com https://*.clarity.ms https://c.bing.com; connect-src 'self' https://media.bankregreports.com https://www.google-analytics.com https://analytics.google.com https://www.googletagmanager.com https://stats.g.doubleclick.net https://*.clarity.ms https://c.bing.com; frame-src 'self' https://checkout.stripe.com https://challenges.cloudflare.com https://open.spotify.com; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self' https://accounts.google.com
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy same-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self), usb=(), magnetometer=(), gyroscope=(), accelerometer=(), unload=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.bankregreports.com/api/mcp/ Verified 200
http (plaintext) http://api.bankregreports.com/api/mcp/ HTTPS enforced 301 https://api.bankregreports.com/api/mcp/
MCP tools · 116 exposed · ~8,153 tokens

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 →

Tool Tokens
sec_8k_body ~61

Item-by-item narrative bodies for one 8-K filing by accession number. (Source: SEC EDGAR 8-K.)

NameTypeReqDescription
accession_numberstringyesSEC accession number (e.g. 0001193125-24-000001).

No output schema declared.

No examples provided.

sec_8k_events ~71

8-K filings broken out by item number, the SEC material-event feed. (Source: SEC EDGAR 8-K.)

NameTypeReqDescription
limitinteger–Max item rows to return (default 100, max 500).
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_cusip ~88

CUSIP cross-reference - the 13F-holdings rollup for one security by CUSIP: issuer-name variants, how many filers/RSSDs hold it, and aggregate value and share counts. (Source: SEC Form 13F (aggregated by CUSIP).)

NameTypeReqDescription
cusipstringyes9-character CUSIP of the security.

No output schema declared.

No examples provided.

sec_facts ~52

Most recently filed XBRL concept facts from the bank's 10-K/Q. (Source: SEC EDGAR (XBRL).)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_filings ~42

SEC EDGAR filing index for one bank's registrant. (Source: SEC EDGAR.)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_form_13f ~50

Bank's institutional-manager Form 13F holdings, top positions by USD value. (Source: SEC Form 13F.)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_insider_txns ~45

Insider Form-4 transactions for one bank's registrant. (Source: SEC Form 4.)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_ma_events ~73

Mergers & acquisitions where this bank is on either side (SEC filings). (Source: SEC EDGAR 8-K / Schedule 13D.)

NameTypeReqDescription
limitinteger–Max rows to return (default 50, max 250).
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_officers ~55

Named officers and roles from the BHC's most recent Form 3/4/5 filings. (Source: SEC Form 3/4/5.)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

sec_peers ~65

SEC-derived peer-group assignment for this bank's registrant(s) - SIC industry, asset tier, exchange listing, and latest reported total assets. (Source: SEC EDGAR (company facts + SIC).)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

securities ~66

AFS / HTM holdings, unrealized gain/loss, sector breakdown. (Source: FFIEC Call Report (Schedule RC-B).) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

securities_trends ~83

Quarterly AFS/HTM portfolio with industry-wide overlay. (Source: FFIEC Call Report (Schedule RC-B).) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

NameTypeReqDescription
quartersinteger–Number of bank quarters (1-80, default 20).
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

structure ~43

Charter type, primary regulator, holding company chain, branches. (Source: FDIC Institution Directory + NIC.)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

structure_full ~52

Full ownership hierarchy for one bank: parent(s), subsidiaries, and NIC merger/transformation history. (Source: FFIEC NIC + FDIC directory.)

NameTypeReqDescription
rssd_idintegeryesFederal Reserve RSSD id.

No output schema declared.

No examples provided.

treasury_backdrop ~43

Treasury General Account balance, public debt and major foreign holders of Treasury securities. (Source: US Treasury.)

NameTypeReqDescription
periodstring–TIC month, YYYY-MM-DD.

No output schema declared.

No examples provided.

yield_curve ~55

US Treasury yield curve (long form). Pass ?latest=1 for the current curve. (Source: US Treasury.)

NameTypeReqDescription
lateststring–Return only the current curve.
tenor_codestring–One tenor series.

No output schema declared.

No examples provided.

Install

How do I install the BankRegReports MCP server?

BankRegReports is a hosted endpoint at https://api.bankregreports.com/api/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 · api.bankregreports.com

# add to Claude Code
claude mcp add --transport http com-bankregreports-bankregreports 'https://api.bankregreports.com/api/mcp/'
Common questions

What is the BankRegReports MCP server?

BankRegReports is an MCP server listed in the public MCP registry as com.bankregreports/bankregreports. US bank and credit union data from call reports, UBPR, FDIC, NCUA, Fed NIC and SEC filings. This page covers its hosted endpoint (https://api.bankregreports.com/api/mcp/).

Is the BankRegReports MCP server safe to use?

BankRegReports scores 75 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 BankRegReports MCP server expose?

BankRegReports exposes 116 tools: bank, bank_branch_map, bank_branches_counties, bank_branches_fdic, bank_branches_nic, and 111 more. Their descriptions and schemas cost roughly 8,153 tokens of context every time the server is loaded.

Does the BankRegReports MCP server require authentication?

No. We connected to BankRegReports without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BankRegReports MCP server still maintained?

BankRegReports 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 BankRegReports MCP server?

VerifyMCP ran 13 checks on BankRegReports, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.