reputemap
Registry code: b460c702aeaeaf0b
ReputeMap manages Google reviews for local businesses. Tools cover the workspace you connected (by signing in, or with an API key): list locations, read reviews (filterable), get review stats, draft AI replies, publish an approved reply to Google, send a review-request email, and check API credit usage. publish_reply is public and customer-visible - only call it with text the user has explicitly approved. Billable tool calls share the org's monthly API credits (default 1000/month) with the REST API. Docs: https://reputemap.com/docs/mcp
- endpoint
- https://api.reputemap.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 reputemap live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is reputemap free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does reputemap have?
- 7 tools: get_review_stats, list_reviews, list_locations, send_review_request, draft_reply, publish_reply, get_usage.
- Is reputemap 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.
90 days 99.6%· all time 99.6%
last good check
of 7 tools
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- list google reviews for a business
- draft replies to reviews
- publish a review reply
- send a review request email
- takes → gives
- text → data, text
- tools
- 5 reads1 changes data1 sends messages
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.
through this hub
successful
what callers paid
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.
get_review_stats reads auth-required 16h ago
Review stats per location and org totals: review counts, average rating, 1-5 star breakdown, unanswered count, and activity in the trailing window (default 30 days).
{ "type": "object", "properties": { "days": { "type": "integer", "default": 30, "maximum": 365, "minimum": 1 }, "location_id": { "type": "string", "description": "UUID from list_locations; omit for all locations" } }, "additionalProperties": false }arguments 16 lineslist_reviews reads auth-required 16h ago
List Google reviews for the org (newest first) with the published reply text inlined. Filter by location, star-rating range, replied/unreplied, or a trailing day window. Google moderates owner replies: reply_state is approved, pending (Google is checking it) or rejected (not shown on Google - has_reply is false and reply_policy_violation says why; write a new reply).
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1 }, "offset": { "type": "integer", "default": 0, "minimum": 0 }, "rating_max": { "type": "integer", "maximum": 5, "minimum": 1 }, "rating_min": { "type": "integer", "maximum": 5, "minimum": 1 }, "since_days": { "type": "integer", "maximum": 365, "minimum": 1, "description": "only reviews from the last N days" }, "location_id": { "type": "string", "description": "UUID from list_locations; omit for all locations" }, "unanswered_only": { "type": "boolean", "description": "true = only reviews without an owner reply on Google (a reply Google rejected counts as none)" } }, "additionalProperties": false }arguments 41 lineslist_locations reads auth-required 12h ago
List every business location this ReputeMap org manages, with ids to use in the other tools.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessend_review_request sends messages auth-required never probed
Send ONE review-request email to a real customer, through ReputeMap's campaign engine (respects unsubscribes and the suppression list). This emails a real person - only use it when the user explicitly asks to request a review. Returns status 'sent', 'skipped' (opted out or suppressed), 'already_requested' (this location already asked this address - no second email is sent and no credit is spent) or 'failed'.
{ "type": "object", "required": [ "location_id", "email" ], "properties": { "name": { "type": "string", "description": "customer name (optional)" }, "email": { "type": "string", "description": "customer email address" }, "location_id": { "type": "string", "description": "UUID from list_locations" } }, "additionalProperties": false }arguments 22 linesdraft_reply reads auth-required never probed
Generate 2-3 reply drafts for one review using ReputeMap's tuned generator (the same one the app uses, with the business's saved voice and sign-off), and save the draft so it appears in the app's editor. NEVER publishes anything - drafts only.
{ "type": "object", "required": [ "review_id" ], "properties": { "review_id": { "type": "string", "description": "UUID from list_reviews" }, "instructions": { "type": "string", "maxLength": 300, "description": "optional one-off guidance for this draft, e.g. 'mention the new units' or 'keep it under 40 words'" } }, "additionalProperties": false }arguments 18 linespublish_reply changes data auth-required never probed
PUBLISH a reply to this review's public Google profile. This is a public, customer-visible action - call it ONLY when the user has explicitly approved this exact text (Google's policy: a person approves every reply; one call per approved reply, never in bulk). If Google refuses the request, the text is preserved in ReputeMap with a manual fallback (status 'manual_required') - words are never lost. Google also moderates replies: google_state 'pending' = it is checking the reply before showing it; status 'rejected_by_google' = it will not show it (policy_violation and detail say why) - write a different reply.
{ "type": "object", "required": [ "review_id", "text" ], "properties": { "text": { "type": "string", "description": "the exact reply text the user approved" }, "review_id": { "type": "string", "description": "UUID from list_reviews" } }, "additionalProperties": false }arguments 18 linesget_usage reads auth-required 16h ago
Current month's API credit usage for this org (shared between the REST API and MCP tools).
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb460c702aeaeaf0b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b460c702aeaeaf0b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b460c702aeaeaf0b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.