MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Re:amaze MCP by usefulapi

By usefulapi.io Verified namespace

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

WebsiteSource code
Connect to Re:amaze MCP by usefulapi
Checks passed
14 / 22

0 failed · 8 not measured

Median response
162 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
17

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 162 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name re-amaze-mcp.

  • Pass
    Lists tools

    tools/list returned 17 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 162 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 162 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    64 of 64 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:33:33.926433Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Re:amaze MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 17

reamaze_create_contact

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

Discovered
reamaze_create_conversation

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

Discovered
reamaze_get_article

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

Discovered
reamaze_get_channel

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

Discovered
reamaze_get_contact

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

Discovered
reamaze_get_conversation

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

Discovered
reamaze_list_articles

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

Discovered
reamaze_list_channels

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

Discovered
reamaze_list_contacts

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

Discovered
reamaze_list_conversations

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

Discovered
reamaze_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.

Discovered
reamaze_list_staff

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

Discovered
reamaze_reply_conversation

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

Discovered
reamaze_report_response_time

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

Discovered
reamaze_report_volume

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

Discovered
reamaze_update_contact

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

Discovered
reamaze_update_conversation

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

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected162 ms17

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to Re:amaze MCP by usefulapi