# CVM: Processos Sancionadores Julgados (remote · api.mcp.ai)

CVM: Court Cases Sancionadores Julgados, official-source lookup. Platform-hosted, pay per query with

- Trust score: 28/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-21

## Components

- remote · `api.mcp.ai`: 28/100 (this document), [markdown](https://verifymcp.io/servers/mcp-dir-cvm-sancionadores-mcp/p-cvm-sancionadores.md), [page](https://verifymcp.io/servers/mcp-dir-cvm-sancionadores-mcp/p-cvm-sancionadores)

## Channel facts

- Endpoint: `https://api.mcp.ai/p_cvm_sancionadores`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-08-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http mcp-dir-cvm-sancionadores-mcp https://api.mcp.ai/p_cvm_sancionadores
```

### Codex

```toml
[mcp_servers.mcp-dir-cvm-sancionadores-mcp]
url = "https://api.mcp.ai/p_cvm_sancionadores"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-cvm-sancionadores-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_cvm_sancionadores",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mcp-dir-cvm-sancionadores-mcp --url https://api.mcp.ai/p_cvm_sancionadores --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mcp-dir-cvm-sancionadores-mcp:
    url: "https://api.mcp.ai/p_cvm_sancionadores"
```

### Other

```json
{
  "mcpServers": {
    "mcp-dir-cvm-sancionadores-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_cvm_sancionadores"
    }
  }
}
```

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-08-21 (score 28, −32)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-08-20 (score 60)

First indexed and scored.

## MCP tools (7)

### `cvm_sancionadores_consultar` (~125 tokens)

CVM: Processos Sancionadores Julgados, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

Input parameters:

- `data_fim` (string)
- `data_inicio` (string)
- `termo` (string)
- `tipo_filtro` (string)

### `show_version` (~17 tokens)

Show the current MCP platform and adapter versions.

### `report_bug` (~50 tokens)

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Input parameters:

- `context` (string)
- `conversation` (string)
- `message` (string, required)

### `connect` (~42 tokens)

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

### `toolkit_info` (~37 tokens)

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

### `marketplace` (~532 tokens)

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

Input parameters:

- `action` (string)
- `arguments` (string)
- `cancel_comment` (string)
- `cancel_reason` (string)
- `conversation` (string)
- `immediate` (boolean)
- `limit` (number)
- `mcp_id` (string)
- `message` (string)
- `prompt_body` (string)
- `prompt_category` (string)
- `prompt_description` (string)
- `prompt_slug` (string)
- `prompt_targets` (array)
- `prompt_title` (string)
- `prompt_tool` (string)
- `prompt_vars` (string)
- `query` (string)
- `report_context` (string)
- `request_details` (string)
- `request_name` (string)
- `tier_slug` (string)
- `tool_id` (string)

### `authenticate` (~99 tokens)

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Input parameters:

- `token` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mcp-dir-cvm-sancionadores-mcp/p-cvm-sancionadores#diagnostics

## Score history

- 2026-08-21: 28
- 2026-08-20: 60

## Links

- Remote endpoint: https://api.mcp.ai/p_cvm_sancionadores
- Repository: https://github.com/mcp-dir/cvm_sancionadores-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mcp-dir-cvm-sancionadores-mcp/p-cvm-sancionadores.xml
- Changelog JSON feed: https://verifymcp.io/servers/mcp-dir-cvm-sancionadores-mcp/p-cvm-sancionadores.json
- HTML version of this page: https://verifymcp.io/servers/mcp-dir-cvm-sancionadores-mcp/p-cvm-sancionadores