Receita Federal PF
MCP server · api.mcp.ai · found in a public registry · checked since 2026-10-17
Timed out · latest check
Looks up a person's Brazilian tax registration status from CPF and birth date.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/3). What this means
Placed in Validate tax and bank numbers: Validate VAT, tax ID, IBAN and similar numbers by format, check digit or official lookup.
GET https://api.mcp.ai/p_receita_pfThe name is the registry's label, not ours. Not reviewed by a person. See 1116 endpoints from mcp.ai.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
1 passed, 1 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-20 | 1 | 1 | — | — | — | — | — | — |
| 7 dayssince 2026-10-20 | 1 | 1 | — | — | — | — | — | — |
| 30 dayssince 2026-10-20 | 1 | 1 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing nothing yet: no check of the current method has passed. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Identity, security and compliance / Verification / Validate tax and bank numbers (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/5): ✓ says what it does; ✗ its latest check did not pass.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Timed out no complete handshake within 10000 ms |
— |
cloudflare:EWR |
Live, MCP endpoint answered HTTP 406 | 185 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 3 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_118a82928ab9fd50