CFPB consumer complaints
REMOTE · CFPB-COMPLAINTS-ANALYSIS.FLY.DEV
CFPB consumer complaints: 18M records, 3.85M archived narratives. Search, counts, trends.
Available components
Last scanned (13 hours ago)
Scores higher than 46% of remote servers
Unreachable for 1 day in a row. Last reached 17 Oct 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 18 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.27 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 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.
- 12 Oct 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.
- 10 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Oct 26 59
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 18 Oct 2026 · Probed https://cfpb-complaints-analysis.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| 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 insecure
Validation of cfpb-complaints-analysis.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cfpb-complaints-analysis.fly.dev/mcp | Unreachable | ||
| http (plaintext) | http://cfpb-complaints-analysis.fly.dev/mcp | HTTPS enforced | 301 | https://cfpb-complaints-analysis.fly.dev/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 →
company_profile ~84
Profile of one company (or all name variants via company_contains): totals, first/last complaint, top products, issues, states, response outcomes, yearly counts. Counts are not adjusted for company size. Optional date_from/date_to/product.
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| company_contains | – | – | – |
| date_from | – | – | – |
| date_to | – | – | – |
| product | – | – | – |
No output schema declared.
No examples provided.
compare_companies ~99
Side-by-side comparison of up to 6 companies on the same filters: complaints, timely_rate, relief rates, top product and top issue each. Each entry in companies is matched as a substring on the company name (all variants combined). Counts are not adjusted for company size.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| date_from | – | – | – |
| date_to | – | – | – |
| issue | – | – | – |
| product | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
complaint_counts ~324
Count complaints, optionally grouped. group_by is one or two of: year, quarter, month, product, sub_product, issue, sub_issue, company, state, company_response, company_public_response, submitted_via, timely_response. Returns complaints, timely_rate, monetary_relief_rate, nonmonetary_relief_rate, in_progress_rate per group (rates are fractions of that group's complaints). Counts are raw complaint counts, not adjusted for company size. In progress and Untimely response are CFPB response categories, not outcomes. Filters: company (exact name as in find_company), company_contains (substring), product, sub_product, issue, product: CFPB renamed credit reporting twice, so it appears under three product names (use list_values field=product), company_response (exact CFPB value, case-insensitive), submitted_via, state (2 letters), tag (e.g. 'Servicemember', 'Older American'), timely (true/false), date_from/date_to (YYYY-MM-DD or YYYY-MM, on date received).
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| company_contains | – | – | – |
| company_response | – | – | – |
| date_from | – | – | – |
| date_to | – | – | – |
| group_by | – | – | – |
| has_narrative | – | – | – |
| issue | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| order_by | string | – | – |
| product | – | – | – |
| state | – | – | – |
| sub_product | – | – | – |
| submitted_via | – | – | – |
| tag | – | – | – |
| timely | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
count_narratives ~158
Count how many archived narratives match a keyword search, optionally grouped by year, month, product, company, issue or state. Same search and filter arguments as search_narratives (without the slower issue/response filters). Use this for 'how many complaints mention X'. Counts only complaints that have a narrative (through 2026-08-14), not all complaints. Narrow with date, company or product when you can.
| Name | Type | Req | Description |
|---|---|---|---|
| any_of | – | – | – |
| company | – | – | – |
| company_contains | – | – | – |
| date_from | – | – | – |
| date_to | – | – | – |
| group_by | – | – | – |
| limit | integer | – | – |
| phrase | – | – | – |
| product | – | – | – |
| query | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
dataset_info ~34
What this dataset is: row counts, date ranges, narrative coverage, and the narrative freeze. Call first when unsure about coverage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_company ~92
Find companies by name. CFPB lists the same firm under variants and subsidiaries (e.g. 'EQUIFAX, INC.', 'Equifax Information Services LLC'), so this returns every matching name with complaint counts and first/last dates; pass the exact names you want to other tools via company, or use company_contains for all variants at once.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_complaint ~39
One complaint by its CFPB Complaint ID: all structured fields and, when archived, the full narrative.
| Name | Type | Req | Description |
|---|---|---|---|
| complaint_id | integer | yes | – |
No output schema declared.
No examples provided.
list_values ~202
List the values of a field with complaint counts, to find exact product/issue/response names. field is one of: product, sub_product, issue, sub_issue, company_response, company_public_response, submitted_via, state, timely_response. Optional search narrows by substring; product narrows issues to that product. Filters: company (exact name as in find_company), company_contains (substring), product, sub_product, issue, product: CFPB renamed credit reporting twice, so it appears under three product names (use list_values field=product), company_response (exact CFPB value, case-insensitive), submitted_via, state (2 letters), tag (e.g. 'Servicemember', 'Older American'), timely (true/false), date_from/date_to (YYYY-MM-DD or YYYY-MM, on date received).
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | – |
| limit | integer | – | – |
| product | – | – | – |
| search | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_narratives ~269
Keyword search over archived complaint narratives (frozen at 2026-08-14; CFPB stopped publishing them in September 2026). query: words that must all appear (case-insensitive), or use phrase for an exact phrase, or any_of for alternatives. Returns a snippet per complaint plus its structured fields, newest first (date order, not relevance-ranked: every result contains all your words); use get_complaint for the full text. Searches scan text, so narrow with date_from/date_to, company/company_contains, product or state when you can: an unfiltered search over all years can time out. Filters: company, company_contains, product, state (2 letters), date_from/date_to (YYYY-MM-DD or YYYY-MM), plus issue, sub_product, company_response, timely, tag (these are slower).
| Name | Type | Req | Description |
|---|---|---|---|
| any_of | – | – | – |
| company | – | – | – |
| company_contains | – | – | – |
| company_response | – | – | – |
| date_from | – | – | – |
| date_to | – | – | – |
| issue | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| phrase | – | – | – |
| product | – | – | – |
| query | – | – | – |
| state | – | – | – |
| sub_product | – | – | – |
| tag | – | – | – |
| timely | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
trend ~221
Complaints over time (month, quarter or year), for one filter set. Set period to month, quarter or year. The latest period is partial. In progress and Untimely response are CFPB response categories, not outcomes. Filters: company (exact name as in find_company), company_contains (substring), product, sub_product, issue, product: CFPB renamed credit reporting twice, so it appears under three product names (use list_values field=product), company_response (exact CFPB value, case-insensitive), submitted_via, state (2 letters), tag (e.g. 'Servicemember', 'Older American'), timely (true/false), date_from/date_to (YYYY-MM-DD or YYYY-MM, on date received).
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| company_contains | – | – | – |
| company_response | – | – | – |
| date_from | – | – | – |
| date_to | – | – | – |
| issue | – | – | – |
| period | string | – | – |
| product | – | – | – |
| state | – | – | – |
| submitted_via | – | – | – |
| tag | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the CFPB consumer complaints MCP server?
CFPB consumer complaints is a hosted endpoint at https://cfpb-complaints-analysis.fly.dev/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 · cfpb-complaints-analysis.fly.dev
claude mcp add --transport http bnovarini-cfpb-complaints-analysis 'https://cfpb-complaints-analysis.fly.dev/mcp'
What is the CFPB consumer complaints MCP server?
CFPB consumer complaints is an MCP server listed in the public MCP registry as io.github.bnovarini/cfpb-complaints-analysis. CFPB consumer complaints: 18M records, 3.85M archived narratives. Search, counts, trends. This page covers its hosted endpoint (https://cfpb-complaints-analysis.fly.dev/mcp).
Is the CFPB consumer complaints MCP server safe to use?
CFPB consumer complaints scores 63 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 CFPB consumer complaints MCP server expose?
CFPB consumer complaints exposes 10 tools: dataset_info, list_values, find_company, complaint_counts, trend, and 5 more. Their descriptions and schemas cost roughly 1,522 tokens of context every time the server is loaded.
Does the CFPB consumer complaints MCP server require authentication?
Its publisher declares no required credentials for CFPB consumer complaints. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the CFPB consumer complaints MCP server still maintained?
CFPB consumer complaints is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.