# io.usefulapi/re-amaze (remote · re-amaze.usefulapi.io)

Manage Re:amaze conversations, messages, contacts and help articles.

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

## Components

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

## Channel facts

- Endpoint: `https://re-amaze.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-03.

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1887 tokens (~111/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 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 io.usefulapi/re-amaze MCP server?

io.usefulapi/re-amaze is a hosted endpoint at https://re-amaze.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-re-amaze 'https://re-amaze.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-re-amaze": {
      "type": "http",
      "url": "https://re-amaze.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-02 (score 77, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 76, +58)

- [security improvement] Transport: unverified → pass
- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-30 (score 18, 0)

- [security regression] Transport: fail → unverified

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (17)

### `reamaze_list_conversations` (~217 tokens)

List conversations

List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.

Input parameters:

- `category` (string): Filter by channel slug.
- `end_date` (string): Filter to items on/before this ISO8601 date, e.g. 2026-01-31.
- `filter` (string): Restrict to a set of conversations.
- `for` (string): Filter to conversations for this customer email.
- `for_id` (string): Filter to conversations for this SSO user id.
- `origin` (string): Filter by conversation origin/channel type.
- `page` (integer): 1-based page number to fetch (responses report page_size/page_count/total_count).
- `sort` (string): Sort order.
- `start_date` (string): Filter to items on/after this ISO8601 date, e.g. 2026-01-31.
- `tag` (string): Filter by tag(s) — comma-separated.

### `reamaze_get_conversation` (~43 tokens)

Get conversation

Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.

Input parameters:

- `slug` (string, required): The conversation slug.

### `reamaze_list_messages` (~260 tokens)

List messages

List messages. If `conversation` (a slug) is given, list that conversation's messages (GET /conversations/{slug}/messages); otherwise list messages across the brand (GET /messages). All other filters optional. Re:amaze REST.

Input parameters:

- `category` (string): Filter by channel slug.
- `conversation` (string): Conversation slug — scopes to GET /conversations/{slug}/messages (goes in the PATH, not the query).
- `end_date` (string): Filter to items on/before this ISO8601 date, e.g. 2026-01-31.
- `filter` (string): Restrict to staff or customer messages.
- `include` (string): Include extra fields, e.g. 'original_body'.
- `origin` (integer): Filter by numeric message origin.
- `page` (integer): 1-based page number to fetch (responses report page_size/page_count/total_count).
- `sent_by` (string): Filter to messages sent by this email.
- `start_date` (string): Filter to items on/after this ISO8601 date, e.g. 2026-01-31.
- `tag` (string): Filter by tag(s) — comma-separated.

### `reamaze_list_contacts` (~80 tokens)

List contacts

List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.

Input parameters:

- `filter` (string): Free-text filter, e.g. an email or name substring.
- `page` (integer): 1-based page number to fetch (responses report page_size/page_count/total_count).

### `reamaze_get_contact` (~49 tokens)

Get contact

Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.

Input parameters:

- `identifier` (string, required): A contact email or id.

### `reamaze_list_articles` (~77 tokens)

List articles

List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.

Input parameters:

- `filter` (string): Free-text filter, e.g. a title/body substring.
- `page` (integer): 1-based page number to fetch (responses report page_size/page_count/total_count).

### `reamaze_get_article` (~43 tokens)

Get article

Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.

Input parameters:

- `slug` (string, required): The article slug.

### `reamaze_list_staff` (~55 tokens)

List staff

List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.

Input parameters:

- `page` (integer): 1-based page number to fetch (responses report page_size/page_count/total_count).

### `reamaze_list_channels` (~70 tokens)

List channels

List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.

Input parameters:

- `page` (integer): 1-based page number to fetch (responses report page_size/page_count/total_count).

### `reamaze_get_channel` (~41 tokens)

Get channel

Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.

Input parameters:

- `slug` (string, required): The channel slug.

### `reamaze_report_volume` (~97 tokens)

Report: volume

Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.

Input parameters:

- `end_date` (string): Filter to items on/before this ISO8601 date, e.g. 2026-01-31.
- `start_date` (string): Filter to items on/after this ISO8601 date, e.g. 2026-01-31.

### `reamaze_report_response_time` (~101 tokens)

Report: response time

Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.

Input parameters:

- `end_date` (string): Filter to items on/before this ISO8601 date, e.g. 2026-01-31.
- `start_date` (string): Filter to items on/after this ISO8601 date, e.g. 2026-01-31.

### `reamaze_create_conversation` (~227 tokens)

Create conversation

Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.

Input parameters:

- `assignee` (string): Staff email to assign the conversation to.
- `category` (string, required): The channel slug to open the conversation in (required).
- `message_body` (string, required): The first message body — markdown ok (required).
- `recipients` (array): Additional recipients (emails/phones) for the message.
- `status` (integer): Initial status. Status integer: 0=Open, 1=Responded, 2=Done, 3=Spam, 4=Archived, 5=On Hold, 6=Auto-Done, 7=AI Agent Assigned, 8=AI Agent Done, 9=Spam (AI).
- `subject` (string, required): The conversation subject (required).
- `tag_list` (array): Tags to apply to the conversation.
- `user_email` (string, required): The customer's email (required).
- `user_name` (string, required): The customer's display name (required).

### `reamaze_reply_conversation` (~171 tokens)

Reply to conversation

Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.

Input parameters:

- `attachment` (string): URL of a file to attach.
- `body` (string, required): The message body — markdown ok (required).
- `recipients` (array): Additional recipients (emails/phones).
- `slug` (string, required): The conversation slug to reply to.
- `suppress_notifications` (boolean): If true, do not send notification emails for this message.
- `user_email` (string): Email of the author (customer or staff).
- `user_name` (string): Display name of the author.
- `visibility` (integer): 0 = Regular reply (customer-facing), 1 = Internal Note. Default 0.

### `reamaze_update_conversation` (~193 tokens)

Update conversation

Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.

Input parameters:

- `assignee` (string): Staff email to assign the conversation to.
- `hold_until` (string): ISO8601 DateTime to hold the conversation until (used when status=5 On Hold).
- `slug` (string, required): The conversation slug to update.
- `status` (integer): New status. Status integer: 0=Open, 1=Responded, 2=Done, 3=Spam, 4=Archived, 5=On Hold, 6=Auto-Done, 7=AI Agent Assigned, 8=AI Agent Done, 9=Spam (AI).
- `subject` (string): New subject.
- `tag_list` (array): Replace the conversation's tags.

### `reamaze_create_contact` (~71 tokens)

Create contact

Create a new contact (customer). Re:amaze REST: POST /contacts.

Input parameters:

- `data` (object): Arbitrary key/value custom attributes for the contact.
- `email` (string, required): The contact's email (required).
- `name` (string, required): The contact's display name (required).

### `reamaze_update_contact` (~92 tokens)

Update contact

Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.

Input parameters:

- `data` (object): Arbitrary key/value custom attributes for the contact.
- `email` (string): New email.
- `id` (string, required): The contact id to update (goes in the path, never the body).
- `name` (string): New display name.

## Diagnostics

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

## Score history

- 2026-10-03: 77
- 2026-10-02: 77
- 2026-10-01: 76
- 2026-09-30: 18
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/re-amaze MCP server?

io.usefulapi/re-amaze is an MCP server listed in the public MCP registry as io.usefulapi/re-amaze. Manage Re:amaze conversations, messages, contacts and help articles. This page covers its hosted endpoint (https://re-amaze.usefulapi.io/mcp).

### Is the io.usefulapi/re-amaze MCP server safe to use?

io.usefulapi/re-amaze 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 io.usefulapi/re-amaze MCP server expose?

io.usefulapi/re-amaze exposes 17 tools: reamaze_list_conversations, reamaze_get_conversation, reamaze_list_messages, reamaze_list_contacts, reamaze_get_contact, and 12 more. Their descriptions and schemas cost roughly 1,887 tokens of context every time the server is loaded.

### Does the io.usefulapi/re-amaze MCP server require authentication?

Yes. io.usefulapi/re-amaze 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 io.usefulapi/re-amaze MCP server still maintained?

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