Skip to content

Re:amaze MCP by usefulapi

io.usefulapi/re-amazeusefulapi.iostreamable-httpv1.40.5Scanned

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

17 tools: 5 can delete or cancel things and 12 only read.

Tools: 5 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 8
  • Reads text others write · 7
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Re:amaze MCP by usefulapi can do

The Re:amaze MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (5 tools: reamaze_create_conversation, reamaze_reply_conversation, reamaze_update_conversation, reamaze_create_contact and 1 more). 12 tools only read.

8 tools read private data (reamaze_list_conversations, reamaze_get_conversation, reamaze_list_messages and 5 more); 7 tools bring in text other people can write (reamaze_list_conversations, reamaze_get_conversation, reamaze_list_messages and 4 more); 1 tool can send data out of your system (reamaze_reply_conversation). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Deletes or cancels 5Claude Code: deny
  • reamaze_create_contactCreate a new contact (customer).No findings

    Why it is in this group

    • The name "reamaze_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a new contact (customer). Re:amaze REST: POST /contacts.

    Annotations the server declares

    • title: Create contact
    • destructiveHint: true
  • reamaze_create_conversationCreate a new conversation (support ticket) with its first message.No findings

    Why it is in this group

    • The name "reamaze_create_conversation" says "create": a word for a change.
    • The input addresses people (input.recipients): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.

    Annotations the server declares

    • title: Create conversation
    • destructiveHint: true
  • reamaze_reply_conversationAdd a message to an existing conversation — a customer-facing reply or an internal note.Can send data outNo findings

    Why it is in this group

    • The name "reamaze_reply_conversation" says "reply": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.recipients): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "reamaze_reply_conversation" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.

    Annotations the server declares

    • title: Reply to conversation
    • destructiveHint: true
  • reamaze_update_contactUpdate fields on an existing contact.No findings

    Why it is in this group

    • The name "reamaze_update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.

    Annotations the server declares

    • title: Update contact
    • destructiveHint: true
  • reamaze_update_conversationUpdate fields on an existing conversation (subject, status, tags, assignee).No findings

    Why it is in this group

    • The name "reamaze_update_conversation" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.

    Annotations the server declares

    • title: Update conversation
    • destructiveHint: true
Only reads 12Show 12 read-only tools
  • reamaze_get_articleGet a single help-center article by its slug.No findings

    Why it is in this group

    • The name "reamaze_get_article" says "get": a word for reading.
    Description, as the server wrote it
    Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.

    Annotations the server declares

    • title: Get article
    • readOnlyHint: true
  • reamaze_get_channelGet a single channel by its slug.No findings

    Why it is in this group

    • The name "reamaze_get_channel" says "get": a word for reading.
    Description, as the server wrote it
    Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.

    Annotations the server declares

    • title: Get channel
    • readOnlyHint: true
  • reamaze_get_contactGet a single contact (customer) by identifier (email or id).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "reamaze_get_contact" says "get": a word for reading.

    What it can reach

    • private-dataThe name "reamaze_get_contact" says "get" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.

    Annotations the server declares

    • title: Get contact
    • readOnlyHint: true
  • reamaze_get_conversationGet a single conversation by its slug.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "reamaze_get_conversation" says "get": a word for reading.

    What it can reach

    • private-dataThe name "reamaze_get_conversation" says "get" and "conversation": it reads messages.
    • private-dataThe description's first sentence says "get" and "conversation": it reads messages.
    • untrusted-inputThe name "reamaze_get_conversation" says "get" and "conversation": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.

    Annotations the server declares

    • title: Get conversation
    • readOnlyHint: true
  • reamaze_list_articlesList/search help-center (knowledge-base) articles.No findings

    Why it is in this group

    • The name "reamaze_list_articles" says "list": a word for reading.
    Description, as the server wrote it
    List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.

    Annotations the server declares

    • title: List articles
    • readOnlyHint: true
  • reamaze_list_channelsList channels (inboxes: email, chat, social, etc.).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "reamaze_list_channels" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "inbox": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.

    Annotations the server declares

    • title: List channels
    • readOnlyHint: true
  • reamaze_list_contactsList/search contacts (customers).Reads private dataNo findings

    Why it is in this group

    • The name "reamaze_list_contacts" says "list": a word for reading.

    What it can reach

    • private-dataThe name "reamaze_list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.

    Annotations the server declares

    • title: List contacts
    • readOnlyHint: true
  • reamaze_list_conversationsList/search conversations (support tickets).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "reamaze_list_conversations" says "list": a word for reading.

    What it can reach

    • private-dataThe name "reamaze_list_conversations" says "list" and "conversation": it reads messages.
    • private-dataThe description's first sentence says "list" and "conversation": it reads messages.
    • untrusted-inputThe name "reamaze_list_conversations" says "list" and "conversation": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.

    Annotations the server declares

    • title: List conversations
    • readOnlyHint: true
  • reamaze_list_messagesList messages.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "reamaze_list_messages" says "list": a word for reading.

    What it can reach

    • private-dataThe name "reamaze_list_messages" says "list" and "message": it reads messages.
    • private-dataThe description's first sentence says "list" and "message": it reads messages.
    • untrusted-inputThe name "reamaze_list_messages" says "list" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List messages
    • readOnlyHint: true
  • reamaze_list_staffList staff (agent) accounts on the brand.No findings

    Why it is in this group

    • The name "reamaze_list_staff" says "list": a word for reading.
    Description, as the server wrote it
    List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.

    Annotations the server declares

    • title: List staff
    • readOnlyHint: true
  • reamaze_report_response_timeGet the response-time report (how quickly conversations were answered).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "get" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.

    Annotations the server declares

    • title: Report: response time
    • readOnlyHint: true
  • reamaze_report_volumeGet the conversation-volume report (counts over time).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "get" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.

    Annotations the server declares

    • title: Report: volume
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

