Roofer Registry MCP server
com.rooferregistry/roofer-registryrooferregistry.comstreamable-httpv0.2.0Scanned
State-licensed roofing contractors with regulator discipline records and provenance.
9 tools: 1 do something that can't be undone, 3 change things and 5 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 Roofer Registry MCP server can do
The Roofer Registry MCP server is published by rooferregistry.com, a domain the MCP Registry verified. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_contact) and create or change data (3 tools: check_license, enforcement_actions and changes_since), but cannot delete data. 5 tools only read.
1 tool brings in text other people can write (state_rules); 1 tool can send data out of your system (request_contact).
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, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 0.2.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.
9 tools
Can't be undone 1Claude Code: ask
request_contactSend a contact request to ONE specific licensee the user has chosen, by license number.Can send data outNo findings
Why it is in this group
- The name "request_contact" 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
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Changes things 3Claude Code: ask
changes_sinceLicense changes (new, lapsed, status change) since a given date, optionally filtered by state and change type.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.
Description, as the server wrote it 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.
check_licenseLook up one roofing contractor license or registration by state and number.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.
Description, as the server wrote it 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.
enforcement_actionsBoard discipline and unlicensed-activity citations for a state, license number, name, or county.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.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
compare_rulesCompare a specific rule field across 2–10 states.No findings
Why it is in this group
- The name "compare_rules" says "compare": a word for reading.
Description, as the server wrote it 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.
search_licenseesSearch roofing contractors by name, firm, or partial license number, optionally within a state and city.No findings
Why it is in this group
- The name "search_licensees" says "search": a word for reading.
Description, as the server wrote it 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.
state_rulesReturn what Roofer Registry has verified about a state's rules for roofing contractors: licensing, licenseTypes, deductibleWaiver, depositRule, permit, insurance, unlicensedPenalty…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
unlicensed_activityList people and companies the state board cited for unlicensed contracting, filtered by county and/or name.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
verify_liveFetch the current license status directly from the state regulator (FL only) and compare it with our roster copy.No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it 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.
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 21, 2026, 19:24 UTC, unchanged since Oct 23, 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
- 4
- 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 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://rooferregistry.com/api/mcp: tools/list returned 9 tools to an anonymous client, including request_contact (irreversible), check_license (write), enforcement_actions (write), changes_since (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.
Tools1 changed.~1 changedView diff
- Changed:check_licenseChanges thingsdescription
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http roofer-registry https://rooferregistry.com/api/mcpclaude mcp add --transport http roofer-registry https://rooferregistry.com/api/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__roofer-registry__search_licensees",
"mcp__roofer-registry__state_rules",
"mcp__roofer-registry__unlicensed_activity",
"mcp__roofer-registry__compare_rules",
"mcp__roofer-registry__verify_live"
],
"ask": [
"mcp__roofer-registry__check_license",
"mcp__roofer-registry__enforcement_actions",
"mcp__roofer-registry__changes_since",
"mcp__roofer-registry__request_contact"
],
"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 roofer-registry. Review it before you use it.
Capability tags behind 2 rules
- mcp__roofer-registry__state_rules untrusted-input
- mcp__roofer-registry__request_contact 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.rooferregistry/roofer-registry/verify?hash=4dbfa7ce6e252e56daf5b41a194a359ac19a02de1e711e7b6b7a34d28b447ce9" | jq -e '.changed == false'Pinned hash 4dbfa7ce6e25, from Nov 8, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.rooferregistry/roofer-registry/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.rooferregistry/roofer-registry)Source: MCP Registry · repository. Synced Oct 22, 2026, 21:20 UTC.
Roofer Registry MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Roofer Registry MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 4 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 Roofer Registry MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Roofer Registry MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_contact.
What tools does the Roofer Registry MCP server have?
- 9 tools: 1 irreversible, 3 write, 5 read. request_contact, check_license, enforcement_actions, changes_since, search_licensees, state_rules, unlicensed_activity, compare_rules and 1 more.
Does the Roofer Registry MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Roofer Registry 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_contact.
Has the Roofer Registry MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.