PermitReporter — US Building Permit Intelligence
Server Details
Source-linked building-permit search across 34 US states and DC, with county-level coverage.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 25.0% over 65 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Most tools have a clear purpose, but fetch with a permit:ID overlaps heavily with get_permit_record, and get_contractor_leads overlaps with search_permits for finding collected permit records. The descriptions help differentiate, but an agent could still select the wrong tool.
Tool names are snake_case and mostly follow a verb_noun pattern like get_county_coverage and search_permits. However, fetch and search are generic single-word verbs that break the otherwise consistent naming rhythm.
Eight tools is well-scoped for a permit-data intelligence service, covering search, retrieval, coverage, alerts, and contractor leads. Each tool has a defined role and the set is easy to navigate.
The core workflow is covered: search permits, retrieve records, check coverage, create watches, and get contractor leads. Minor gaps exist such as no way to list or delete permit watches, but agents can work around these.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- Changed
fetch5 fields changed- changed
Input schema / properties / id / descriptionPrevious value: -"A guide:… or permit:… ID returned by search."New value: +"A free guide:ID from search, or a paid permit:ID using a numeric record_id from search_permits." - removed
Output schema / additionalPropertiesRemoved value: -false - added
Output schema / oneOfAdded value: +[ + { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "billed": { + "type": "boolean" + }, + "id": { + "type": "string" + }, + "metadata": { + "additionalProperties": { + "type": "string" + }, + "type": "object" + }, + "price_charged_usdc": { + "type": "string" + }, + "text": { + "type": "string" + }, + "title": { + "type": "string" + }, + "url": { + "format": "uri", + "type": "string" + } + }, + "required": [ + "id", + "title", + "text", + "url", + "metadata" + ], + "type": "object" + }, + { + "additionalProperties": true, + "properties": { + "error": { + "type": "string" + } + }, + "required": [ + "error" + ], + "type": "object" + } +] - removed
Output schema / propertiesRemoved value: -{ - "id": { - "type": "string" - }, - "metadata": { - "additionalProperties": { - "type": "string" - }, - "type": "object" - }, - "text": { - "type": "string" - }, - "title": { - "type": "string" - }, - "url": { - "format": "uri", - "type": "string" - } -} - removed
Output schema / requiredRemoved value: -[ - "id", - "title", - "text", - "url", - "metadata" -]
- Changed
get_contractor_leads2 fields changed- changed
Input schema / properties / limit / defaultPrevious value: -20New value: +25 - changed
Input schema / properties / limit / maximumPrevious value: -50New value: +100
- Changed
search_permits4 fields changed- changed
Input schema / properties / limit / defaultPrevious value: -20New value: +25 - changed
Input schema / properties / limit / maximumPrevious value: -50New value: +100 - added
Input schema / properties / qAdded value: +{ + "description": "Alias for query; supply only one.", + "maxLength": 300, + "type": "string" +} - added
Input schema / properties / stateAdded value: +{ + "description": "Tracked US state or district.", + "pattern": "^[A-Za-z]{2}$", + "type": "string" +}
8 tool updates
- First observed
create_permit_watch - First observed
fetch - First observed
get_contractor_leads - First observed
get_county_coverage - First observed
get_permit_record - First observed
get_statewide_snapshot - First observed
search - First observed
search_permits
Related MCP Connectors
U.S. building permits, permit histories by address and contractors from city and county records.
Building permits by address for a growing list of US cities and counties, from city open data.
Building permits from 18 US cities (NYC, LA, Chicago, Philadelphia...), Canada, Ireland, France.
US parcels and building permits from public sources. No owner data. Pay per record or monthly plan.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables US address resolution and location-scoped search of building permits and construction contractors via the Shovels.ai API.10 npmMIT
- AlicenseAqualityAmaintenanceOwner, APN and address lookup across 479 US counties (494 verified ArcGIS REST endpoints, all 50 states plus DC), plus city code-violation, building-permit and zoning-case datasets. No API key; built on public county GIS data.4356 npm1MIT
- AlicenseAqualityCmaintenanceSearch official US government data from any MCP client: building permits from 10 city open-data portals, federal contract opportunities from SAM.gov with contracting-officer contacts, and the CMS NPI healthcare-provider registry. Open-source TypeScript server; data delivered via Apify's pay-per-result actors using your own Apify token.3MIT
- FlicenseNot gradedqualityFmaintenanceEnables municipal permit preflight checks for construction and renovation projects, returning evidence-linked, rule-version-aware results without using an LLM.-
Glama MCP Gateway
Add one secure layer between your agents and this server.