# Claro Gerencial (pypi · ws-claro-gerencial-mcp)

Servidor MCP para integração com os WebServices SOAP do Claro Gerencial (Redeinova)

- Trust score: 75/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `ws-claro-gerencial-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/hlgurgel-ws-claro-gerencial/ws-claro-gerencial-mcp.md), [page](https://verifymcp.io/servers/hlgurgel-ws-claro-gerencial/ws-claro-gerencial-mcp)

## Channel facts

- Registry: `pypi`
- Package: `ws-claro-gerencial-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 38 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1258 tokens (~209/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Claro Gerencial MCP server?

Claro Gerencial runs locally as a PyPI package, launched with uvx ws-claro-gerencial-mcp. 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 hlgurgel-ws-claro-gerencial -- uvx ws-claro-gerencial-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "hlgurgel-ws-claro-gerencial": {
      "command": "uvx",
      "args": [
        "ws-claro-gerencial-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hlgurgel-ws-claro-gerencial": {
      "command": "uvx",
      "args": [
        "ws-claro-gerencial-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hlgurgel-ws-claro-gerencial -- uvx ws-claro-gerencial-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hlgurgel-ws-claro-gerencial": {
      "type": "local",
      "command": [
        "uvx",
        "ws-claro-gerencial-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hlgurgel-ws-claro-gerencial --command uvx --arg ws-claro-gerencial-mcp
```

### Hermes

```yaml
mcp_servers:
  hlgurgel-ws-claro-gerencial:
    command: "uvx"
    args: ["ws-claro-gerencial-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "hlgurgel-ws-claro-gerencial": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "ws-claro-gerencial-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hlgurgel-ws-claro-gerencial -t stdio -c uvx -a ws-claro-gerencial-mcp
```

### Other

```json
{
  "mcpServers": {
    "hlgurgel-ws-claro-gerencial": {
      "command": "uvx",
      "args": [
        "ws-claro-gerencial-mcp"
      ]
    }
  }
}
```

## 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-09-21 (score 75, +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-09-19 (score 74, +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-09-18 (score 73, +18)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.27

### 2026-09-16 (score 55, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-14 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-10 (score 55)

First indexed and scored.

## MCP tools (6)

### `listar_entidades` (~49 tokens)

Lista todas as entidades disponíveis no Claro Gerencial, indicando quais suportam consulta (output) e quais suportam envio (input). Use esta ferramenta para descobrir quais entidades existem antes de usar as demais.

### `obter_registros` (~338 tokens)

Obtém registros de uma entidade do Claro Gerencial (WebService de Output). Use esta ferramenta para consultar/baixar dados do sistema.

Parâmetros:
\- entidade: slug da entidade (ex: 'clientes', 'pedidos', 'visitas'). Use 'listar_entidades' para ver todas as opções.
\- completa: True para carga completa (todos os registros), False para carga incremental (apenas novos/alterados desde a última consulta).
\- usuario/senha: opcionais, usam as variáveis de ambiente CLARO_USUARIO/CLARO_SENHA por padrão.
\- ambiente: opcional, 'homologacao' ou 'producao'. Padrão: variável CLARO_AMBIENTE.

Retorna um ticket que pode ser usado em 'gerar_arquivo' para gerar um arquivo FTP. Se a quantidade de registros retornados atingir o limite, faça novas chamadas com completa=False até que o retorno venha vazio.

Input parameters:

- `ambiente` (string): Ambiente: 'homologacao' ou 'producao' (opcional — usa env var CLARO_AMBIENTE).
- `completa` (boolean, required): True para carga completa (SIM), False para incremental (NAO).
- `entidade` (string, required): Slug da entidade (ex: 'clientes', 'pedidos', 'visitas'). Use 'listar_entidades' para ver todas.
- `senha` (string): Senha de acesso (opcional — usa env var CLARO_SENHA se omitido).
- `usuario` (string): Usuário de acesso (opcional — usa env var CLARO_USUARIO se omitido).

### `gerar_arquivo` (~201 tokens)

Gera um arquivo FTP com os registros obtidos anteriormente via 'obter_registros'. Use o ticket retornado por 'obter_registros' para solicitar que o conteúdo seja disponibilizado via FTP. O arquivo ficará disponível em até 2 horas.

Parâmetros:
\- ticket: ticket retornado por 'obter_registros'.
\- entidade: slug da mesma entidade usada em 'obter_registros'.
\- usuario/senha/ambiente: opcionais, usam variáveis de ambiente por padrão.

Input parameters:

- `ambiente` (string): Ambiente: 'homologacao' ou 'producao' (opcional).
- `entidade` (string, required): Slug da entidade (a mesma usada em 'obter_registros').
- `senha` (string): Senha de acesso (opcional).
- `ticket` (string, required): Ticket obtido na chamada de 'obter_registros'.
- `usuario` (string): Usuário de acesso (opcional).

### `enviar_registros` (~233 tokens)

Envia registros em XML para importação no Claro Gerencial (WebService de Input). Use esta ferramenta para inserir, alterar ou excluir registros no sistema.

O XML deve seguir o schema XSD da entidade (use 'obter_schema_xml' para validar). Cada registro no XML deve conter o campo DbAcao: I (Inclusão), A (Alteração), E (Exclusão).

Parâmetros:
\- entidade: slug da entidade de destino.
\- xml: string contendo o XML completo a ser enviado.
\- usuario/senha/ambiente: opcionais.

Retorna um ticket para acompanhar o status via 'obter_status'.

Input parameters:

- `ambiente` (string): Ambiente: 'homologacao' ou 'producao' (opcional).
- `entidade` (string, required): Slug da entidade para envio (ex: 'clientes', 'pedidos').
- `senha` (string): Senha de acesso (opcional).
- `usuario` (string): Usuário de acesso (opcional).
- `xml` (string, required): Conteúdo XML completo a ser enviado, conforme schema XSD da entidade.

### `obter_status` (~276 tokens)

Consulta o status de um envio de registros pelo ticket (WebService de Input). Use após 'enviar_registros' para acompanhar o processamento.

Códigos de status:
  0 - Na Fila para importação
  1 - Registros sendo transferidos para o SGR
  2 - Verificar preenchimento das informações
  3 - Verificar se registros de exclusão existem
  4 - Verificar registros de inclusão repetidos
  5 - Verificar campos de cadastros relacionados
  6 - Atualizar log para Inclusão
  7 - Atualizar log para Alteração
  8 - Atualizar log para Exclusão
  9 - Envio Finalizado
  99 - Erro ao Enviar

Quando status=9 (Envio Finalizado), o campo Conteudo traz o log detalhado com registros importados e eventuais erros.

Input parameters:

- `ambiente` (string): Ambiente: 'homologacao' ou 'producao' (opcional).
- `entidade` (string, required): Slug da entidade enviada.
- `senha` (string): Senha de acesso (opcional).
- `ticket` (string, required): Ticket retornado por 'enviar_registros'.
- `usuario` (string): Usuário de acesso (opcional).

### `obter_schema_xml` (~161 tokens)

Obtém o schema XSD (XML Schema Definition) de uma entidade para validação antes do envio (WebService de Input).

Use esta ferramenta para verificar a estrutura esperada do XML antes de chamar 'enviar_registros'. O schema define os campos obrigatórios, tipos e formato esperado para cada entidade.

Parâmetros:
\- entidade: slug da entidade.
\- usuario/senha/ambiente: opcionais.

Input parameters:

- `ambiente` (string): Ambiente: 'homologacao' ou 'producao' (opcional).
- `entidade` (string, required): Slug da entidade para obter o schema XSD.
- `senha` (string): Senha de acesso (opcional).
- `usuario` (string): Usuário de acesso (opcional).

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/hlgurgel-ws-claro-gerencial/ws-claro-gerencial-mcp#diagnostics

## Score history

- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 55
- 2026-09-16: 55
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 55
- 2026-09-12: 55
- 2026-09-11: 55
- 2026-09-10: 55

## Common questions

### What is the Claro Gerencial MCP server?

Claro Gerencial is an MCP server listed in the public MCP registry as io.github.hlgurgel/ws-claro-gerencial. Servidor MCP para integração com os WebServices SOAP do Claro Gerencial (Redeinova). This page covers its PyPI package (ws-claro-gerencial-mcp).

### Is the Claro Gerencial MCP server safe to use?

Claro Gerencial scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 Claro Gerencial MCP server expose?

Claro Gerencial exposes 6 tools: listar_entidades, obter_registros, gerar_arquivo, enviar_registros, obter_status, obter_schema_xml. Their descriptions and schemas cost roughly 1,258 tokens of context every time the server is loaded.

### Is the Claro Gerencial MCP server still maintained?

Claro Gerencial is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Claro Gerencial MCP server under?

Claro Gerencial declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/ws-claro-gerencial-mcp/
- Socket report: https://socket.dev/pypi/package/ws-claro-gerencial-mcp
- Repository: https://github.com/hlgurgel/ws-claro-gerencial-mcp
- Changelog RSS feed: https://verifymcp.io/servers/hlgurgel-ws-claro-gerencial/ws-claro-gerencial-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hlgurgel-ws-claro-gerencial/ws-claro-gerencial-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hlgurgel-ws-claro-gerencial/ws-claro-gerencial-mcp