# Reclame Aqui (remote · api.mcp.ai)

Manage your company's complaints on Reclame Aqui through the Company Area account. You provide the c

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

## Components

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

## Channel facts

- Endpoint: `https://api.mcp.ai/p_reclameaqui`
- 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-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1179 tokens (~117/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Reclame Aqui MCP server?

Reclame Aqui is a hosted endpoint at https://api.mcp.ai/p_reclameaqui, 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 mcp-dir-reclameaqui-mcp 'https://api.mcp.ai/p_reclameaqui'
```

### Cursor

```json
{
  "mcpServers": {
    "mcp-dir-reclameaqui-mcp": {
      "url": "https://api.mcp.ai/p_reclameaqui"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mcp-dir-reclameaqui-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_reclameaqui"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mcp-dir-reclameaqui-mcp]
url = "https://api.mcp.ai/p_reclameaqui"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mcp-dir-reclameaqui-mcp --url 'https://api.mcp.ai/p_reclameaqui' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mcp-dir-reclameaqui-mcp:
    url: "https://api.mcp.ai/p_reclameaqui"
```

### Netclaw

```json
{
  "McpServers": {
    "mcp-dir-reclameaqui-mcp": {
      "Transport": "http",
      "Url": "https://api.mcp.ai/p_reclameaqui"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mcp-dir-reclameaqui-mcp -t streamable-http -u 'https://api.mcp.ai/p_reclameaqui'
```

### Other

```json
{
  "mcpServers": {
    "mcp-dir-reclameaqui-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_reclameaqui"
    }
  }
}
```

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-09-25 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-21 (score 77, 0)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 74, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.9.346 → 0.9.351

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.9.345 → 0.9.346

## MCP tools (10)

### `reclameaqui_listar_reclamacoes` (~88 tokens)

Lista as reclamações da sua empresa no Reclame Aqui (mais recentes primeiro). Traz id, título, status, consumidor, cidade/UF, se já foi respondida e avaliação.

Input parameters:

- `index` (number)
- `limit` (number)
- `order` (string)
- `order_type` (string)
- `status` (string)

### `reclameaqui_reclamacao` (~56 tokens)

Detalhe de uma ou mais reclamações por id (conversa completa em treatments, avaliação, score, status). Aceita lista de ids.

Input parameters:

- `id` (string)
- `ids` (array)

### `reclameaqui_responder` (~94 tokens)

Responde uma reclamação da sua empresa no Reclame Aqui. Por padrão é resposta PÚBLICA; use privada=true para mensagem interna ao consumidor. AÇÃO PÚBLICA — confirme o texto antes de enviar.

Bulk support: accepts ids for batched execution.

Input parameters:

- `id` (string, required)
- `ids` (array)
- `mensagem` (string, required)
- `privada` (boolean)

### `reclameaqui_reputacao` (~34 tokens)

Indicadores de reputação da sua empresa no Reclame Aqui (nota/rating e principais problemas reclamados).

### `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-reclameaqui-mcp/p-reclameaqui#diagnostics

## Score history

- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 69
- 2026-09-03: 69
- 2026-09-02: 68
- 2026-09-01: 48
- 2026-08-31: 48
- 2026-08-30: 47
- 2026-08-29: 47
- 2026-08-28: 46
- 2026-08-27: 66

## Common questions

### What is the Reclame Aqui MCP server?

Reclame Aqui is an MCP server listed in the public MCP registry as io.github.mcp-dir/reclameaqui-mcp. Manage your company's complaints on Reclame Aqui through the Company Area account. You provide the c. This page covers its hosted endpoint (https://api.mcp.ai/p_reclameaqui).

### Is the Reclame Aqui MCP server safe to use?

Reclame Aqui scores 77 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 Reclame Aqui MCP server expose?

Reclame Aqui exposes 10 tools: reclameaqui_listar_reclamacoes, reclameaqui_reclamacao, reclameaqui_responder, reclameaqui_reputacao, show_version, and 5 more. Their descriptions and schemas cost roughly 1,049 tokens of context every time the server is loaded.

### Does the Reclame Aqui MCP server require authentication?

No. We connected to Reclame Aqui without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Reclame Aqui MCP server still maintained?

Reclame Aqui is still listed as active in the MCP registry. We last reached this channel on 25 September 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://api.mcp.ai/p_reclameaqui
- Repository: https://github.com/mcp-dir/reclameaqui-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mcp-dir-reclameaqui-mcp/p-reclameaqui.xml
- Changelog JSON feed: https://verifymcp.io/servers/mcp-dir-reclameaqui-mcp/p-reclameaqui.json
- HTML version of this page: https://verifymcp.io/servers/mcp-dir-reclameaqui-mcp/p-reclameaqui