CPFHub.io is a Brazilian CPF lookup and validation API built for developers. This MCP server lets AI agents query CPF data — including full name, gender, and date of birth — directly from a conversation, without writing any HTTP code. ## Available tools - **`lookup_cpf`** — Query a Brazilian CPF number. Returns full name, gender, and date of birth. - **`get_quota_info`** — Check your current credit balance and plan details. ## Key specs - ~300ms average response time · 99.9% uptime - LGPD-compliant · 10M+ CPFs queried · 1,300+ active companies - Works with Claude, Cursor, Windsurf, and any MCP-compatible agent - Same quota as the REST API — no separate credit pool ## Common use cases KYC & identity verification · fraud prevention · customer onboarding · fintech · e-commerce · healthcare · betting & iGaming · ERP/MRP integration ## Plans - **Free:** 50 queries/month — no credit card required - **Pro:** R$149/month for 1,000 queries (R$0.15 per extra query) - **Enterprise:** cust
CPFHub.io - API de Consulta de CPF is a remote MCP server published at api.cpfhub.io. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 676 ms, a delay an agent will notice. It offers a narrow, focused set of 2 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
lookup_cpf — No input schema details for CPF number parameter or API key authentication.get_quota_info — No input schema details for API key authentication.Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/admin-noez-cpfhub)<a href="https://mcpmetrics.io/servers/admin-noez-cpfhub"><img src="https://mcpmetrics.io/badge/admin-noez/cpfhub/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 11:20:19 | Legacy | 400 | 559 | 200 | 541 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 685 | 200 | 676 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 689 | 200 | 692 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 679 | 200 | 670 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 735 | 200 | 991 | 2025-11-25 |
| 2026-09-11 01:59:45 | Legacy | 400 | 434 | 200 | 434 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 330 | 401 | 378 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.