ReplyOnTheFly
com.replyonthefly/replyontheflyreplyonthefly.comstreamable-httpv1.0.0Scanned
Writes replies to Google, Yelp and other customer reviews, and texts asking for a review.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- 2 findings
Anlyon alternative
2 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 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 →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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "write_review_reply" says "write": a word for a change.
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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "write_review_request_message" says "write": a word for a change.
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.
Findings
Matches of fixed checks, with the text they matched.
The server marks "write_review_reply" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "write_review_reply" says "write": a word for a change.
The server marks "write_review_request_message" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "write_review_request_message" says "write": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http replyonthefly https://www.replyonthefly.com/mcpclaude mcp add --transport http replyonthefly https://www.replyonthefly.com/mcpRun 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.
{
"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://anlyon.dev/api/v1/servers/com.replyonthefly/replyonthefly/verify?hash=5f9f4fedc2ae89d87eb4d85f2d5cb3664624fba9d2cc8ffcc98dfb6dbfcb9c0b" | jq -e '.changed == false'Pinned hash 5f9f4fedc2ae, from Oct 22, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.replyonthefly/replyonthefly/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.replyonthefly/replyonthefly)Source: MCP Registry. Synced Oct 22, 2026, 20:17 UTC.