Roger Repair MCP server
com.rogerrepair/roger-repairrogerrepair.comstreamable-httpv1.0.0Scanned
Book home repairs in the US and Canada: coverage, price ranges and one vetted local pro.
5 tools: 1 do something that can't be undone, 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Roger Repair MCP server can do
The Roger Repair MCP server is published by rogerrepair.com, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_booking) and create or change data (1 tool: check_coverage), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (request_booking); 1 tool can send data out of your system (request_booking).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
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.
5 tools
Can't be undone 1Claude Code: ask
request_bookingSends a homeowner repair request to Roger, which matches one vetted local pro.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "request_booking" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Sends a homeowner repair request to Roger, which matches one vetted local pro. Returns a confirm_url where the homeowner confirms and books on rogerrepair.com. Requires homeowner_confirmed=true. Emails at example.com run in test mode: nothing is saved.
Annotations the server declares
- title: Send a repair request
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
check_coverageCheck whether Roger serves a ZIP or postal code, and whether a vetted pro for the trade is available there right now.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check whether Roger serves a ZIP or postal code, and whether a vetted pro for the trade is available there right now.
Annotations the server declares
- title: Check coverage
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_estimateGet the estimated price range Roger shows for this problem at this location.No findings
Why it is in this group
- The name "get_estimate" says "get": a word for reading.
Description, as the server wrote it Get the estimated price range Roger shows for this problem at this location. Does not create a request.
Annotations the server declares
- title: Get a price range
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_request_statusCheck where a Roger repair request stands, using the request_id from request_booking.No findings
Why it is in this group
- The name "get_request_status" says "get": a word for reading.
Description, as the server wrote it Check where a Roger repair request stands, using the request_id from request_booking.
Annotations the server declares
- title: Check a request
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_servicesList the 30 home repair trades Roger books in the United States and Canada.No findings
Why it is in this group
- The name "list_services" says "list": a word for reading.
Description, as the server wrote it List the 30 home repair trades Roger books in the United States and Canada.
Annotations the server declares
- title: List Roger services
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 9, 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
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://rogerrepair.com/mcp: tools/list returned 5 tools to an anonymous client, including request_booking (irreversible), check_coverage (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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 roger-repair https://rogerrepair.com/mcpclaude mcp add --transport http roger-repair https://rogerrepair.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": [
"mcp__roger-repair__list_services",
"mcp__roger-repair__get_estimate",
"mcp__roger-repair__get_request_status"
],
"ask": [
"mcp__roger-repair__check_coverage",
"mcp__roger-repair__request_booking"
],
"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 roger-repair. Review it before you use it.
Capability tags behind 1 rule
- mcp__roger-repair__request_booking untrusted-input, 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.rogerrepair/roger-repair/verify?hash=7f9ef324556169a06ca39e3bcc9bc32936ccb9cb4019d94ce3f4d70d04092266" | jq -e '.changed == false'Pinned hash 7f9ef3245561, from Nov 8, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.rogerrepair/roger-repair/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.rogerrepair/roger-repair)Source: MCP Registry. Synced Nov 8, 2026, 16:18 UTC.
Roger Repair MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Roger Repair MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 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 Roger Repair MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Roger Repair MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_booking.
What tools does the Roger Repair MCP server have?
- 5 tools: 1 irreversible, 1 write, 3 read. request_booking, check_coverage, list_services, get_estimate and get_request_status.
Does the Roger Repair MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Roger Repair MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_booking.
Has the Roger Repair MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.