voa-tiss
REMOTE · TISS-API.VOA.HEALTH
Ferramentas para validar documentos TISS e consultar TUSS, operadoras e dados da ANS.
Available components
Last scanned (18 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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
- Authorisation not fully verified: no authorisation is required to call this server, and 26 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 2098 tokens (~61/item across 34 items; 26 tools + 8 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 3% of tool parameters carry a description.Partial
- 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 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 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.
- 29 Oct 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.
- 27 Oct 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: voa-tiss → tiss security
- New tool “tiss_referencia” functional
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1614 → 1949 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → fair functional
- New tool “tiss_autorizacao_build” functional
- New tool “tiss_autorizacao_check” functional
- New tool “tiss_autorizacao_parse” functional
- New tool “tiss_rejection_map” functional
- New tool “tiss_sandbox_autorizacao” functional
- “tiss_audit” added an optional parameter “operadora” cosmetic
- “tiss_sandbox_enviar_lote” added an optional parameter “registro_ans” cosmetic
- 22 Oct 26 65
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 4 Nov 2026 · Probed https://tiss-api.voa.health/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tiss-api.voa.health | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 598817c8256e7f15de17a47ad268cebcee9 |
| SANs: tiss-api.voa.health | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tiss-api.voa.health. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| health. | present | 42514 | 13 | Verified |
| voa.health. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tiss-api.voa.health/mcp | Verified | 200 | |
| http (plaintext) | http://tiss-api.voa.health/mcp | HTTPS enforced | 308 | https://tiss-api.voa.health/mcp |
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 →
buscar_docs ~56
Busca trechos da documentação local da biblioteca. Quando usar: para encontrar instruções e referências da API. Quando não usar: para consultar dados clínicos ou códigos específicos.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
| texto | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| resultados | array | yes | – |
No examples provided.
glosa_explain ~53
Explica um código da Tabela 38 da ANS. Quando usar: ao interpretar uma glosa recebida. Quando não usar: para validar ou corrigir o lote.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | string | yes | – |
| descricao | string | yes | – |
| fonte | object | yes | – |
| grupo | string | yes | – |
| orientacao | object | yes | – |
No examples provided.
operadora_lookup ~68
Busca operadoras ativas pelo nome, registro, CNPJ ou localidade. Quando usar: para localizar uma operadora na base pública. Quando não usar: para consultar vínculos hospitalares; use tiss_rede.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
| texto | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| resultados | array | yes | – |
No examples provided.
operadora_perfil ~64
Consulta o cadastro e a série semestral de glosa e pagamento de uma operadora na ANS. Quando usar: para conhecer uma operadora pelo registro ANS. Quando não usar: para buscar operadoras por nome.
| Name | Type | Req | Description |
|---|---|---|---|
| registro_ans | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| indicadores | object | yes | – |
| razao_social | string | yes | – |
| registro_ans | string | yes | – |
No examples provided.
operadora_rede ~68
Consulta os estabelecimentos vinculados a uma operadora. Quando usar: para identificar unidades da rede por UF. Quando não usar: para buscar o cadastro geral; use operadora_lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
| registro | string | yes | – |
| uf | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| atualizado_em | string | yes | – |
| estabelecimentos | array | yes | – |
| fonte | string | yes | – |
| por_uf | object | yes | – |
| registro_ans | string | yes | – |
| total | integer | yes | – |
No examples provided.
tiss_apply_fixes ~72
Aplica correções JSON Patch de um relatório ao lote. Quando usar: depois de tiss_validate ou tiss_audit com achados corrigíveis. Quando não usar: para inventar dados ausentes; peça-os ao usuário.
| Name | Type | Req | Description |
|---|---|---|---|
| lote | object | yes | – |
| report | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| lote | object | yes | – |
No examples provided.
tiss_audit ~80
Audita um lote JSON com regras locais e contexto da operadora. Quando usar: para identificar inconsistências administrativas. Quando não usar: para aplicar correções; use tiss_apply_fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| contexto | object | – | – |
| data | string | – | – |
| lote | object | yes | – |
| operadora | string|object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| decisao | object | – | – |
| findings | array | yes | – |
| valid | boolean | yes | – |
| version | string|null | yes | – |
No examples provided.
tiss_autorizacao_build ~41
Gera XML TISS 4.03.00 para solicitação ou resposta de autorização SP/SADT.
| Name | Type | Req | Description |
|---|---|---|---|
| mensagem | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
| xml | string | yes | – |
No examples provided.
tiss_autorizacao_check ~49
Valida uma solicitação SP/SADT e retorna uma decisão explicável.
| Name | Type | Req | Description |
|---|---|---|---|
| contexto | object | – | – |
| solicitacao | object | – | – |
| xml | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
tiss_autorizacao_parse ~32
Interpreta solicitações e respostas de autorização SP/SADT.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| mensagem | object | yes | – |
No examples provided.
tiss_build ~95
Gera o XML TISS 4.03.00 de um lote em JSON, com hash do epílogo. Consulte tiss://schemas/lote para o esquema estrutural. Quando usar: depois de validar o lote em JSON sem erros. Quando não usar: para corrigir achados; use tiss_apply_fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| lote | object | yes | Schema estrutural disponível em tiss://schemas/lote. |
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
| xml | string | yes | – |
No examples provided.
tiss_dominio ~90
Consulta tabelas e códigos de domínio TISS. Quando usar: para localizar um código ou termo de domínio. Quando não usar: para buscar procedimentos TUSS; use tuss_search.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | string | – | – |
| data | string | – | – |
| include_expired | boolean | – | – |
| limite | integer | – | – |
| tabela | string | – | – |
| texto | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| resultados | array | – | – |
| tabelas | array | – | – |
No examples provided.
tiss_hash ~55
Calcula o hash do epílogo de um XML TISS. Quando usar: para conferir a integridade do XML. Quando não usar: para validar o conteúdo; use tiss_validate.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No examples provided.
tiss_parse_demonstrativo ~46
Lê decisões de um demonstrativo. Quando usar: para identificar pagamentos e glosas. Quando não usar: para validar lotes.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| decisoes | array | yes | – |
No examples provided.
tiss_plan_reconciliation ~89
Propõe vínculos entre decisões e guias. Quando usar: após ler um demonstrativo. Quando não usar: para alterar guias.
| Name | Type | Req | Description |
|---|---|---|---|
| decisoes | array | yes | – |
| guias | array | yes | – |
| id_key | string | – | – |
| operadora_key | string | – | – |
| prestador_key | string | – | – |
| status_key | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ambiguas | array | yes | – |
| propostas | array | yes | – |
| sem_par | array | yes | – |
No examples provided.
tiss_rede ~73
Consulta as operadoras vinculadas a um CNPJ ou CNES. Quando usar: para identificar vínculos de um estabelecimento. Quando não usar: para buscar o cadastro geral; use operadora_lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| cnes | string | – | – |
| cnpj | string | – | – |
| limite | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| atualizado_em | string | yes | – |
| fonte | string | yes | – |
| operadoras | array | yes | – |
| total | integer | yes | – |
No examples provided.
tiss_referencia ~108
Consulta valores unitários de referência D-TISS da ANS por procedimento TUSS. Quando usar: para comparar valores informados por UF, modalidade, porte e semestre. Quando não usar: para glosa ou preço contratado de uma operadora; use as ferramentas de operadoras.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | string | yes | – |
| modalidade | string | – | – |
| porte | string | – | – |
| semestre | string | – | – |
| tabela | string | – | – |
| uf | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| atualizado_em | string | yes | – |
| aviso | string|null | yes | – |
| fonte | string | yes | – |
| minimo_n | integer | yes | – |
| referencia | object|null | yes | – |
| semestre | string | yes | – |
No examples provided.
tiss_rejection_map ~110
Agrega achados por prestador e mês, sem expor dados das guias; CPF é pseudonimizado. Quando usar: para analisar rejeições por prestador. Quando não usar: para consultar guias individuais ou corrigir lotes.
| Name | Type | Req | Description |
|---|---|---|---|
| contexto | object | – | – |
| data | string | – | – |
| lotes | array | yes | – |
| operadora | string | – | – |
| regras | object | – | – |
| segredo_pseudonimo | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| guias | integer | yes | – |
| ignored | array | yes | – |
| lotes | integer | yes | – |
| providers | array | yes | – |
| rows | array | yes | – |
| version | – | yes | – |
No examples provided.
tiss_sadt_catalog ~41
Retorna o catálogo SP/SADT. Quando usar: para conhecer campos e domínios. Quando não usar: para preencher uma guia sem dados.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
tiss_sadt_missing ~48
Identifica campos obrigatórios SP/SADT ausentes. Quando usar: antes de renderizar uma guia. Quando não usar: para validar um lote.
| Name | Type | Req | Description |
|---|---|---|---|
| values | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| faltando | array | yes | – |
No examples provided.
tiss_sandbox_autorizacao ~48
Gera uma resposta SP/SADT sintética nos cenários disponíveis.
| Name | Type | Req | Description |
|---|---|---|---|
| cenario | – | – | – |
| solicitacao | object | – | – |
| xml | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | – |
No examples provided.
tiss_sandbox_demonstrativo ~50
Gera o demonstrativo de um protocolo simulado. Quando usar: após enviar um lote. Quando não usar: com protocolo de outra operadora.
| Name | Type | Req | Description |
|---|---|---|---|
| protocolo | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| protocolo | string | yes | – |
| xml | string | yes | – |
No examples provided.
tiss_sandbox_enviar_lote ~69
Envia um lote à operadora simulada. Quando usar: para testar integração local. Quando não usar: para transmitir dados reais.
| Name | Type | Req | Description |
|---|---|---|---|
| cenario | – | – | – |
| registro_ans | string | – | – |
| tentativa | integer | – | – |
| xml | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| aceito | boolean | yes | – |
| cenario | string | yes | – |
| findings | array | yes | – |
| numero_lote | string|null | yes | – |
| numero_protocolo | string|null | yes | – |
| protocolo | string|null | yes | – |
| resumo | object | – | – |
No examples provided.
tiss_validate ~102
Valida XML TISS ou lote em JSON. Quando usar: antes de gerar ou enviar um lote. Quando não usar: para corrigir achados sem aplicar o ciclo validar → tiss_apply_fixes → validar de novo.
| Name | Type | Req | Description |
|---|---|---|---|
| contexto | object | – | – |
| data | string | – | – |
| lote | object | – | Schema estrutural disponível em tiss://schemas/lote. |
| operadora | string | – | – |
| xml | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| decisao | object | – | – |
| findings | array | yes | – |
| valid | boolean | yes | – |
| version | string|null | yes | – |
No examples provided.
tuss_lookup ~65
Busca um código TUSS exato. Quando usar: para consultar código ou vigência. Quando não usar: para buscar por descrição.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| data | string | – | – |
| include_expired | boolean | – | – |
| tabela | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| resultados | array | yes | – |
No examples provided.
tuss_search ~69
Busca códigos TUSS por texto. Quando usar: para localizar procedimentos por descrição. Quando não usar: para validar XML.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | – |
| include_expired | boolean | – | – |
| limite | integer | – | – |
| tabela | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| resultados | array | yes | – |
No examples provided.
How do I install the voa-tiss MCP server?
voa-tiss is a hosted endpoint at https://tiss-api.voa.health/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 · tiss-api.voa.health
claude mcp add --transport http health-voa-tiss 'https://tiss-api.voa.health/mcp'
What is the voa-tiss MCP server?
voa-tiss is an MCP server listed in the public MCP registry as health.voa/tiss. Ferramentas para validar documentos TISS e consultar TUSS, operadoras e dados da ANS. This page covers its hosted endpoint (https://tiss-api.voa.health/mcp).
Is the voa-tiss MCP server safe to use?
voa-tiss scores 70 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 voa-tiss MCP server expose?
voa-tiss exposes 26 tools: tiss_validate, tiss_parse_demonstrativo, tiss_plan_reconciliation, tuss_lookup, tuss_search, and 21 more. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.
Does the voa-tiss MCP server require authentication?
No. We connected to voa-tiss without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the voa-tiss MCP server still maintained?
voa-tiss is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.