Re:amaze MCP by usefulapi
REMOTE · RE-AMAZE.USEFULAPI.IO
Manage Re:amaze conversations, messages, contacts and help articles.
Available components
Last scanned (20 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +4
- Authorization: partial → pass ▲ security
- Stability: 0.97 → pass security
- MCP protocol: fail → pass ▲ functional
- New prompt “change_a_conversation_s_status_tags_or_assignee” functional
- New prompt “check_conversation_volume_and_response_time” functional
- New prompt “find_a_help_center_article” functional
- New prompt “look_up_add_or_update_a_customer” functional
- New prompt “reply_to_a_conversation_or_start_a_new_one” functional
- New prompt “review_conversations_of_a_channel_and_read_their_messages” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 +1
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.4 → 1.22.0 functional
- Server version: 1.21.3 → 1.21.4 functional
- Server version: 1.21.0 → 1.21.3 functional
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 21 Nov 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 | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| 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. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/re-amaze/ |
| http (plaintext) | http://re-amaze.usefulapi.io/mcp | Inconclusive | 302 | http://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.
How do I install the Re:amaze MCP by usefulapi server?
Re:amaze MCP by usefulapi 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'
What is the Re:amaze MCP by usefulapi server?
Re:amaze MCP by usefulapi is 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 Re:amaze MCP by usefulapi server safe to use?
Re:amaze MCP by usefulapi scores 18 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 Re:amaze MCP by usefulapi server expose?
Re:amaze MCP by usefulapi 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 Re:amaze MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Re:amaze MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Re:amaze MCP by usefulapi server still maintained?
Re:amaze MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Re:amaze MCP by usefulapi server?
VerifyMCP ran 4 checks on Re:amaze MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Re:amaze MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.