# voa-tiss (remote · tiss-api.voa.health)

Ferramentas para validar documentos TISS e consultar TUSS, operadoras e dados da ANS.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `tiss-api.voa.health`: 71/100 (this document), [markdown](https://verifymcp.io/servers/health-voa-tiss/tiss-api.md), [page](https://verifymcp.io/servers/health-voa-tiss/tiss-api)

## Channel facts

- Endpoint: `https://tiss-api.voa.health/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 2098 tokens (~61/item across 34 items; 26 tools + 8 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 3% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http health-voa-tiss 'https://tiss-api.voa.health/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "health-voa-tiss": {
      "url": "https://tiss-api.voa.health/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "health-voa-tiss": {
      "type": "http",
      "url": "https://tiss-api.voa.health/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.health-voa-tiss]
url = "https://tiss-api.voa.health/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "health-voa-tiss": {
      "type": "remote",
      "url": "https://tiss-api.voa.health/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add health-voa-tiss --url 'https://tiss-api.voa.health/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  health-voa-tiss:
    url: "https://tiss-api.voa.health/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "health-voa-tiss": {
      "Transport": "http",
      "Url": "https://tiss-api.voa.health/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add health-voa-tiss -t streamable-http -u 'https://tiss-api.voa.health/mcp'
```

### Other

```json
{
  "mcpServers": {
    "health-voa-tiss": {
      "type": "http",
      "url": "https://tiss-api.voa.health/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +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.

### 2026-11-02 (score 70, +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.

### 2026-10-31 (score 69, +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.

### 2026-10-29 (score 68, +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.

### 2026-10-27 (score 67, +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.

### 2026-10-25 (score 66, +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.

### 2026-10-24 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: voa-tiss → tiss
- [functional] New tool “tiss_referencia”

### 2026-10-23 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1614 → 1949
- [functional improvement] 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”
- [cosmetic] “tiss_audit” added an optional parameter “operadora”
- [cosmetic] “tiss_sandbox_enviar_lote” added an optional parameter “registro_ans”

## MCP tools (26)

### `tiss_validate` (~102 tokens)

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.

Input parameters:

- `contexto` (object)
- `data` (string)
- `lote` (object): Schema estrutural disponível em tiss://schemas/lote.
- `operadora` (string)
- `xml` (string)

Output parameters:

- `decisao` (object)
- `findings` (array)
- `valid` (boolean)
- `version` (string|null)

### `tiss_parse_demonstrativo` (~46 tokens)

Lê decisões de um demonstrativo. Quando usar: para identificar pagamentos e glosas. Quando não usar: para validar lotes.

Input parameters:

- `xml` (string, required)

Output parameters:

- `decisoes` (array)

### `tiss_plan_reconciliation` (~89 tokens)

Propõe vínculos entre decisões e guias. Quando usar: após ler um demonstrativo. Quando não usar: para alterar guias.

Input parameters:

- `decisoes` (array, required)
- `guias` (array, required)
- `id_key` (string)
- `operadora_key` (string)
- `prestador_key` (string)
- `status_key` (string)

Output parameters:

- `ambiguas` (array)
- `propostas` (array)
- `sem_par` (array)

### `tuss_lookup` (~65 tokens)

Busca um código TUSS exato. Quando usar: para consultar código ou vigência. Quando não usar: para buscar por descrição.

Input parameters:

- `code` (string, required)
- `data` (string)
- `include_expired` (boolean)
- `tabela` (string)

Output parameters:

- `resultados` (array)

### `tuss_search` (~69 tokens)

Busca códigos TUSS por texto. Quando usar: para localizar procedimentos por descrição. Quando não usar: para validar XML.

Input parameters:

- `data` (string)
- `include_expired` (boolean)
- `limite` (integer)
- `tabela` (string)
- `text` (string, required)

Output parameters:

- `resultados` (array)

### `tiss_sadt_missing` (~48 tokens)

Identifica campos obrigatórios SP/SADT ausentes. Quando usar: antes de renderizar uma guia. Quando não usar: para validar um lote.

Input parameters:

- `values` (object, required)

Output parameters:

- `faltando` (array)

### `tiss_sadt_catalog` (~41 tokens)

Retorna o catálogo SP/SADT. Quando usar: para conhecer campos e domínios. Quando não usar: para preencher uma guia sem dados.

### `tiss_rede` (~73 tokens)

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.

Input parameters:

- `cnes` (string)
- `cnpj` (string)
- `limite` (integer)

Output parameters:

- `atualizado_em` (string)
- `fonte` (string)
- `operadoras` (array)
- `total` (integer)

### `operadora_rede` (~68 tokens)

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.

Input parameters:

- `limite` (integer)
- `registro` (string, required)
- `uf` (string)

Output parameters:

- `atualizado_em` (string)
- `estabelecimentos` (array)
- `fonte` (string)
- `por_uf` (object)
- `registro_ans` (string)
- `total` (integer)

### `operadora_perfil` (~64 tokens)

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.

Input parameters:

- `registro_ans` (string, required)

Output parameters:

- `indicadores` (object)
- `razao_social` (string)
- `registro_ans` (string)

### `tiss_sandbox_enviar_lote` (~69 tokens)

Envia um lote à operadora simulada. Quando usar: para testar integração local. Quando não usar: para transmitir dados reais.

Input parameters:

- `cenario`
- `registro_ans` (string)
- `tentativa` (integer)
- `xml` (string, required)

Output parameters:

- `aceito` (boolean)
- `cenario` (string)
- `findings` (array)
- `numero_lote` (string|null)
- `numero_protocolo` (string|null)
- `protocolo` (string|null)
- `resumo` (object)

### `tiss_sandbox_demonstrativo` (~50 tokens)

Gera o demonstrativo de um protocolo simulado. Quando usar: após enviar um lote. Quando não usar: com protocolo de outra operadora.

Input parameters:

- `protocolo` (string, required)

Output parameters:

- `protocolo` (string)
- `xml` (string)

### `tiss_build` (~95 tokens)

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.

Input parameters:

- `lote` (object, required): Schema estrutural disponível em tiss://schemas/lote.

Output parameters:

- `hash` (string)
- `xml` (string)

### `tiss_hash` (~55 tokens)

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.

Input parameters:

- `xml` (string, required)

Output parameters:

- `hash` (string)

### `tiss_audit` (~80 tokens)

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.

Input parameters:

- `contexto` (object)
- `data` (string)
- `lote` (object, required)
- `operadora` (string|object)

Output parameters:

- `decisao` (object)
- `findings` (array)
- `valid` (boolean)
- `version` (string|null)

### `tiss_rejection_map` (~110 tokens)

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.

Input parameters:

- `contexto` (object)
- `data` (string)
- `lotes` (array, required)
- `operadora` (string)
- `regras` (object)
- `segredo_pseudonimo` (string)

Output parameters:

- `guias` (integer)
- `ignored` (array)
- `lotes` (integer)
- `providers` (array)
- `rows` (array)
- `version`

### `tiss_apply_fixes` (~72 tokens)

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.

Input parameters:

- `lote` (object, required)
- `report` (object, required)

Output parameters:

- `lote` (object)

### `glosa_explain` (~53 tokens)

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.

Input parameters:

- `codigo` (string, required)

Output parameters:

- `codigo` (string)
- `descricao` (string)
- `fonte` (object)
- `grupo` (string)
- `orientacao` (object)

### `tiss_dominio` (~90 tokens)

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.

Input parameters:

- `codigo` (string)
- `data` (string)
- `include_expired` (boolean)
- `limite` (integer)
- `tabela` (string)
- `texto` (string)

Output parameters:

- `resultados` (array)
- `tabelas` (array)

### `operadora_lookup` (~68 tokens)

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.

Input parameters:

- `limite` (integer)
- `texto` (string, required)

Output parameters:

- `resultados` (array)

### `tiss_referencia` (~108 tokens)

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.

Input parameters:

- `codigo` (string, required)
- `modalidade` (string)
- `porte` (string)
- `semestre` (string)
- `tabela` (string)
- `uf` (string, required)

Output parameters:

- `atualizado_em` (string)
- `aviso` (string|null)
- `fonte` (string)
- `minimo_n` (integer)
- `referencia` (object|null)
- `semestre` (string)

### `tiss_autorizacao_build` (~41 tokens)

Gera XML TISS 4.03.00 para solicitação ou resposta de autorização SP/SADT.

Input parameters:

- `mensagem` (object, required)

Output parameters:

- `hash` (string)
- `xml` (string)

### `tiss_autorizacao_parse` (~32 tokens)

Interpreta solicitações e respostas de autorização SP/SADT.

Input parameters:

- `xml` (string, required)

Output parameters:

- `mensagem` (object)

### `tiss_autorizacao_check` (~49 tokens)

Valida uma solicitação SP/SADT e retorna uma decisão explicável.

Input parameters:

- `contexto` (object)
- `solicitacao` (object)
- `xml` (string)

### `tiss_sandbox_autorizacao` (~48 tokens)

Gera uma resposta SP/SADT sintética nos cenários disponíveis.

Input parameters:

- `cenario`
- `solicitacao` (object)
- `xml` (string)

Output parameters:

- `xml` (string)

### `buscar_docs` (~56 tokens)

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.

Input parameters:

- `limite` (integer)
- `texto` (string, required)

Output parameters:

- `resultados` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/health-voa-tiss/tiss-api#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 66
- 2026-10-25: 66
- 2026-10-24: 65
- 2026-10-23: 65
- 2026-10-22: 65

## Common questions

### 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 71 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tiss-api.voa.health/mcp
- Repository: https://github.com/Voa-Health/tiss
- Website: https://tiss-api.voa.health/
- Changelog RSS feed: https://verifymcp.io/servers/health-voa-tiss/tiss-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/health-voa-tiss/tiss-api.json
- HTML version of this page: https://verifymcp.io/servers/health-voa-tiss/tiss-api