Skip to content

ReplyOnTheFly MCP server

com.replyonthefly/replyontheflyreplyonthefly.comstreamable-httpv1.0.1Scanned

Writes replies to Google, Yelp and other customer reviews, and texts asking for a review.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ReplyOnTheFly MCP server can do

The ReplyOnTheFly MCP server is published by replyonthefly.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: write_review_reply and write_review_request_message), but cannot delete data. None of its tools only reads.

2 tools can send data out of your system (write_review_reply and write_review_request_message).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.1.

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.

2 tools

Changes things 2Claude Code: ask
  • write_review_replyWrites a reply a business owner can post under a customer review on Google, Yelp, Facebook, TripAdvisor or Trustpilot.Can send data out1 finding

    Why it is in this group

    • The name "write_review_reply" says "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "write_review_reply" says "write" and "reply": it writes something other people read.

    Findings

    • Warn

      The server marks "write_review_reply" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "write_review_reply" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Writes a reply a business owner can post under a customer review on Google, Yelp, Facebook, TripAdvisor or Trustpilot. Use it when someone shares a review of their business and wants a response to it, including angry or negative reviews. The reply follows the star rating: it thanks happy customers, and for low ratings it acknowledges the problem without arguing and offers to make it right. It does not post anything anywhere; the owner copies the reply and posts it themselves. It does not write reviews.

    Annotations the server declares

    • title: Write a review reply
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: false
  • write_review_request_messageWrites short messages a business owner can text or email to a customer to ask for a Google review, adapted to the type of business.Can send data out1 finding

    Why it is in this group

    • The name "write_review_request_message" says "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "write_review_request_message" says "write" and "message": it writes something other people read.
    • outboundThe input takes a destination (input.channel): what the tool writes goes there.

    Findings

    • Warn

      The server marks "write_review_request_message" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "write_review_request_message" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Writes short messages a business owner can text or email to a customer to ask for a Google review, adapted to the type of business. Use it when someone wants more Google reviews or asks how to ask a customer for a review. Returns up to three ready-to-send options with the owner's review link at the end. It does not send anything. The messages never offer incentives, which Google prohibits.

    Annotations the server declares

    • title: Write a review request message
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.replyonthefly.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://www.replyonthefly.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.replyonthefly.com/mcp: tools/list returned 2 tools to an anonymous client, including write_review_reply (write), write_review_request_message (write)

    What this check looks for

Posture changes

  1. Nov 7, 2026
    • RFC 9728 protected resource metadata: none to https://www.replyonthefly.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://www.replyonthefly.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "write_review_reply" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "write_review_reply" says "write": a word for a change.

    What this check looks for
  • The server marks "write_review_request_message" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "write_review_request_message" says "write": a word for a change.

    What this check looks for

History

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

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://www.replyonthefly.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://www.replyonthefly.com; Dynamic client registration: not obs…View diff
    • RFC 9728 protected resource metadata: none to https://www.replyonthefly.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://www.replyonthefly.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

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

claude mcp add --transport http replyonthefly https://www.replyonthefly.com/mcp
claude mcp add --transport http replyonthefly https://www.replyonthefly.com/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": [],
    "ask": [
      "mcp__replyonthefly__write_review_reply",
      "mcp__replyonthefly__write_review_request_message"
    ],
    "deny": []
  }
}

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 replyonthefly. Review it before you use it.

Capability tags behind 2 rules
  • mcp__replyonthefly__write_review_reply outbound
  • mcp__replyonthefly__write_review_request_message 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/com.replyonthefly/replyonthefly/verify?hash=5f9f4fedc2ae89d87eb4d85f2d5cb3664624fba9d2cc8ffcc98dfb6dbfcb9c0b" | jq -e '.changed == false'

Pinned hash 5f9f4fedc2ae, from Nov 8, 2026, 23:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.replyonthefly/replyonthefly/changes.xml

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

Badge

Anlyon Radar badge for com.replyonthefly/replyonthefly
[![Anlyon Radar](https://radar.anlyon.com/badge/com.replyonthefly/replyonthefly.svg)](https://radar.anlyon.com/servers/com.replyonthefly/replyonthefly)

Source: MCP Registry · repository. Synced Oct 24, 2026, 04:17 UTC.

ReplyOnTheFly MCP server: questions and answers

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

Is the ReplyOnTheFly MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 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 ReplyOnTheFly MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ReplyOnTheFly MCP server 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 ReplyOnTheFly MCP server have?

2 tools: 2 write. write_review_reply and write_review_request_message.

Does the ReplyOnTheFly MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ReplyOnTheFly MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): write_review_reply and write_review_request_message.

Has the ReplyOnTheFly MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.