Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Roger Repair

REMOTE · ROGERREPAIR.COM

Book home repairs in the US and Canada: coverage, price ranges and one vetted local pro.

Available components

+3 this week 76 Trust /100

Last scanned (18 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 708 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://rogerrepair.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rogerrepair.com CN=YR2,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 2048 SHA256-RSA 5bc121ce571278c182762a7ff64354f11db
SANs: rogerrepair.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rogerrepair.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
rogerrepair.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'; base-uri 'self'; object-src 'none'; form-action 'self' https://checkout.stripe.com; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rogerrepair.com/mcp Verified 200
http (plaintext) http://rogerrepair.com/mcp HTTPS enforced 308 https://rogerrepair.com/mcp
MCP tools · 5 exposed · ~488 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_coverage ~103

Check whether Roger serves a ZIP or postal code, and whether a vetted pro for the trade is available there right now.

NameTypeReqDescription
postal_codestringyesUS 5-digit ZIP (e.g. 33133) or Canadian postal code (e.g. M5V 2T6) where the work is.
servicestring–Optional. A trade from list_services (e.g. 'plumbing') or a few words about the problem.

No output schema declared.

No examples provided.

get_estimate ~96

Get the estimated price range Roger shows for this problem at this location. Does not create a request.

NameTypeReqDescription
postal_codestringyesUS 5-digit ZIP (e.g. 33133) or Canadian postal code (e.g. M5V 2T6) where the work is.
problemstringyesThe homeowner's problem in plain words, e.g. 'Kitchen sink is leaking under the cabinet'.

No output schema declared.

No examples provided.

get_request_status ~33

Check where a Roger repair request stands, using the request_id from request_booking.

NameTypeReqDescription
request_idstringyes–

No output schema declared.

No examples provided.

list_services ~24

List the 30 home repair trades Roger books in the United States and Canada.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_booking ~232

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.

NameTypeReqDescription
address_line1stringyesStreet address of the job.
citystringyes–
emailstringyesHomeowner's email. Roger sends booking updates here.
first_namestringyes–
homeowner_confirmedbooleanyesTrue when the homeowner has reviewed these details and asked for the request to be sent.
last_namestringyes–
phonestring–Optional. Homeowner phone so the pro can reach them.
postal_codestringyesUS 5-digit ZIP (e.g. 33133) or Canadian postal code (e.g. M5V 2T6) where the work is.
problemstringyesThe homeowner's problem in plain words, e.g. 'Kitchen sink is leaking under the cabinet'.
statestringyesState or province.

No output schema declared.

No examples provided.

Install

How do I install the Roger Repair MCP server?

Roger Repair is a hosted endpoint at https://rogerrepair.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · rogerrepair.com

# add to Claude Code
claude mcp add --transport http com-rogerrepair-roger-repair 'https://rogerrepair.com/mcp'
Common questions

What is the Roger Repair MCP server?

Roger Repair is an MCP server listed in the public MCP registry as com.rogerrepair/roger-repair. Book home repairs in the US and Canada: coverage, price ranges and one vetted local pro. This page covers its hosted endpoint (https://rogerrepair.com/mcp).

Is the Roger Repair MCP server safe to use?

Roger Repair scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Roger Repair MCP server expose?

Roger Repair exposes 5 tools: list_services, check_coverage, get_estimate, request_booking, get_request_status. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

Does the Roger Repair MCP server require authentication?

No. We connected to Roger Repair without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Roger Repair MCP server still maintained?

Roger Repair is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Roger Repair MCP server?

VerifyMCP ran 13 checks on Roger Repair, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.