Onça Setorial
REMOTE · TAMANDUA.ONSSA.ORG
Brazilian regulator data: CVM filings, dam safety, airline punctuality, rules, enforcement
Available components
Last scanned (20 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1534 tokens (~191/item across 8 items; 8 tools + 0 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, 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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 64
First indexed and scored.
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 21 Nov 2026 · Probed https://tamandua.onssa.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tamandua.onssa.org | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 14 Sept 2026 | 30 Mar 2027 | RSA 2048 | SHA256-RSA | f75fc5acfca58a903dce98cdecf018e |
| SANs: tamandua.onssa.org | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tamandua.onssa.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| onssa.org. | 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://tamandua.onssa.org/mcp | Verified | 200 | |
| http (plaintext) | http://tamandua.onssa.org/mcp | Inconclusive | 403 |
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 →
airline_punctuality Airline cancellations and delays (ANAC VRA) ~97
Per airline, from ANAC's latest monthly VRA file: scheduled flights, cancellations and departures more than 15 minutes late, with rates. Use for 'which Brazilian airline cancels or delays most'. Needs the aviation sector licensed. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Optional. One airline by name, e.g. 'Azul', 'LATAM'. |
No output schema declared.
No examples provided.
base_rates Regulatory base rates (Outcome Ledger), labelled estimativa ~152
How long regulatory processes take and how they end, measured over each regulator's own records (e.g. ANEEL fine → appeal → decision; ANVISA public consultation → published rule): N, median, quartiles and range per figure, with method and limits. Figures are estimativa; a figure below the minimum N is withheld and has no number. Use for 'how long until ANVISA turns a consultation into a rule'. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| study | string | – | Optional. A study id (e.g. 'aneel_enforcement'), a regulator ('ANVISA') or a sector. Default: every study for your sectors. |
No output schema declared.
No examples provided.
company_financials Company financials from CVM filings (DFP/ITR) ~219
Revenue, net income, assets, equity, EBIT, D&A for a Brazilian listed company in your licensed sectors, from its own CVM filings: the annual DFP and the latest quarterly ITR (year-to-date). Derived values (EBITDA, net debt, margins, leverage) are returned separately and labelled estimativa. A company with no CVM filing says so (closed capital or IR-page only) instead of returning numbers. Use for 'what was X's revenue / net income / debt'. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Company name or Onça Setorial id, e.g. 'Vale', 'Eletrobras', 'Hypera'. |
| period | string | – | Optional. '2025' or '2025-12-31' for the annual DFP; '2T26', '2026Q2' or '2026-06-30' for a quarterly ITR. Default: every statement on file. |
No output schema declared.
No examples provided.
consultation_outcome What one ANVISA public consultation became (Outcome Ledger) ~179
For one ANVISA consulta pública: its opening date and contribution window, whether a norm resulted (only links ANVISA itself publishes; an older norm the consultation revises is shown as prior, not as its result), the norm and its date, days elapsed, and the base rate for context (consultation → norm median days and the share of consultations that produce a norm; estimativa). Use for 'did CP 1.234/2023 become a rule, and how long did it take'. Needs the pharmaceutical sector licensed. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| consultation | string | yes | The consultation, e.g. 'CP 1.234/2023', 'Consulta Pública nº 1234, de 2023', 'consulta-publica-1234:2023'. |
No output schema declared.
No examples provided.
dam_safety Mining dam safety per company (ANM SIGBM) ~113
Tailings-dam safety per mining company from ANM's SIGBM register: number of dams, dams at an emergency level or at alert, high risk category (CRI) and high associated potential damage (DPA), and the worst emergency level. Use for 'which mining companies have dams in emergency'. Worst first. Needs the mining sector licensed. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Optional. One company by name, e.g. 'Vale'. |
No output schema declared.
No examples provided.
enforcement_process One enforcement process's timeline (Outcome Ledger) ~268
The dated steps of ONE sanctioning process from the regulator's own records: an ANEEL auto de infração (issued, received, appeal, decisions, closure), an ANS penalty case (1st and 2nd instance, payment, archiving) or an ANATEL PADO process (phases, dated when first observed). Returns the regulator, the source url, the company only when the record binds it by CNPJ to a tracked company, and each span's days next to that regulator's published base rate (median, quartiles, N; estimativa). Use for 'where is auto 0001/2019-AGEPAN-SFE and is it slow'. Needs the regulator's sector licensed (ANEEL energy, ANS health, ANATEL telecom). Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| process | string | yes | The process id: ANEEL auto number ('0001/2019-AGEPAN-SFE') or SEI process ('48500.026432/2025-01'), ANS demanda or processo ('33902.499206/2016-46'), or ANATEL PADO process number. |
| regulator | string | – | Optional. Restrict the lookup to one regulator. |
No output schema declared.
No examples provided.
regulatory_events Regulatory acts and deadlines for a sector ~143
For one of your licensed sectors: public consultations and other regulatory deadlines falling due in the next `days`, then the acts published in the current window (Diário Oficial, the sector regulator, Câmara/Senado), each with its lifecycle stage and a link to the act. Use for 'which regulatory deadlines are coming up in energy'. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Optional. Deadline horizon in days, default 90. |
| sector | string | yes | Sector: energy, health, pharmaceutical, telecom, logistics, last_mile, agro, retail, mining or aviation (Portuguese names work too). |
No output schema declared.
No examples provided.
rule_enforcement ANVISA sanctions citing one rule (Outcome Ledger) ~208
For one ANVISA rule (RDC or IN): its publication date and source, the ANVISA sanctions in the Diário Oficial that cite it as breached (date, act url, and the company only when the act names exactly one company by CNPJ), their count, the lag from publication to the first citing sanction when observable, and, counted apart, refusals of companies' own requests that cite the rule as grounds (these are NOT sanctions). Each act counts once. Use for 'who was sanctioned under RDC 47/2013 and since when'. Needs the pharmaceutical sector licensed. Deterministic: computed from official datasets, no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | The rule, e.g. 'RDC 47/2013', 'RDC nº 47, de 2013', 'rdc-anvisa-47:2013', 'IN 9/2014'. Without a year, every year on record for that number. |
No output schema declared.
No examples provided.
How do I install the Onça Setorial MCP server?
Onça Setorial is a hosted endpoint at https://tamandua.onssa.org/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 · tamandua.onssa.org
claude mcp add --transport http marcioyoshida-onca-setorial 'https://tamandua.onssa.org/mcp'
What is the Onça Setorial MCP server?
Onça Setorial is an MCP server listed in the public MCP registry as io.github.marcioyoshida/onca-setorial. Brazilian regulator data: CVM filings, dam safety, airline punctuality, rules, enforcement. This page covers its hosted endpoint (https://tamandua.onssa.org/mcp).
Is the Onça Setorial MCP server safe to use?
Onça Setorial scores 68 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 Onça Setorial MCP server expose?
Onça Setorial exposes 8 tools: company_financials, dam_safety, airline_punctuality, regulatory_events, base_rates, and 3 more. Their descriptions and schemas cost roughly 1,379 tokens of context every time the server is loaded.
Does the Onça Setorial MCP server require authentication?
No. We connected to Onça Setorial without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Onça Setorial MCP server still maintained?
Onça Setorial is still listed as active in the MCP registry. We last reached this channel on 21 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 Onça Setorial MCP server?
VerifyMCP ran 12 checks on Onça Setorial, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Onça Setorial: 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.