A customer enters a CPF during signup, but your system still needs to know whether the name and birth date line up with it. Checking those details by hand does not scale. Building a data lookup into your own software means choosing a source, managing requests and deciding what to do with the response.
CPFHub.io is a Brazilian CPF lookup service that packages those checks as a REST API, a web panel and a remote MCP server for AI agents. Its job is narrower than identity verification in general: it looks up CPF data and returns selected details. The useful question is which kind of lookup you need, since the available results depend on the route you use.
Three ways to check a CPF
The simplest request sends a CPF and returns a name, gender and birth date. The developer describes the typical response time as about 150 milliseconds. That makes this mode suited to a registration flow that needs to compare submitted details with a lookup, rather than a broad background check. The simple lookup does not return registration status or death-year information.
For those details, CPFHub offers a real-time lookup. It requires both the CPF and the person's birth date, then checks with Brazil's Receita Federal at request time. The response can include registration status, a death year and a consultation receipt with a control code. The developer says this typically takes about a second. The death information is limited to the year, not the day or month, and a birth-date mismatch can prevent the lookup from succeeding.
The third option is for existing records rather than one-at-a-time onboarding. Bulk jobs accept a list or file, with the landing page describing CSV and text uploads in the panel and batches of up to 10,000 CPFs. They return the simple-lookup fields, not the additional real-time status information. Processing time depends on the batch size. The same account and credit balance cover the different lookup types.
Where the API and MCP server fit
For software integrations, the REST API uses an API key and returns structured data. The landing page shows a request using an x-api-key header and provides public OpenAPI documentation. In practical terms, an application can send a CPF, receive a response and decide how to use the returned fields in its own workflow. The service also offers a web panel for individual lookups or file uploads, so using the product does not necessarily mean writing an integration first.
The MCP server is a separate way to expose lookups to compatible AI agents as tools. The developer names three: lookup_cpf, lookup_cpf_realtime and get_quota_info. That gives an agent a route to request a lookup or check account quota, rather than relying on a person to copy results into a chat. It does not make the underlying data more extensive: the results still depend on whether the agent calls the simple or real-time lookup, and the latter still needs a birth date.
CPFHub has a free plan and a paid upgrade. That gives a developer a way to try the service before committing to a paid tier, but the free allowance is finite, so it is not a basis for assuming a production workload will remain free.
The data boundary matters
There is an important distinction between the two data paths. According to CPFHub's own explanation, simple and bulk lookups use its validation database, assembled from licensed private providers and public official sources. They are not described as live checks with the Receita Federal. The real-time route is the one that contacts the federal service at the time of the request and returns a receipt. A team that needs current registration status should not treat a fast simple lookup as a substitute.
There are also operational and privacy considerations. CPFHub says it records each consultation, including the CPF, result, date and account, for history, billing, auditing and fraud prevention. It places responsibility on the customer to establish a lawful basis and purpose for each query. Since CPF data is sensitive personal information in practice, teams should review those handling and retention terms before sending real customer records. An API response does not settle whether a particular use is appropriate.
A focused lookup service, not full identity proofing
CPFHub's value is in making a defined lookup available in a few forms: a quick API call, a more detailed request against the federal source, a bulk validation job, or a tool an MCP-compatible agent can invoke. It does not, based on the described product, provide liveness checks, document verification or face matching. Those appear as planned offerings on the landing page, not capabilities to rely on now.
This is for Brazilian services that need CPF lookup fields inside onboarding, account checks or a data-cleaning workflow, especially teams comfortable deciding how to use and protect the results. It is not for teams looking for complete identity proofing, or for anyone who needs every lookup to return live registration status without supplying a birth date.
Brazilian CPF lookup API with an MCP server for AI agents