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.

Roofer Registry

REMOTE · ROOFERREGISTRY.COM

State-licensed roofing contractors with regulator discipline records and provenance.

+3 this week 64 Trust /100

Last scanned (11 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 5 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 Security63
Transport & Reachability100
Schema Quality & AI Usability40
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1266 tokens (~126/item across 10 items; 9 tools + 1 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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_contact" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 5 Nov 26 +1

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

  • 2 Nov 26 +1
    • Tool “check_license” rewrote its description, which is the text the model reads security
  • 31 Oct 26 +1
    • Tool “check_license” rewrote its description, which is the text the model reads security
  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 22 Oct 26 57

    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 5 Nov 2026 · Probed https://rooferregistry.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rooferregistry.com CN=YR2,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 RSA 2048 SHA256-RSA 693ed70858ed0e4b127efcc9b172c862c63
SANs: rooferregistry.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 rooferregistry.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
rooferregistry.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rooferregistry.com/api/mcp Verified 200
http (plaintext) http://rooferregistry.com/api/mcp HTTPS enforced 308 https://rooferregistry.com/api/mcp
MCP tools · 9 exposed · ~1,262 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
changes_since ~118

License changes (new, lapsed, status change) since a given date, optionally filtered by state and change type. Changes are tracked starting from the first roster refresh after deploy — no backfill is available. Use when monitoring for new licenses, lapses, or status changes.

NameTypeReqDescription
cursorstring––
limitinteger––
sincestringyesISO date, max 90 days back, e.g. 2026-09-01
statestring––
typestring––

No output schema declared.

No examples provided.

check_license ~201

Look up one roofing contractor license or registration by state and number. Returns status as published by the state regulator, a machine-readable verdict, licensee name, city, expiration, and provenance (regulator source URL + fetch date). Verdicts: licensed-active | licensed-not-active (trade license states like FL), registered-active | registered-not-active (registration states like NJ/PA — business registration, not a trade license), not-in-roster, not-found. The verdict is derived from the regulator-published status, not a recommendation. Use this when a user asks "is this roofing contractor licensed" or has a license number from a truck, yard sign, ad, or contract.

NameTypeReqDescription
license_numberstringyesLicense number as printed, e.g. CCC1325838 or CGC061405; hyphens/spaces are ignored
statestringyesTwo-letter state code or state name, e.g. FL, tx, Florida

No output schema declared.

No examples provided.

compare_rules ~115

Compare a specific rule field across 2–10 states. Only states with verified: true carry a rule. Treat null as "not verified", not "no rule". Input formats: states as two-letter codes (FL, GA, TX); field is one of licensing, licenseTypes, deductibleWaiver, depositRule, permit, insurance, unlicensedPenalty, rightToCancel, aob.

NameTypeReqDescription
fieldstringyes–
statesarrayyesTwo-letter state codes, e.g. ["FL", "GA"]

No output schema declared.

No examples provided.

enforcement_actions ~153

Board discipline and unlicensed-activity citations for a state, license number, name, or county. Merges licensed-activity discipline rows and unlicensed-activity citations, newest first. Republished as filed; a citation is an allegation the board acted on, a Final Order is the board's decision.

NameTypeReqDescription
all_tradesboolean––
countystring–e.g. Miami-Dade
license_numberstring–e.g. CCC1325838
limitinteger––
namestring–Respondent or DBA name fragment
sincestring–ISO date, e.g. 2025-01-01
statestringyes–

No output schema declared.

No examples provided.

request_contact ~222

Send a contact request to ONE specific licensee the user has chosen, by license number. This creates the same consent-recorded request a person submits on the profile page; it is not lead routing and we never pick the licensee for the user. Only call after the user has seen the record and explicitly chosen this licensee. Required consent text must be shown to the user verbatim before calling.

NameTypeReqDescription
consent_confirmedbooleanyesUser saw the consent text and agreed
emailstringyes–
first_namestringyes–
insurance_jobstringyesis this an insurance claim: yes, no, not-sure
license_numberstringyes–
phonestringyes–
project_typestringyesproject type: replacement, repair-leak, storm, inspection, gutters, new-construction, commercial
statestringyes–
timelinestringyeswhen needed: emergency, within-month, 1-3-months, just-quotes
zipstringyes–

No output schema declared.

No examples provided.

search_licensees ~92

Search roofing contractors by name, firm, or partial license number, optionally within a state and city. Returns up to 50 regulator-sourced records with a true total count. Use this when the user has a name but no license number.

NameTypeReqDescription
citystring––
limitinteger––
querystringyesName, firm, or license fragment
statestring––

No output schema declared.

No examples provided.

state_rules ~106

Return what Roofer Registry has verified about a state's rules for roofing contractors: licensing, licenseTypes, deductibleWaiver, depositRule, permit, insurance, unlicensedPenalty, rightToCancel, aob — each { value, quote, citation, url } or null. Plus regulator, lookup URL, active-licensee count. If the state is not yet verified, the response says so — do not state a rule for that state from this source.

NameTypeReqDescription
statestringyes–

No output schema declared.

No examples provided.

unlicensed_activity ~161

List people and companies the state board cited for unlicensed contracting, filtered by county and/or name. Use when the user has a name or company from a truck or flyer but no license number, or asks who was caught working unlicensed after a storm. Republished as filed; a citation is not a judgment. Defaults to roofing-typed citations; set all_trades=true for all construction trades.

NameTypeReqDescription
all_tradesboolean–false (default) = roofing-typed citations only; true = all trades
countystring–e.g. Lee, Miami-Dade, Dade — normalized automatically
limitinteger––
namestring–Respondent or DBA name fragment
statestringyes–

No output schema declared.

No examples provided.

verify_live ~94

Fetch the current license status directly from the state regulator (FL only) and compare it with our roster copy. Uses a 24-hour cache; the second call within 24h returns cached: true. Other states return { supported: false, lookupUrl }. Hard cap: 100 live fetches per UTC day.

NameTypeReqDescription
license_numberstringyese.g. CCC1325838
statestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Roofer Registry MCP server?

Roofer Registry is a hosted endpoint at https://rooferregistry.com/api/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 · rooferregistry.com

# add to Claude Code
claude mcp add --transport http com-rooferregistry-roofer-registry 'https://rooferregistry.com/api/mcp'
Common questions

What is the Roofer Registry MCP server?

Roofer Registry is an MCP server listed in the public MCP registry as com.rooferregistry/roofer-registry. State-licensed roofing contractors with regulator discipline records and provenance. This page covers its hosted endpoint (https://rooferregistry.com/api/mcp).

Is the Roofer Registry MCP server safe to use?

Roofer Registry scores 64 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 Roofer Registry MCP server expose?

Roofer Registry exposes 9 tools: check_license, search_licensees, state_rules, unlicensed_activity, enforcement_actions, and 4 more. Their descriptions and schemas cost roughly 1,262 tokens of context every time the server is loaded.

Does the Roofer Registry MCP server require authentication?

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

Is the Roofer Registry MCP server still maintained?

Roofer Registry is still listed as active in the MCP registry. We last reached this channel on 5 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 Roofer Registry MCP server?

VerifyMCP ran 12 checks on Roofer Registry, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Roofer Registry: Authorization. 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.