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.

PermitReporter — US Building Permit Intelligence

REMOTE · PERMITREPORTER.COM

Source-linked building-permit search across 34 US states and DC, with county-level coverage.

0 this week 28 Trust /100

Last scanned (19 hours ago)

Scores higher than 13% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Search and Retrieval

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 Security71
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.53 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: partial → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 5 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “fetch” rewrote its description, which is the text the model reads security
    • Tool “get_contractor_leads” rewrote its description, which is the text the model reads security
    • Tool “get_permit_record” rewrote its description, which is the text the model reads security
    • Tool “search” rewrote its description, which is the text the model reads security
    • Tool “search_permits” rewrote its description, which is the text the model reads security
    • Schema quality: 71 → 82 ▼ functional
    • Tool coverage: 41% → 46% ▲ functional
    • Server version: 1.0.0 → 2.0.0 functional
    • “search_permits” added an optional parameter “q” cosmetic
    • “search_permits” added an optional parameter “state” cosmetic
    • “fetch” reworded the description of “id” cosmetic
  • 31 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Aug 26 0

    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 4 Nov 2026 · Probed https://permitreporter.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=permitreporter.com CN=WE1,O=Google Trust Services,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA256 6ebfbde42a5bb1990e8c2a86105ef70e
SANs: permitreporter.com, *.permitreporter.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of permitreporter.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
permitreporter.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 403
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://permitreporter.com/mcp Auth required 403
http (plaintext) http://permitreporter.com/mcp Inconclusive 403
MCP tools · 8 exposed · ~889 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
create_permit_watch ~261

Create a pending email watch only after the user reviews the exact email, search query and optional county, explicitly authorizes this request and confirmation email, and accepts https://permitreporter.com/terms and https://permitreporter.com/privacy. This additive action stores the email and search for alerts; it does not file a permit or prove coverage. The address must confirm before alerts begin. Reuse submission_id for safe retries.

NameTypeReqDescription
countystring–Optional county restriction. Bare for Georgia ('Cobb'), state-qualified elsewhere ('Los Angeles, CA').
emailstringyesThe user's reviewed email address. It is stored for confirmation and alerts, never returned.
querystringyesThe exact address, project, subdivision, business term or county-wide phrase the user approved.
submission_idstringyesGenerate once for this watch; reuse it when retrying the same exact request.
terms_and_privacy_acceptedbooleanyesTrue only after the user accepts https://permitreporter.com/terms and https://permitreporter.com/privacy.
user_authorizedbooleanyesTrue only after the user reviews the exact email, query and county and explicitly asks PermitReporter to create this watch and send its confirmation email.
NameTypeReqDescription
next_stepstringyes–
okbooleanyes–
referencestringyes–
replayedbooleanyes–
statusstringyes–
submission_meaningstringyes–
watchobjectyes–

No examples provided.

fetch ~75

Fetch a guide:ID for free, or a permit:ID for 0.005 USDC via x402. Permit records retain source, record date, collection timestamp and coverage limits.

NameTypeReqDescription
idstringyesA free guide:ID from search, or a paid permit:ID using a numeric record_id from search_permits.

Structured output declared, but exposes no named fields.

No examples provided.

get_contractor_leads ~97

Return recent, source-linked collected permits classified by trade and project scope for contractor research within the last days ending today (default 30). Costs 0.01 USDC via x402; empty results are unbilled. Classifications are editorial signals, not official fields or guaranteed work.

NameTypeReqDescription
countystring––
daysinteger––
limitinteger––
tradestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_county_coverage ~56

Return the current source route, issuer, cadence, lag, through-date, collected record count, sources and statistical floor for one covered US county. Call this before interpreting a missing county result.

NameTypeReqDescription
countystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_permit_record ~65

Retrieve one privacy-minimized collected building-permit record by PermitReporter record ID, including its canonical citation, official source link and collection timestamp. Costs 0.005 USDC via x402; a missing record is unbilled.

NameTypeReqDescription
record_idintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

get_statewide_snapshot ~93

Return current PermitReporter counts, route-status boundaries, record-date range and latest collection timestamp without returning personal data. Pass `state` with a two-letter code to get that one jurisdiction's collected coverage, including an explicit answer for states where nothing has been collected yet.

NameTypeReqDescription
statestring–Two-letter US state or district code, for example 'OH' or 'DC'. Omit for the national snapshot.

Structured output declared, but exposes no named fields.

No examples provided.

search ~54

Search free PermitReporter reviewed guides and coverage guidance. Returns guide IDs and canonical URLs. Use the paid search_permits tool for collected permit records.

NameTypeReqDescription
querystringyesA natural-language question about US building permits or PermitReporter.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_permits ~188

Costs 0.005 USDC via x402; empty results are unbilled. Search privacy-minimized collected building-permit records by public text, US county, city, PermitReporter trade classification or record-date range. Coverage spans 34 states and the District of Columbia; name a county bare for Georgia ('Cobb') or state-qualified elsewhere ('Los Angeles, CA'). Returns no raw payloads or party arrays. An empty result means no matching record was collected, not that no permit exists.

NameTypeReqDescription
citystring––
countystring––
date_fromstring––
date_tostring––
limitinteger––
qstring–Alias for query; supply only one.
querystring––
statestring–Tracked US state or district.
tradestring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the PermitReporter — US Building Permit Intelligence MCP server?

PermitReporter — US Building Permit Intelligence is a hosted endpoint at https://permitreporter.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 · permitreporter.com

# add to Claude Code
claude mcp add --transport http com-permitreporter-us-building-permits 'https://permitreporter.com/mcp'
Common questions

What is the PermitReporter — US Building Permit Intelligence MCP server?

PermitReporter — US Building Permit Intelligence is an MCP server listed in the public MCP registry as com.permitreporter/us-building-permits. Source-linked building-permit search across 34 US states and DC, with county-level coverage. This page covers its hosted endpoint (https://permitreporter.com/mcp).

Is the PermitReporter — US Building Permit Intelligence MCP server safe to use?

PermitReporter — US Building Permit Intelligence scores 28 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 PermitReporter — US Building Permit Intelligence MCP server expose?

PermitReporter — US Building Permit Intelligence exposes 8 tools: search, fetch, search_permits, get_permit_record, get_county_coverage, and 3 more. Their descriptions and schemas cost roughly 889 tokens of context every time the server is loaded.

Does the PermitReporter — US Building Permit Intelligence MCP server require authentication?

Yes. PermitReporter — US Building Permit Intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the PermitReporter — US Building Permit Intelligence MCP server still maintained?

PermitReporter — US Building Permit Intelligence is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.