Claro Gerencial
PYPI · WS-CLARO-GERENCIAL-MCP · SCANNED SEP 21
Servidor MCP para integração com os WebServices SOAP do Claro Gerencial (Redeinova)
Available components
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 hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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 6 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
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.
pypi · ws-claro-gerencial-mcp
claude mcp add hlgurgel-ws-claro-gerencial -- uvx ws-claro-gerencial-mcp
{
"mcpServers": {
"hlgurgel-ws-claro-gerencial": {
"command": "uvx",
"args": [
"ws-claro-gerencial-mcp"
]
}
}
} {
"servers": {
"hlgurgel-ws-claro-gerencial": {
"command": "uvx",
"args": [
"ws-claro-gerencial-mcp"
]
}
}
} codex mcp add hlgurgel-ws-claro-gerencial -- uvx ws-claro-gerencial-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hlgurgel-ws-claro-gerencial": {
"type": "local",
"command": [
"uvx",
"ws-claro-gerencial-mcp"
],
"enabled": true
}
}
} openclaw mcp add hlgurgel-ws-claro-gerencial --command uvx --arg ws-claro-gerencial-mcp
mcp_servers:
hlgurgel-ws-claro-gerencial:
command: "uvx"
args: ["ws-claro-gerencial-mcp"] {
"McpServers": {
"hlgurgel-ws-claro-gerencial": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"ws-claro-gerencial-mcp"
]
}
}
} assistant mcp add hlgurgel-ws-claro-gerencial -t stdio -c uvx -a ws-claro-gerencial-mcp
{
"mcpServers": {
"hlgurgel-ws-claro-gerencial": {
"command": "uvx",
"args": [
"ws-claro-gerencial-mcp"
]
}
}
} 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.
- 21 Sept 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.
- 19 Sept 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 Sept 26 +18
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.27 ▲ functional
- 16 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 10 Sept 26 55
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 Sept 2026 · Analysed pypi/ws-claro-gerencial-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| Stale | 1 |
| 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 →
enviar_registros ~233
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| ambiente | string | – | Ambiente: 'homologacao' ou 'producao' (opcional). |
| entidade | string | yes | Slug da entidade para envio (ex: 'clientes', 'pedidos'). |
| senha | string | – | Senha de acesso (opcional). |
| usuario | string | – | Usuário de acesso (opcional). |
| xml | string | yes | Conteúdo XML completo a ser enviado, conforme schema XSD da entidade. |
No output schema declared.
No examples provided.
gerar_arquivo ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ambiente | string | – | Ambiente: 'homologacao' ou 'producao' (opcional). |
| entidade | string | yes | Slug da entidade (a mesma usada em 'obter_registros'). |
| senha | string | – | Senha de acesso (opcional). |
| ticket | string | yes | Ticket obtido na chamada de 'obter_registros'. |
| usuario | string | – | Usuário de acesso (opcional). |
No output schema declared.
No examples provided.
listar_entidades ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
obter_registros ~338
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ambiente | string | – | Ambiente: 'homologacao' ou 'producao' (opcional — usa env var CLARO_AMBIENTE). |
| completa | boolean | yes | True para carga completa (SIM), False para incremental (NAO). |
| entidade | string | yes | 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). |
No output schema declared.
No examples provided.
obter_schema_xml ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ambiente | string | – | Ambiente: 'homologacao' ou 'producao' (opcional). |
| entidade | string | yes | Slug da entidade para obter o schema XSD. |
| senha | string | – | Senha de acesso (opcional). |
| usuario | string | – | Usuário de acesso (opcional). |
No output schema declared.
No examples provided.
obter_status ~276
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ambiente | string | – | Ambiente: 'homologacao' ou 'producao' (opcional). |
| entidade | string | yes | Slug da entidade enviada. |
| senha | string | – | Senha de acesso (opcional). |
| ticket | string | yes | Ticket retornado por 'enviar_registros'. |
| usuario | string | – | Usuário de acesso (opcional). |
No output schema declared.
No examples provided.
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.