# Roofer Registry (remote · rooferregistry.com)

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

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `rooferregistry.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp.md), [page](https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp)

## Channel facts

- Endpoint: `https://rooferregistry.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 40/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-rooferregistry-roofer-registry 'https://rooferregistry.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rooferregistry-roofer-registry": {
      "url": "https://rooferregistry.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rooferregistry-roofer-registry": {
      "type": "http",
      "url": "https://rooferregistry.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-rooferregistry-roofer-registry]
url = "https://rooferregistry.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rooferregistry-roofer-registry": {
      "type": "remote",
      "url": "https://rooferregistry.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rooferregistry-roofer-registry --url 'https://rooferregistry.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rooferregistry-roofer-registry:
    url: "https://rooferregistry.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rooferregistry-roofer-registry": {
      "Transport": "http",
      "Url": "https://rooferregistry.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rooferregistry-roofer-registry -t streamable-http -u 'https://rooferregistry.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-rooferregistry-roofer-registry": {
      "type": "http",
      "url": "https://rooferregistry.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 64, +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.

### 2026-11-02 (score 63, +1)

- [security] Tool “check_license” rewrote its description, which is the text the model reads

### 2026-10-31 (score 62, +1)

- [security] Tool “check_license” rewrote its description, which is the text the model reads

### 2026-10-29 (score 61, +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.

### 2026-10-27 (score 60, +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.

### 2026-10-25 (score 59, +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.

### 2026-10-23 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (9)

### `check_license` (~201 tokens)

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.

Input parameters:

- `license_number` (string, required): License number as printed, e.g. CCC1325838 or CGC061405; hyphens/spaces are ignored
- `state` (string, required): Two-letter state code or state name, e.g. FL, tx, Florida

### `search_licensees` (~92 tokens)

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.

Input parameters:

- `city` (string)
- `limit` (integer)
- `query` (string, required): Name, firm, or license fragment
- `state` (string)

### `state_rules` (~106 tokens)

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.

Input parameters:

- `state` (string, required)

### `unlicensed_activity` (~161 tokens)

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.

Input parameters:

- `all_trades` (boolean): false (default) = roofing-typed citations only; true = all trades
- `county` (string): e.g. Lee, Miami-Dade, Dade — normalized automatically
- `limit` (integer)
- `name` (string): Respondent or DBA name fragment
- `state` (string, required)

### `enforcement_actions` (~153 tokens)

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.

Input parameters:

- `all_trades` (boolean)
- `county` (string): e.g. Miami-Dade
- `license_number` (string): e.g. CCC1325838
- `limit` (integer)
- `name` (string): Respondent or DBA name fragment
- `since` (string): ISO date, e.g. 2025-01-01
- `state` (string, required)

### `compare_rules` (~115 tokens)

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.

Input parameters:

- `field` (string, required)
- `states` (array, required): Two-letter state codes, e.g. ["FL", "GA"]

### `changes_since` (~118 tokens)

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.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `since` (string, required): ISO date, max 90 days back, e.g. 2026-09-01
- `state` (string)
- `type` (string)

### `verify_live` (~94 tokens)

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.

Input parameters:

- `license_number` (string, required): e.g. CCC1325838
- `state` (string, required)

### `request_contact` (~222 tokens)

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.

Input parameters:

- `consent_confirmed` (boolean, required): User saw the consent text and agreed
- `email` (string, required)
- `first_name` (string, required)
- `insurance_job` (string, required): is this an insurance claim: yes, no, not-sure
- `license_number` (string, required)
- `phone` (string, required)
- `project_type` (string, required): project type: replacement, repair-leak, storm, inspection, gutters, new-construction, commercial
- `state` (string, required)
- `timeline` (string, required): when needed: emergency, within-month, 1-3-months, just-quotes
- `zip` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp#diagnostics

## Score history

- 2026-11-06: 64
- 2026-11-05: 64
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 60
- 2026-10-27: 60
- 2026-10-26: 59
- 2026-10-25: 59
- 2026-10-24: 58
- 2026-10-23: 58
- 2026-10-22: 57

## 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 6 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.

## Links

- Remote endpoint: https://rooferregistry.com/api/mcp
- Repository: https://github.com/kevincolahan/roofing-directory
- Website: https://rooferregistry.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-rooferregistry-roofer-registry/api-mcp