Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
PermitStack is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
U.S. building permits, permit histories by address and contractors from city and county records.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http permit-stack-permitstack-mcp https://mcp.permit-stack.com/mcp
# 2 — ask your agent for something these tools do
# search_permits, get_permit, get_property_history and 3 more
PermitStack costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PSAll 1 server
permit-stack1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http permit-stack-permitstack-mcp https://mcp.permit-stack.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 `to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | City name, e.g. 'Austin', 'Boston', 'Miami-Dade County' |
| state | string | no | Two-letter US state code, e.g. 'TX', 'MA', 'FL' |
| zip_code | string | no | 5-digit ZIP code |
| category | string | no | Permit category (case-insensitive). Common values: SOLAR, ROOFING, HVAC, NEW_CONSTRUCTION, POOL, ELECTRICAL, PLUMBING, DEMOLITION, MECHANICAL, RENOVATION. |
| status | string | no | Permit status, e.g. 'ISSUED', 'FINAL', 'EXPIRED', 'FILED' |
| jurisdiction | string | no | Jurisdiction name or partial name, e.g. 'Wake County', 'Tacoma' |
| property_type | string | no | Property type, one of: residential, commercial, industrial, mixed_use, institutional, unknown (case-insensitive) |
| filed_after | string | no | ISO date (YYYY-MM-DD): only permits filed on or after this date |
| filed_before | string | no | ISO date (YYYY-MM-DD): only permits filed on or before this date |
| issued_after | string | no | ISO date (YYYY-MM-DD): only permits issued on or after this date |
| issued_before | string | no | ISO date (YYYY-MM-DD): only permits issued on or before this date |
| date_after | string | no | ISO date (YYYY-MM-DD): only permits dated on or after this date, using the issue date, else the filing date |
| date_before | string | no | ISO date (YYYY-MM-DD): only permits dated on or before this date, using the issue date, else the filing date |
| min_value | number | no | Minimum estimated project value in dollars |
| max_value | number | no | Maximum estimated project value in dollars |
| lat | number | no | Latitude for radius search (use with lng) |
| lng | number | no | Longitude for radius search (use with lat) |
| radius_miles | number | no | Radius in miles for lat/lng search (max 50, default 5) |
| q | string | no | Free-text search over description, address, and permit number |
| contractor_name | string | no | Filter by contractor name (partial match supported) |
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 cont
| Parameter | Type | Required | Notes |
|---|---|---|---|
| permit_number | string | yes | The permit number from the issuing jurisdiction |
| city | string | no | City where the permit was issued (optional, narrows the match) |
| state | string | no | Two-letter state code (optional, narrows the match) |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Street address with house number, e.g. '123 Main St' (min 3 characters) |
| city | string | no | Optional city, to tell identical street addresses apart |
| state | string | no | Optional two-letter state code |
| zip | string | no | Optional ZIP code (prefix-matched) |
| per_page | integer | no | Results per page (default 25, max 25) |
| page | integer | no | Page number, 1-based (default 1) |
| start | integer | no | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in _notes) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Contractor name (partial match) |
| city | string | no | City where the contractor has worked |
| state | string | no | Two-letter state code |
| specialty | string | no | Specialty/trade to filter by, e.g. 'solar', 'roofing', 'hvac' |
| min_permits | integer | no | Only contractors with at least this many permits |
| per_page | integer | no | Results per page (default 25, max 25) |
| page | integer | no | Page number, 1-based (default 1) |
| start | integer | no | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in _notes) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contractor_id | string | yes | Contractor UUID from search_contractors results |
| per_page | integer | no | Results per page (default 25, max 25) |
| page | integer | no | Page number, 1-based (default 1) |
| start | integer | no | Instead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in _notes) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Optional two-letter state code to list only that state's jurisdictions |
| name | string | no | Optional text matched against jurisdiction names, e.g. 'Austin' or 'County' |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install PermitStack or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digeste85a7e6c8e4f30e605a5736ada2b5ec63ed3c78ff7dd99acb61746398ddd1ef7
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_permits | no tags | |
| get_permit | no tags | |
| get_property_history | no tags | |
| search_contractors | no tags | |
| get_contractor_permits | no tags | |
| get_coverage | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste85a7e6c8e4f30e6
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish PermitStack can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.