PermitStack MCP server

• Registry namecom.permit-stack/permitsverified in the MCP registry

The registry name sits under permit-stack.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-23
• Tools6
• Server calls itselfpermitstack
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 217 ms.

• Its tools do pull recent solar permits by zip code to build lead lists; look up the full permit history for a property, but not get alerts when matching permits are filed.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• What an agent can do with it2 of 3 use cases
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer246 ms
• Space in an agent's context≈ 2,405 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_permits

  Search U.S. building permits by location (city, state, ZIP code, or a lat/lng radius), category, status, property type, filing or issue date range, estimated project value, contractor name, or free text. Returns up to 25 permits per call…

• get_permit

  Look up a permit by the permit number assigned by the issuing jurisdiction, optionally narrowed by city and state. The number is matched exactly (ignoring case), and the same number can exist in several jurisdictions, so up to 5 matching…

• get_property_history

  Permit history for one property, looked up by street address (house number and street name, e.g. '123 Main St'). Optional city, state and ZIP narrow the match when the same street address exists in several places. Returns a property…

• search_contractors

  Search contractors by name, city, state or specialty. Returns up to 25 contractors per call with the contractor UUID, name, licence number and licence state, home city and state, total permit count, first and last permit dates…

• get_contractor_permits

  List the permits pulled by one contractor, identified by the contractor UUID from search_contractors. Returns up to 25 permits per page with the contractor's work history fields (dates, categories, values). Results carry no property owner…

• get_coverage

  Describe PermitStack's coverage: total permits, jurisdictions (active, archive, frozen) and states. On a signed-in connection it also lists covered jurisdictions with their permit counts, county and `data_through` (the date of the newest…