io.usefulapi/re-amaze
REMOTE · RE-AMAZE.USEFULAPI.IO · SCANNED OCT 3
Manage Re:amaze conversations, messages, contacts and help articles.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · re-amaze.usefulapi.io
claude mcp add --transport http io-usefulapi-re-amaze 'https://re-amaze.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-re-amaze": {
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-re-amaze": {
"type": "http",
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-re-amaze] url = "https://re-amaze.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-re-amaze": {
"type": "remote",
"url": "https://re-amaze.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-re-amaze --url 'https://re-amaze.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-re-amaze:
url: "https://re-amaze.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-re-amaze": {
"Transport": "http",
"Url": "https://re-amaze.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-re-amaze -t streamable-http -u 'https://re-amaze.usefulapi.io/mcp'
{
"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.
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.
- 2 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +58
- Transport: unverified → pass ▲ security
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 30 Sept 26 0
- Transport: fail → unverified ▼ security
- 29 Sept 26 18
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 3 Oct 2026 · Probed https://re-amaze.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of re-amaze.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://re-amaze.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://re-amaze.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://re-amaze.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://re-amaze.usefulapi.io/mcp |
| Authorisation server | https://re-amaze.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://re-amaze.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://re-amaze.usefulapi.io/mcp | HTTPS enforced | 301 | https://re-amaze.usefulapi.io/mcp |
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 →
reamaze_create_contact Create contact ~71
Create a new contact (customer). Re:amaze REST: POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Arbitrary key/value custom attributes for the contact. |
| string | yes | The contact's email (required). | |
| name | string | yes | The contact's display name (required). |
No output schema declared.
No examples provided.
reamaze_create_conversation Create conversation ~227
Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Staff email to assign the conversation to. |
| category | string | yes | The channel slug to open the conversation in (required). |
| message_body | string | yes | 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 | yes | The conversation subject (required). |
| tag_list | array | – | Tags to apply to the conversation. |
| user_email | string | yes | The customer's email (required). |
| user_name | string | yes | The customer's display name (required). |
No output schema declared.
No examples provided.
reamaze_get_article Get article ~43
Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The article slug. |
No output schema declared.
No examples provided.
reamaze_get_channel Get channel ~41
Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The channel slug. |
No output schema declared.
No examples provided.
reamaze_get_contact Get contact ~49
Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | A contact email or id. |
No output schema declared.
No examples provided.
reamaze_get_conversation Get conversation ~43
Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The conversation slug. |
No output schema declared.
No examples provided.
reamaze_list_articles List articles ~77
List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
reamaze_list_channels List channels ~70
List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (responses report page_size/page_count/total_count). |
No output schema declared.
No examples provided.
reamaze_list_contacts List contacts ~80
List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
reamaze_list_conversations List conversations ~217
List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
reamaze_list_messages List messages ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
reamaze_list_staff List staff ~55
List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (responses report page_size/page_count/total_count). |
No output schema declared.
No examples provided.
reamaze_reply_conversation Reply to conversation ~171
Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | string | – | URL of a file to attach. |
| body | string | yes | The message body — markdown ok (required). |
| recipients | array | – | Additional recipients (emails/phones). |
| slug | string | yes | 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. |
No output schema declared.
No examples provided.
reamaze_report_response_time Report: response time ~101
Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
reamaze_report_volume Report: volume ~97
Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
reamaze_update_contact Update contact ~92
Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Arbitrary key/value custom attributes for the contact. |
| string | – | New email. | |
| id | string | yes | The contact id to update (goes in the path, never the body). |
| name | string | – | New display name. |
No output schema declared.
No examples provided.
reamaze_update_conversation Update conversation ~193
Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.