Remote MCP server that looks up Brazilian individual registration data from a CPF and name, plus platform tools for marketplace, auth and feedback.
What you can do
Look up Brazilian individual registration data from a CPF and name, billed per query with prepaid credit
Search the in-platform marketplace for MCPs and tools by intent, describe one, and run them
Check connection status, pending provider connections and connect URLs
Inspect the toolkit state: installed MCPs, connected accounts and exposed tool counts
Authenticate with an access token, show platform and adapter versions, and report bugs or feedback
When to use it
Useful when an assistant needs to check Brazilian individual registration data from a CPF and name, or when you want a single hosted entry point for discovering and running other MCPs from the same platform.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. No credentials are declared for the lookup itself, but queries are paid per use with prepaid credit. The authenticate tool expects an access token, optionally supplied as an Authorization Bearer header.
Before you install
Lookups are charged per query against prepaid credit, so usage spends money. The server handles CPF and name data, which is personal data even when drawn from public sources. The authenticate tool asks for an access token; treat it as a secret. The report_bug tool asks for recent conversation messages, which may contain sensitive content.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.mcp-dir%2Fregistro_pf_br-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Dados cadastrais de uma pessoa física no Brasil a partir do CPF e nome. Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago. Consulta informação de ACESSO PÚBLICO em bases e fontes oficiais (a mesma disponível ao cidadão), não é dado privado nem sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).
Show the current MCP platform and adapter versions.
Takes no parameters.
report_bug
Report Bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Parameterscontextmessagerequiredconversation
connect
Connection Status
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Takes no parameters.
toolkit_info
Toolkit Info
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Takes no parameters.
marketplace
Marketplace
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more
authenticate
Authenticate
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
Parameterstoken
Version history
1
v0.1.0LatestSep 16, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.
