Brasil Data (pay-per-call via x402)
REMOTE · BRASIL-DATA-X402.WAGNER-PROC.WORKERS.DEV
Brazil CNPJ, CEP, Selic/IPCA/PTAX, holidays, banks/ISPB for agents. Pay per call in USDC (x402).
Available components
Last scanned (18 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1316 tokens (~146/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://brasil-data-x402.wagner-proc.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wagner-proc.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d671945bc35bfecb9a9f07cb6428ddfee9 |
| SANs: *.wagner-proc.workers.dev, wagner-proc.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of brasil-data-x402.wagner-proc.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://brasil-data-x402.wagner-proc.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://brasil-data-x402.wagner-proc.workers.dev/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bank_lookup ~146
Brazilian bank / payment institution lookup by COMPE code, ISPB, CNPJ or name, merged from Banco Central's STR participant list and active Pix participant list. Price: $0.005 USDC per call via x402; first call per tool per day is free. Example response: {"query":"260","count":1,"results":[{"ispb":"18236120","compe_code":"260","short_name":"NU PAGAMENTOS - IP","cnpj":"18236120000158","pix":{"participant":true}}]}
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | COMPE code (e.g. 260), ISPB (8 digits), CNPJ, or name |
No output schema declared.
No examples provided.
business_days ~169
Brazilian business-day calculator (national + banking holidays): count business days between two dates (DU convention, (from, to]) or add N business days to a date. Price: $0.005 USDC per call via x402; first call per tool per day is free. Example response: {"mode":"count","from":"2026-10-01","to":"2026-10-31","business_days":20,"calendar":"BR national + banking holidays"}
| Name | Type | Req | Description |
|---|---|---|---|
| add | integer | – | Business days to add (negative to subtract) |
| date | string | – | Base date YYYY-MM-DD (add/check mode) |
| from | string | – | Start date YYYY-MM-DD (count mode, exclusive) |
| to | string | – | End date YYYY-MM-DD (count mode, inclusive) |
No output schema declared.
No examples provided.
cep_lookup ~103
Brazilian postal code (CEP) to address: street, district, city, UF, IBGE city code, DDD. Free. Example response: {"cep":"01001000","street":"Praça da Sé","district":"Sé","city":"São Paulo","uf":"SP","region":"Sudeste","city_ibge":"3550308","ddd":"11"}
| Name | Type | Req | Description |
|---|---|---|---|
| cep | string | yes | CEP, 8 digits, e.g. 01001-000 |
No output schema declared.
No examples provided.
cnpj_lookup ~259
Brazilian company (CNPJ) registry lookup from Receita Federal open data, normalized: legal/trade name, status, CNAE activities, address, Simples/MEI, partners (QSA). Supports alphanumeric CNPJ. Price: $0.01 USDC per call via x402; first call per tool per day is free. Example response: {"cnpj":"19131243000197","legal_name":"OPEN KNOWLEDGE BRASIL","trade_name":"REDE PELO CONHECIMENTO LIVRE","status":{"description":"ATIVA","since":"2013-10-03"},"opened_on":"2013-10-03","main_activity":{"cnae":"9430800","description":"Atividades de associações de defesa de direitos sociais"},"address":{"street":"AVENIDA PAULISTA 37","district":"BELA VISTA","city":"SAO PAULO","uf":"SP","cep":"01311902"},"simples_nacional":{"opted":null},"partners":[{"name":"LUIZ CARLOS PINHO GUEDES","role":"Diretor"}]}
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | yes | CNPJ, 14 chars, with or without punctuation (alphanumeric supported) |
No output schema declared.
No examples provided.
holidays ~104
Brazilian national and banking holidays for a year (incl. Carnival, Good Friday, Corpus Christi, Nov 20). Free. Example response: {"year":2026,"holidays":[{"date":"2026-01-01","name":"Confraternização Universal","name_en":"New Year's Day","kind":"national"},{"date":"2026-02-16","name":"Carnaval (segunda-feira)","kind":"banking"}]}
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | – |
No output schema declared.
No examples provided.
ipca_inflation ~157
Brazilian official inflation (IPCA, IBGE via BCB): latest monthly change, 12-month accumulated, and monthly history. Price: $0.005 USDC per call via x402; first call per tool per day is free. Example response: {"latest_month":{"reference":"2026-09","value":0.82,"unit":"% a.m."},"accumulated_12m":{"reference":"2026-09","value":4.58,"unit":"%"},"history":[{"reference":"2026-08","value":-0.32},{"reference":"2026-09","value":0.82}]}
| Name | Type | Req | Description |
|---|---|---|---|
| months | integer | – | Months of history (default 12) |
No output schema declared.
No examples provided.
ptax_exchange_rate ~154
Official PTAX exchange rate (BRL per unit of foreign currency) published by Banco Central do Brasil for a given date; falls back to the last bulletin before a weekend/holiday. Price: $0.005 USDC per call via x402; first call per tool per day is free. Example response: {"currency":"USD","requested_date":"2026-10-14","quote_date":"2026-10-14","buy_brl":5.0435,"sell_brl":5.0441,"bulletin":"Fechamento PTAX"}
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO currency code (default USD) |
| date | string | – | YYYY-MM-DD (default today, BRT) |
No output schema declared.
No examples provided.
selic_rate ~131
Current Brazilian policy rate (Selic target set by Copom), effective daily Selic and CDI, annualized, from Banco Central do Brasil. Price: $0.005 USDC per call via x402; first call per tool per day is free. Example response: {"selic_target":{"value":13.75,"unit":"% a.a.","as_of":"2026-10-15"},"selic_daily_annualized":{"value":13.65,"unit":"% a.a."},"cdi_annualized":{"value":13.65,"unit":"% a.a."}}
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Brasil Data (pay-per-call via x402) MCP server?
Brasil Data (pay-per-call via x402) is a hosted endpoint at https://brasil-data-x402.wagner-proc.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · brasil-data-x402.wagner-proc.workers.dev
claude mcp add --transport http dev-workers-wagner-proc-brasil-data-x402-brasil- 'https://brasil-data-x402.wagner-proc.workers.dev/mcp'
What is the Brasil Data (pay-per-call via x402) MCP server?
Brasil Data (pay-per-call via x402) is an MCP server listed in the public MCP registry as dev.workers.wagner-proc.brasil-data-x402/brasil-data. Brazil CNPJ, CEP, Selic/IPCA/PTAX, holidays, banks/ISPB for agents. Pay per call in USDC (x402). This page covers its hosted endpoint (https://brasil-data-x402.wagner-proc.workers.dev/mcp).
Is the Brasil Data (pay-per-call via x402) MCP server safe to use?
Brasil Data (pay-per-call via x402) scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Brasil Data (pay-per-call via x402) MCP server expose?
Brasil Data (pay-per-call via x402) exposes 8 tools: cnpj_lookup, selic_rate, ipca_inflation, ptax_exchange_rate, business_days, and 3 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.
Does the Brasil Data (pay-per-call via x402) MCP server require authentication?
No. We connected to Brasil Data (pay-per-call via x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Brasil Data (pay-per-call via x402) MCP server still maintained?
Brasil Data (pay-per-call via x402) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Brasil Data (pay-per-call via x402) MCP server?
VerifyMCP ran 11 checks on Brasil Data (pay-per-call via x402), covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Brasil Data (pay-per-call via x402): Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.