
ReputeMap MCP server
Which servers in the official MCP registry are ReputeMap's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.reputemap/reputemapverified in the MCP registry
The registry name sits under reputemap.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools7
- Server calls itselfreputemap
- Server version1.1
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 55 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 4 of the 7 days it takes to judge reliability.
Once connected
- send_review_request, publish_reply change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 2 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- Use206 npm downloads a week
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer56 ms
- Space in an agent's context≈ 1,062 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 95 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 7
What an agent can do with it
- not sure · ask happy customers for Google reviews
- cannot · get alerted by email or WhatsApp to low-star reviews
- not sure · draft and publish replies to Google reviews
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: send_review_request, publish_reply
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_locationsList every business location this ReputeMap org manages, with ids to use in the other tools.
list_reviewsList 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…
get_review_statsReview 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).
send_review_requestSend 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…
draft_replyGenerate 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…
publish_replyPUBLISH 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…
get_usageCurrent month's API credit usage for this org (shared between the REST API and MCP tools).
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"reputemap": {
"type": "http",
"url": "https://api.reputemap.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http reputemap https://api.reputemap.com/mcpclaude.ai, ChatGPT and other clients: add https://api.reputemap.com/mcp as a custom connector in the settings.
Also shipped through: npm
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.