# PermitStack (remote · mcp.permit-stack.com)

U.S. building permits, permit histories by address and contractors from city and county records.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.permit-stack.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-permit-stack-permits/mcp.md), [page](https://verifymcp.io/servers/com-permit-stack-permits/mcp)

## Channel facts

- Endpoint: `https://mcp.permit-stack.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-permit-stack-permits 'https://mcp.permit-stack.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-permit-stack-permits": {
      "url": "https://mcp.permit-stack.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-permit-stack-permits": {
      "type": "http",
      "url": "https://mcp.permit-stack.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-permit-stack-permits]
url = "https://mcp.permit-stack.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-permit-stack-permits": {
      "type": "remote",
      "url": "https://mcp.permit-stack.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-permit-stack-permits --url 'https://mcp.permit-stack.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-permit-stack-permits:
    url: "https://mcp.permit-stack.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-permit-stack-permits": {
      "Transport": "http",
      "Url": "https://mcp.permit-stack.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-permit-stack-permits -t streamable-http -u 'https://mcp.permit-stack.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-permit-stack-permits": {
      "type": "http",
      "url": "https://mcp.permit-stack.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +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.

### 2026-11-02 (score 82, +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.

### 2026-10-31 (score 81, +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.

### 2026-10-29 (score 80, +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.

### 2026-10-27 (score 79, +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.

### 2026-10-25 (score 78, +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.

### 2026-10-24 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 77)

First indexed and scored.

## MCP tools (6)

### `search_permits` (~774 tokens)

Search building 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 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.

Input parameters:

- `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

### `get_permit` (~199 tokens)

Look up a permit by number

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.

Input parameters:

- `city` (string): City where the permit was issued (optional, narrows the match)
- `permit_number` (string, required): The permit number from the issuing jurisdiction
- `state` (string): Two-letter state code (optional, narrows the match)

### `get_property_history` (~301 tokens)

Property permit 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 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.

Input parameters:

- `address` (string, required): 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)

### `search_contractors` (~249 tokens)

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, 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.

Input parameters:

- `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

### `get_contractor_permits` (~157 tokens)

Contractor's 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 name, owner mailing address or permit applicant name fields.

Input parameters:

- `contractor_id` (string, required): 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`)

### `get_coverage` (~129 tokens)

Data 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 permit held), filterable by state and by name, up to 25 per call, largest first. Without sign-in it returns the platform totals only.

Input parameters:

- `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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-permit-stack-permits/mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77

## Common questions

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.permit-stack.com/mcp
- Website: https://permit-stack.com/docs/connectors/
- Changelog RSS feed: https://verifymcp.io/servers/com-permit-stack-permits/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-permit-stack-permits/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-permit-stack-permits/mcp