Brasil Planos de Saúde (ANS)
PYPI · BRASIL-PLANOS-SAUDE-MCP
Compare Brazilian health-plan operators with ANS open data: complaints, IDSS, fines, readjustments.
Available components
Last scanned (4 hours ago)
Scores higher than 76% of PyPI servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ThiagoJacobLannes/brasil-planos-saude-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1336 tokens (~267/item across 5 items; 5 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 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.
- 1 Nov 26 76
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 5 Nov 2026 · Analysed pypi/brasil-planos-saude-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ThiagoJacobLannes/brasil-planos-saude-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ThiagoJacobLannes/brasil-planos-saude-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3626791508 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:47b29898933c2776b791896981eea966350287e09e06a635c8700d177e93bc8a |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare_operators ~166
Side-by-side comparison of 2 to 8 health-plan operators on the ANS indicators. Use for "Amil or Bradesco Saúde?", "compare the plans my company offers". For each operator: 12-month complaints index (IGR) with the median of its size class and its position, latest IDSS, latest access-to-care band, number of fines in the last 5 years, and the latest small-group readjustment. Args: operators: Names, CNPJs or ANS registry numbers, e.g. ["Amil", "Bradesco Saúde", "SulAmérica"]. coverage: "medica" (default) or "odonto".
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | – | – |
| operators | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_operators ~316
Find Brazilian health-plan operators (operadoras de planos de saúde) registered with ANS. Use it to turn a brand the user mentions ("Unimed BH", "Amil", "Bradesco Saúde") into the ANS registry number, or to list operators by state, city or type. Largest first. Args: query: Part of the name, the CNPJ, or the ANS registry number. Accents and case don't matter. Several words must all match ("unimed campinas"). uf: State of the operator's head office, e.g. "SP", "MG". city: City of the head office, e.g. "Belo Horizonte". modality: e.g. "Cooperativa Médica", "Medicina de Grupo", "Seguradora", "Autogestão", "Odontologia de Grupo", "Filantropia", "Administradora de Benefícios" (substring match). include_cancelled: Also list operators whose registration was cancelled. limit: How many to return (default 10, max 50). Each operator: registro_ans, name, legal name, modality, head office, status, and beneficiaries and size class (porte) per coverage. Head office is not where the operator sells plans.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| include_cancelled | boolean | – | – |
| limit | integer | – | – |
| modality | – | – | – |
| query | – | – | – |
| uf | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
operator_profile ~362
Everything ANS publishes about one health-plan operator, to judge whether it is a good choice. Use for "is Hapvida good?", "how does Unimed Campinas rank on complaints?", "has SulAmérica been fined?". Returns: - registration: legal name, CNPJ, modality, head office, phone, status (active or cancelled, with date and reason), beneficiaries and size class; - complaints (IGR): latest month, 12-month average, the median of operators of the same size, the operator's position among them, and the monthly series; - quality (IDSS, 0-1, higher is better) for the last 5 years with its four dimensions; - access-to-care monitoring band (0 best, 3 worst) for the last published quarters; - fines applied by ANS: totals, last 5 years, status and the most recent cases; - the readjustment applied to its small-group pool (contracts with < 30 lives). Args: operator: Name (or part of it), CNPJ, or ANS registry number. If the name matches several operators, the largest active one is used and the others are listed in outras_operadoras_com_nome_parecido: check it is the one the user meant (Unimed, for example, is hundreds of separate cooperatives). coverage: "medica" or "odonto". Default: every coverage the operator has. Always quote the month/year of each figure and explain that IGR is lower-is-better and IDSS higher-is-better (see como_ler in the result).
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | – | – | – |
| operator | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
rank_operators ~301
Rank active health-plan operators by complaints or by quality. Use for "which large health plans get the fewest complaints?", "best-rated dental plans", "worst operators in Minas Gerais". Args: by: "reclamacoes" (12-month IGR, lower is better) or "qualidade" (latest IDSS, higher is better). coverage: "medica" (default) or "odonto". porte: "pequeno" (< 20k beneficiaries), "medio" (20k-100k) or "grande" (> 100k). ANS itself only compares operators of the same size. uf: Head-office state, e.g. "MG". Not the same as where it sells plans. modality: e.g. "Cooperativa Médica", "Medicina de Grupo", "Seguradora". min_beneficiaries: Skip operators smaller than this (default 5000; tiny ones swing wildly). worst_first: True to list the worst first. limit: How many to return (default 10, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | – |
| coverage | string | – | – |
| limit | integer | – | – |
| min_beneficiaries | integer | – | – |
| modality | – | – | – |
| porte | – | – | – |
| uf | – | – | – |
| worst_first | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
where_to_complain ~64
How to complain about a health plan in Brazil: the official ANS channels and the steps. Use when a user's plan denied or delayed a procedure, or they have a contract problem. Each channel was checked on the ANS consumer-service page (conferido_em).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Brasil Planos de Saúde (ANS) MCP server?
Brasil Planos de Saúde (ANS) runs locally as a PyPI package, launched with uvx brasil-planos-saude-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · brasil-planos-saude-mcp
claude mcp add thiagojacoblannes-brasil-planos-saude-mcp -- uvx brasil-planos-saude-mcp
What is the Brasil Planos de Saúde (ANS) MCP server?
Brasil Planos de Saúde (ANS) is an MCP server listed in the public MCP registry as io.github.ThiagoJacobLannes/brasil-planos-saude-mcp. Compare Brazilian health-plan operators with ANS open data: complaints, IDSS, fines, readjustments. This page covers its PyPI package (brasil-planos-saude-mcp).
Is the Brasil Planos de Saúde (ANS) MCP server safe to use?
Brasil Planos de Saúde (ANS) scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Planos de Saúde (ANS) MCP server expose?
Brasil Planos de Saúde (ANS) exposes 5 tools: find_operators, operator_profile, compare_operators, rank_operators, where_to_complain. Their descriptions and schemas cost roughly 1,209 tokens of context every time the server is loaded.
Is the Brasil Planos de Saúde (ANS) MCP server still maintained?
Brasil Planos de Saúde (ANS) 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 licence is the Brasil Planos de Saúde (ANS) MCP server under?
Brasil Planos de Saúde (ANS) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.