PermitStack
REMOTE · MCP.PERMIT-STACK.COM
U.S. building permits, permit histories by address and contractors from city and county records.
Available components
Last scanned (19 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1809 tokens (~301/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 77
First indexed and scored.
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://mcp.permit-stack.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.permit-stack.com | CN=YE2,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 542843c8a970a9aa3f0b486071032f17ac6 |
| SANs: mcp.permit-stack.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.permit-stack.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| permit-stack.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.permit-stack.com/.well-known/oauth-protected-resource", scope="permits:read"
Bearer resource_metadata="https://mcp.permit-stack.com/.well-known/oauth-protected-resource", scope="permits:read" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.permit-stack.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.permit-stack.com/mcp |
| Authorisation server | https://api.permit-stack.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.permit-stack.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.permit-stack.com/mcp | HTTPS enforced | 301 | https://mcp.permit-stack.com/mcp |
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 →
get_contractor_permits Contractor's permits ~157
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 name, owner mailing address or permit applicant name fields.
| Name | Type | Req | Description |
|---|---|---|---|
| contractor_id | string | yes | Contractor UUID from search_contractors results |
| page | integer | – | Page number, 1-based (default 1) |
| per_page | integer | – | Results per page (default 25, max 25) |
| start | integer | – | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in `_notes`) |
No output schema declared.
No examples provided.
get_coverage Data coverage ~129
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 permit held), filterable by state and by name, up to 25 per call, largest first. Without sign-in it returns the platform totals only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional text matched against jurisdiction names, e.g. 'Austin' or 'County' |
| state | string | – | Optional two-letter state code to list only that state's jurisdictions |
No output schema declared.
No examples provided.
get_permit Look up a permit by number ~199
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 permits are returned; give the city or state to tell them apart. If nothing matches exactly and a city or state was given, permits in that place whose number contains the text are returned instead, and `match` says "partial". When the connected account covers a limited date range, `account_window_from` is set and only permits from that date onward are searched. Results carry no property owner name, owner mailing address or permit applicant name fields.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City where the permit was issued (optional, narrows the match) |
| permit_number | string | yes | The permit number from the issuing jurisdiction |
| state | string | – | Two-letter state code (optional, narrows the match) |
No output schema declared.
No examples provided.
get_property_history Property permit history ~301
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 profile (permit timeline, category breakdown, contractors) and up to 25 permit records per page, newest first; `has_more` says whether the next page has more. Covers all permit categories. When the connected account covers a limited date range, the profile and records cover only that range, `account_window_from` is set, and `_notes` says so: the result is then not the property's full permit history. Results carry no property owner name, owner mailing address or permit applicant name fields.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address with house number, e.g. '123 Main St' (min 3 characters) |
| city | string | – | Optional city, to tell identical street addresses apart |
| page | integer | – | Page number, 1-based (default 1) |
| per_page | integer | – | Results per page (default 25, max 25) |
| start | integer | – | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in `_notes`) |
| state | string | – | Optional two-letter state code |
| zip | string | – | Optional ZIP code (prefix-matched) |
No output schema declared.
No examples provided.
search_contractors Search contractors ~249
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, specialties and activity score (0-100), sorted by activity score (highest first). Project values are not included; get_contractor_permits lists a contractor's permits with their estimated values.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City where the contractor has worked |
| min_permits | integer | – | Only contractors with at least this many permits |
| name | string | – | Contractor name (partial match) |
| page | integer | – | Page number, 1-based (default 1) |
| per_page | integer | – | Results per page (default 25, max 25) |
| specialty | string | – | Specialty/trade to filter by, e.g. 'solar', 'roofing', 'hvac' |
| start | integer | – | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in `_notes`) |
| state | string | – | Two-letter state code |
No output schema declared.
No examples provided.
search_permits Search building permits ~774
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 with address, dates, category, status, estimated value, contractor and description, plus the total number of matches. Response fields: `total` is exact unless `total_capped` is true, in which case it is a lower bound; when `total_unknown` is true the count could not be computed and `total` is null. `account_window_clamped`, `account_window_days` and `account_window_from` are set when the connected account covers a limited date range, and the results then cover only that range. Category HVAC also matches MECHANICAL, and MECHANICAL also matches HVAC. date_after/date_before match whichever date a permit has (issued, else filed), for feeds that publish only one of the two. Results carry no property owner name, owner mailing address or permit applicant name fields.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Permit category (case-insensitive). Common values: SOLAR, ROOFING, HVAC, NEW_CONSTRUCTION, POOL, ELECTRICAL, PLUMBING, DEMOLITION, MECHANICAL, RENOVATION. |
| city | string | – | City name, e.g. 'Austin', 'Boston', 'Miami-Dade County' |
| contractor_name | string | – | Filter by contractor name (partial match supported) |
| date_after | string | – | ISO date (YYYY-MM-DD): only permits dated on or after this date, using the issue date, else the filing date |
| date_before | string | – | ISO date (YYYY-MM-DD): only permits dated on or before this date, using the issue date, else the filing date |
| filed_after | string | – | ISO date (YYYY-MM-DD): only permits filed on or after this date |
| filed_before | string | – | ISO date (YYYY-MM-DD): only permits filed on or before this date |
| issued_after | string | – | ISO date (YYYY-MM-DD): only permits issued on or after this date |
| issued_before | string | – | ISO date (YYYY-MM-DD): only permits issued on or before this date |
| jurisdiction | string | – | Jurisdiction name or partial name, e.g. 'Wake County', 'Tacoma' |
| lat | number | – | Latitude for radius search (use with lng) |
| lng | number | – | Longitude for radius search (use with lat) |
| max_value | number | – | Maximum estimated project value in dollars |
| min_value | number | – | Minimum estimated project value in dollars |
| page | integer | – | Page number, 1-based (default 1) |
| per_page | integer | – | Results per page (default 25, max 25) |
| property_type | string | – | Property type, one of: residential, commercial, industrial, mixed_use, institutional, unknown (case-insensitive) |
| q | string | – | Free-text search over description, address, and permit number |
| radius_miles | number | – | Radius in miles for lat/lng search (max 50, default 5) |
| start | integer | – | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in `_notes`) |
| state | string | – | Two-letter US state code, e.g. 'TX', 'MA', 'FL' |
| status | string | – | Permit status, e.g. 'ISSUED', 'FINAL', 'EXPIRED', 'FILED' |
| zip_code | string | – | 5-digit ZIP code |
No output schema declared.
No examples provided.
How do I install the PermitStack MCP server?
PermitStack is a hosted endpoint at https://mcp.permit-stack.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 · mcp.permit-stack.com
claude mcp add --transport http com-permit-stack-permits 'https://mcp.permit-stack.com/mcp'
What is the PermitStack MCP server?
PermitStack is an MCP server listed in the public MCP registry as com.permit-stack/permits. U.S. building permits, permit histories by address and contractors from city and county records. This page covers its hosted endpoint (https://mcp.permit-stack.com/mcp).
Is the PermitStack MCP server safe to use?
PermitStack scores 83 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 PermitStack MCP server expose?
PermitStack exposes 6 tools: search_permits, get_permit, get_property_history, search_contractors, get_contractor_permits, get_coverage. Their descriptions and schemas cost roughly 1,809 tokens of context every time the server is loaded.
Does the PermitStack MCP server require authentication?
Yes. PermitStack 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 PermitStack MCP server still maintained?
PermitStack 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.