56 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__re-amaze__reamaze_reply_conversation"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://re-amaze.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://re-amaze.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://re-amaze.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://re-amaze.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http re-amaze https://re-amaze.usefulapi.io/mcp
claude mcp add --transport http re-amaze https://re-amaze.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__re-amaze__reamaze_list_conversations",
      "mcp__re-amaze__reamaze_get_conversation",
      "mcp__re-amaze__reamaze_list_messages",
      "mcp__re-amaze__reamaze_list_contacts",
      "mcp__re-amaze__reamaze_get_contact",
      "mcp__re-amaze__reamaze_list_articles",
      "mcp__re-amaze__reamaze_get_article",
      "mcp__re-amaze__reamaze_list_staff",
      "mcp__re-amaze__reamaze_list_channels",
      "mcp__re-amaze__reamaze_get_channel",
      "mcp__re-amaze__reamaze_report_volume",
      "mcp__re-amaze__reamaze_report_response_time"
    ],
    "ask": [],
    "deny": [
      "mcp__re-amaze__reamaze_create_conversation",
      "mcp__re-amaze__reamaze_reply_conversation",
      "mcp__re-amaze__reamaze_update_conversation",
      "mcp__re-amaze__reamaze_create_contact",
      "mcp__re-amaze__reamaze_update_contact"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as re-amaze. Review it before you use it.

Capability tags behind 9 rules
  • mcp__re-amaze__reamaze_list_conversations private-data, untrusted-input
  • mcp__re-amaze__reamaze_get_conversation private-data, untrusted-input
  • mcp__re-amaze__reamaze_list_messages private-data, untrusted-input
  • mcp__re-amaze__reamaze_list_contacts private-data
  • mcp__re-amaze__reamaze_get_contact private-data, untrusted-input
  • mcp__re-amaze__reamaze_list_channels private-data, untrusted-input
  • mcp__re-amaze__reamaze_report_volume private-data, untrusted-input
  • mcp__re-amaze__reamaze_report_response_time private-data, untrusted-input
  • mcp__re-amaze__reamaze_reply_conversation outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/re-amaze/verify?hash=03d61ef5cff848f504e8fcf063de8d6696216abc17439071be0a203c276d0303" | jq -e '.changed == false'

Pinned hash 03d61ef5cff8, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/re-amaze/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/re-amaze
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/re-amaze.svg)](https://radar.anlyon.com/servers/io.usefulapi/re-amaze)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Re:amaze MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Re:amaze MCP by usefulapi safe?

No scan can promise that. What its definitions show: 17 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Re:amaze MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: reamaze_create_conversation, reamaze_reply_conversation, reamaze_update_conversation, reamaze_create_contact and reamaze_update_contact.

Can the Re:amaze MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Re:amaze MCP by usefulapi have?

17 tools: 5 destructive, 12 read. reamaze_create_conversation, reamaze_reply_conversation, reamaze_update_conversation, reamaze_create_contact, reamaze_update_contact, reamaze_list_conversations, reamaze_get_conversation, reamaze_list_messages and 9 more.

Does the Re:amaze MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Re:amaze MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): reamaze_reply_conversation.

Has the Re:amaze MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.