# Chatra MCP by usefulapi (remote · chatra.usefulapi.io)

Read and update Chatra visitors; send, edit and delete chat and pushed messages.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `chatra.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-chatra/chatra.md), [page](https://verifymcp.io/servers/io-usefulapi-chatra/chatra)

## Channel facts

- Endpoint: `https://chatra.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.3`

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

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1589 tokens (~158/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**: 3/100
  - Stability observed for 1 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.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Chatra MCP by usefulapi server?

Chatra MCP by usefulapi is a hosted endpoint at https://chatra.usefulapi.io/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 io-usefulapi-chatra 'https://chatra.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-chatra": {
      "url": "https://chatra.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-chatra": {
      "type": "http",
      "url": "https://chatra.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-chatra]
url = "https://chatra.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-chatra": {
      "type": "remote",
      "url": "https://chatra.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-chatra --url 'https://chatra.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-chatra:
    url: "https://chatra.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-chatra": {
      "Transport": "http",
      "Url": "https://chatra.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-chatra -t streamable-http -u 'https://chatra.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-chatra": {
      "type": "http",
      "url": "https://chatra.usefulapi.io/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-10-25 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (10)

### `chatra_get_visitor` (~151 tokens)

Get visitor

A chat visitor by id: name and contact details (basicInfo, integrationData and the merged `info`), custom form answers, location, browser, the link to the chat in the Chatra dashboard, the agent group, and the pages viewed in the latest visit. The id is the `clientId` your website passed to the widget or the visitor id from a Chatra webhook; Chatra has no endpoint to list or search visitors. GET /clients/{id}.

Input parameters:

- `client_id` (string, required): Chatra visitor id: the `clientId` your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id).

### `chatra_update_visitor` (~158 tokens)

Update visitor

WRITE: edit a visitor's basic info (name, email, phone, notes) exactly as if an agent edited it in the Chatra dashboard. Only the fields you pass change; `null` removes a value. Returns the updated visitor. PUT /clients/{id}.

Input parameters:

- `client_id` (string, required): Chatra visitor id: the `clientId` your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id).
- `email`: Visitor email; null removes it.
- `name`: Visitor name; null removes it.
- `notes`: Agent notes about the visitor; null removes them.
- `phone`: Visitor phone number; null removes it.

### `chatra_get_message` (~99 tokens)

Get message

One chat message by id (a visitor's or an agent's): type (agent or client), text, visitor id, agent id, timestamp (ms) and receivedFrom. Chatra has no endpoint to list a conversation, so the id must come from a send call or a webhook. GET /messages/{id}.

Input parameters:

- `message_id` (string, required): Chatra message id (from the reply of a send call or from a webhook).

### `chatra_send_message` (~277 tokens)

Send message as an agent

WRITE: send a chat message to a visitor as a Chatra agent. The visitor sees it immediately in their chat window as if the agent typed it, so only call it with text the user asked you to send. It cannot be unsent except by deleting it. Say which agent writes: agent_id, or agent_email + agent_name + received_from (a dummy agent is created in Chatra when the email is unknown). For automated notices (order status, announcements) use chatra_push_message instead. Returns the new message with its id. POST /messages/.

Input parameters:

- `agent_email` (string): Agent email (instead of agent_id; needs agent_name and received_from).
- `agent_id` (string): Chatra agent id (shown on the agent's page in Chatra).
- `agent_name` (string): Agent display name (with agent_email).
- `client_id` (string, required): Chatra visitor id: the `clientId` your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id).
- `received_from` (string): Short name of the sending system, e.g. 'usefulapi-mcp'; marks the message in webhooks.
- `text` (string, required): Message text (plain text, 1-5000 characters).

### `chatra_edit_message` (~96 tokens)

Edit agent message

WRITE: replace the text of an agent message that was sent earlier. Only agents' messages can be edited, not visitors'. The visitor sees the edited text. Returns the updated message. PUT /messages/{id}.

Input parameters:

- `message_id` (string, required): Chatra message id (from the reply of a send call or from a webhook).
- `text` (string, required): Message text (plain text, 1-5000 characters).

### `chatra_delete_message` (~71 tokens)

Delete agent message

WRITE, IRREVERSIBLE: delete an agent message from the conversation. Only agents' messages can be deleted, not visitors'. Returns the deleted message. DELETE /messages/{id}.

Input parameters:

- `message_id` (string, required): Chatra message id (from the reply of a send call or from a webhook).

### `chatra_get_pushed_message` (~72 tokens)

Get pushed message

One pushed (automated) message sent earlier by id: text, visitor id, agent id, timestamp (ms), isPushed. GET /pushedMessages/{id}.

Input parameters:

- `message_id` (string, required): Chatra message id (from the reply of a send call or from a webhook).

### `chatra_push_message` (~226 tokens)

Push message to a visitor

WRITE: send an automated message (order status, product update, announcement) to a visitor whose account is bound to Chatra through a clientId. It is delivered into the visitor's chat on behalf of a random agent, a given agent (agent_id) or a random agent of a group (group_id). It reaches a real customer and cannot be unsent except by deleting it, so only call it with text the user asked you to send. Returns the new message with its id. POST /pushedMessages/.

Input parameters:

- `agent_id` (string): Chatra agent id (shown on the agent's page in Chatra).
- `client_id` (string, required): Chatra visitor id: the `clientId` your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id).
- `group_id` (string): Chatra agent group id (on the group's page); a random agent of the group writes.
- `text` (string, required): Message text (plain text, 1-5000 characters).

### `chatra_edit_pushed_message` (~87 tokens)

Edit pushed message

WRITE: replace the text of a pushed message sent earlier; the visitor sees the edited text. Returns the updated message. PUT /pushedMessages/{id}.

Input parameters:

- `message_id` (string, required): Chatra message id (from the reply of a send call or from a webhook).
- `text` (string, required): Message text (plain text, 1-5000 characters).

### `chatra_delete_pushed_message` (~63 tokens)

Delete pushed message

WRITE, IRREVERSIBLE: delete a pushed message sent earlier. Returns the deleted message. DELETE /pushedMessages/{id}.

Input parameters:

- `message_id` (string, required): Chatra message id (from the reply of a send call or from a webhook).

## Diagnostics

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

## Score history

- 2026-10-25: 63
- 2026-10-24: 62

## Common questions

### What is the Chatra MCP by usefulapi server?

Chatra MCP by usefulapi is listed in the public MCP registry as io.usefulapi/chatra. Read and update Chatra visitors; send, edit and delete chat and pushed messages. This page covers its hosted endpoint (https://chatra.usefulapi.io/mcp).

### Is the Chatra MCP by usefulapi server safe to use?

Chatra MCP by usefulapi scores 63 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 Chatra MCP by usefulapi server expose?

Chatra MCP by usefulapi exposes 10 tools: chatra_get_visitor, chatra_update_visitor, chatra_get_message, chatra_send_message, chatra_edit_message, and 5 more. Their descriptions and schemas cost roughly 1,300 tokens of context every time the server is loaded.

### Does the Chatra MCP by usefulapi server require authentication?

Yes. Chatra MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Chatra MCP by usefulapi server still maintained?

Chatra MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 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://chatra.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/chatra/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-chatra/chatra.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-chatra/chatra.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-chatra/chatra