Consumer Financial Protection Bureau complaint database MCP server (free, no auth)
CFPB MCP has 5 well-named, read-only tools with clear descriptions (avg 156 chars, within baseline 194). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are NOT documented, LLMs cannot predict response structure for downstream chaining. Parameter descriptions lack format constraints (e.g., date format examples, enum values for product categories). No error handling guidance. Missing required field declarations in schemas (only cfpb_company_complaints and cfpb_get_complaint mark required params). No pagination guidance despite API returning potentially large result sets.
Get recent consumer complaints for a specific company, sorted by newest first. Returns complaint details and company response information.
Get full details for a single consumer complaint by its complaint ID number.
Get complaint counts broken down by product category. Optionally filter by company and/or date range.
Search the CFPB consumer complaint database. Filter by keyword, company, product category, and date range. Returns complaint narratives, company responses, and resolution status.
Get the companies with the most consumer complaints in a given date range. Useful for identifying which companies receive the most complaints.
Output schemas not documented. LLMs cannot predict response structure (fields, types, nested objects) for downstream tool chaining or data extraction. Formatters like formatComplaint() exist but are not exposed in tool definitions.
Parameter descriptions lack format constraints. 'start_date' and 'end_date' say 'YYYY-MM-DD format' but no enum or pattern validation. 'product' accepts free-form strings instead of enums (Credit card, Mortgage, Student loan, etc. are listed in description but not as JSON Schema enum).
Missing required field declarations. cfpb_search_complaints, cfpb_top_companies, and cfpb_product_breakdown do not declare which parameters are required vs optional. LLMs may omit critical filters, causing ambiguous or overly broad queries.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
No pagination or result-limiting guidance. Tools return hits.total but no next_cursor or offset/page parameters. Large result sets (e.g., 'overdraft fees' across all companies) could exceed context window. Baseline pattern expects pagination for list-like tools.
No error handling or recovery guidance. If CFPB API returns 4xx/5xx, callTool throws generic 'CFPB API error: {status}' with no actionable next step. LLM cannot distinguish retryable (503) from user-fixable (400 bad date format) from fatal errors.