_ registry / mcp streamable-http · checked 4h ago

replyonthefly

https://www.replyonthefly.com

Registry code: bbd45171d8f7daab

api record

ReplyOnTheFly writes replies to customer reviews for business owners. When a user shares a review of their business (pasted text or a screenshot you have read), call write_review_reply with the business name, star rating and review text. Show the reply as written. If the user wants changes, call the tool again with owner_notes describing what they want, or alternate=true for different wording. Never invent facts about the business; only pass owner_notes the user actually gave. When the user wants to ask a customer for a review, call write_review_request_message.

endpoint
https://www.replyonthefly.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is replyonthefly live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is replyonthefly free to use?
Not measured yet.
What tools does replyonthefly have?
2 tools: write_review_reply, write_review_request_message.
Is replyonthefly safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
328ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • write_review_reply unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "business_name",
        "star_rating"
      ],
      "properties": {
        "tone": {
          "enum": [
            "friendly",
            "professional",
            "casual",
            "enthusiastic"
          ],
          "type": "string",
          "description": "Voice of the reply. Defaults to friendly."
        },
        "length": {
          "enum": [
            "concise",
            "standard",
            "detailed"
          ],
          "type": "string",
          "description": "concise is 1 to 2 sentences, standard 2 to 3, detailed 3 to 4. Defaults to standard."
        },
        "platform": {
          "enum": [
            "google",
            "yelp",
            "facebook",
            "tripadvisor",
            "trustpilot"
          ],
          "type": "string",
          "description": "Where the review was posted. Defaults to google."
        },
        "alternate": {
          "type": "boolean",
          "description": "Set true to get a differently worded version of a reply already written for the same review."
        },
        "owner_notes": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 200
          },
          "maxItems": 5,
          "description": "Facts or wishes the owner gave for this reply, e.g. \"we fixed the AC last week\" or \"sign off as Maria\". Only include what the owner actually said."
        },
        "review_text": {
          "type": "string",
          "maxLength": 2000,
          "description": "The review exactly as the customer wrote it. Leave out for a rating with no text."
        },
        "star_rating": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Star rating the customer gave, 1 to 5."
        },
        "business_name": {
          "type": "string",
          "maxLength": 120,
          "description": "Name of the business being reviewed."
        },
        "business_type": {
          "type": "string",
          "maxLength": 80,
          "description": "What kind of business it is, e.g. \"dentist\", \"pizza restaurant\", \"plumber\"."
        },
        "reviewer_name": {
          "type": "string",
          "maxLength": 120,
          "description": "The reviewer's display name, if shown. Leave out if unknown; the reply will not invent one."
        }
      },
      "additionalProperties": false
    }
    arguments 79 lines
  • write_review_request_message unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "business_name"
      ],
      "properties": {
        "channel": {
          "enum": [
            "text",
            "email"
          ],
          "type": "string",
          "description": "text (SMS or WhatsApp) or email. Defaults to text."
        },
        "review_link": {
          "type": "string",
          "maxLength": 300,
          "description": "The business's Google review link if the owner has it (https://...). Leave out and the messages use a placeholder."
        },
        "business_name": {
          "type": "string",
          "maxLength": 120,
          "description": "Name of the business asking for the review."
        },
        "business_type": {
          "type": "string",
          "maxLength": 80,
          "description": "What kind of business it is, e.g. \"plumber\", \"hair salon\", \"restaurant\". Picks the right wording."
        },
        "customer_first_name": {
          "type": "string",
          "maxLength": 120,
          "description": "The customer's first name, if the owner gave it."
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bbd45171d8f7daab.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bbd45171d8f7daab/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bbd45171d8f7daab/badge.svg)](https://brick.blue/agent/bbd45171d8f7daab?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.