CPFHub.io is a Brazilian CPF lookup 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.
LGPD-compliant · ~300ms response time · 99.9% uptime · 10M+ CPFs queried · works with Claude, Cursor, Windsurf, and any MCP-compatible agent.
Retorna informações sobre o saldo de créditos e plano do usuário. Requer autenticação via API key.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Sua API key do CPFHub (opcional se configurada via env) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It discloses the authentication requirement and indicates a read-only retrieval ('Retorna informações'), but it does not mention potential rate limits, whether the call consumes quota, or the output format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler. It frontloads the core purpose and then adds the auth prerequisite.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, so the description should clarify what information is returned. It gives a high-level idea ('saldo de créditos e plano') but lacks specifics like field names or structure, leaving some ambiguity despite the simple scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter (api_key) is fully described in the schema with 100% coverage, so the description adds no additional parameter semantics. The schema already explains the key is optional if configured via environment, matching the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns information about the user's credit balance and plan, which is a specific verb+resource. This distinguishes it from the sibling lookup_cpf, which is a lookup operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: when needing quota/plan information. It also notes the authentication prerequisite. It doesn't explicitly discuss alternatives, but no alternative quota tool is listed among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Consulta informações de um CPF brasileiro. Retorna nome, data de nascimento e gênero. Requer autenticação via API key.
| Name | Required | Description | Default |
|---|---|---|---|
| cpf | Yes | CPF a ser consultado (apenas números ou formatado) | |
| api_key | No | Sua API key do CPFHub (opcional se configurada via env) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It states that authentication via API key is required and specifies the output fields. It does not detail error handling or confirm read-only behavior, but 'consulta' implies a safe read operation, making the description reasonably transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the main purpose, followed by return fields and authentication. Every sentence provides necessary information without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, so the description correctly explains what is returned (nome, data de nascimento, gênero) and mentions the auth prerequisite. It does not cover error cases or response format, but for a simple lookup tool with two parameters, this is largely complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully describes both parameters (cpf and api_key) with 100% coverage. The description adds the auth requirement context but does not elaborate on parameter syntax or formatting beyond what the schema provides, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb ('Consulta informações') and resource ('CPF brasileiro'), and lists the returned fields (nome, data de nascimento, gênero). It is distinct from the sibling get_quota_info, which focuses on quota information.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool (querying Brazilian CPF information) and notes the auth requirement via API key. It does not explicitly mention when not to use it or name alternatives, but the sibling tool is obviously different in purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
The two tools are completely distinct: one retrieves quota/plan information, the other performs a CPF lookup. There is no overlap in their purposes, making selection unambiguous.
Both tools follow a consistent verb_noun snake_case pattern (get_quota_info, lookup_cpf). The naming style is uniform and predictable.
With only 2 tools, the server feels thin for a CPF lookup service, but it covers the essential actions (lookup and quota check). The count is borderline acceptable for the narrow scope.
The core functionality (lookup_cpf) and a supporting quota tool are present, but the surface lacks potentially expected operations like batch lookup, history, or detailed report generation, leaving noticeable gaps for a fuller service.