# io.github.chaoz23/king-county-permit-status (remote · permits-api.secondlandings.ai)

Live permit history + status for any King County, WA address, parcel or permit number. Read-only.

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

## Components

- remote · `permits-api.secondlandings.ai`: 81/100 (this document), [markdown](https://verifymcp.io/servers/chaoz23-king-county-permit-status/permits-api.md), [page](https://verifymcp.io/servers/chaoz23-king-county-permit-status/permits-api)

## Channel facts

- Endpoint: `https://permits-api.secondlandings.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 453 tokens (~453/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.chaoz23/king-county-permit-status MCP server?

io.github.chaoz23/king-county-permit-status is a hosted endpoint at https://permits-api.secondlandings.ai/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 chaoz23-king-county-permit-status 'https://permits-api.secondlandings.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chaoz23-king-county-permit-status": {
      "url": "https://permits-api.secondlandings.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chaoz23-king-county-permit-status": {
      "type": "http",
      "url": "https://permits-api.secondlandings.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chaoz23-king-county-permit-status]
url = "https://permits-api.secondlandings.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chaoz23-king-county-permit-status": {
      "type": "remote",
      "url": "https://permits-api.secondlandings.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chaoz23-king-county-permit-status --url 'https://permits-api.secondlandings.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chaoz23-king-county-permit-status:
    url: "https://permits-api.secondlandings.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chaoz23-king-county-permit-status": {
      "Transport": "http",
      "Url": "https://permits-api.secondlandings.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chaoz23-king-county-permit-status -t streamable-http -u 'https://permits-api.secondlandings.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chaoz23-king-county-permit-status": {
      "type": "http",
      "url": "https://permits-api.secondlandings.ai/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-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 75, +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-10-21 (score 74, +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.

## MCP tools (1)

### `king_county_permit_status` (~408 tokens)

King County permit status

Look up building permit history and status for any King County, WA property. Accepts a street address, 10-digit parcel number, or permit number. Live sources: MyBuildingPermit (14 cities + unincorporated King County), Seattle and Bellevue open data, Renton EnerGov, Redmond Civic Access, Shoreline eTRAKiT, Woodinville + King County Accela, Normandy Park and Carnation SmartGov, SeaTac LAMA, WA State L&I (electrical), plus the King County Assessor's issued-permit index for every parcel (covers the 19 cities without a public portal; history only, no status). Jurisdiction is derived from the city-limits polygon, not the mailing city. Returns all matching permits sorted newest-first. Use for due diligence, permit tracking, or verifying contractor pull history.

Input parameters:

- `contractor` (string): Contractor company name (substring) — returns what they have pulled across the MyBuildingPermit cities. Use instead of query.
- `license` (string): WA L&I contractor license number — same search by license. Use instead of query.
- `limit` (integer): Max permits to return (newest first). summary always covers the whole matched set, so start small and raise only if you need the rows.
- `query` (string): One of: street address ('1817 Morris Ave S, Renton WA 98055'), 10-digit parcel number (plain '7222000353' or formatted '722200-0353'), or permit number ('B25000947', 'ADDC21-0275', '23-127651-LP', '6…
- `since` (string): Only permits applied/issued on or after this date (YYYY-MM-DD).
- `types` (array): Case-insensitive substrings matched against each permit's type, e.g. ['electrical', 'mechanical'].

Output parameters:

- `action` (string): found — permits[] is populated; none — no permits found; refine — connection issue, retry; reject — bad input
- `address_resolution` (object): How well the geocoder matched an address query. match_type: point (exact address point), interpolated (number placed along the street; no parcel), street (street only). partial_match is true for anyt…
- `cite_as` (string): One-line attribution string for generated text
- `coverage_note` (string): Contractor searches only: which cities were (and were not) searched
- `errors` (array): Source errors when a search is incomplete; may accompany permits from sources that succeeded.
- `fetched_at` (string): UTC ISO-8601 timestamp of this query; records are live, not cached
- `filters` (object): The limit/since/types that produced this response
- `jurisdiction` (object): Which authority the query was routed to and why. basis: city-limits (geocoded point inside the city's polygon — authoritative), geocoder-city (locator's city, outside King County's polygon layer), ad…
- `message` (string)
- `next_step` (object): Structured twin of separate_portal: the exact follow-up an agent can take. kind=manual_portal_search; reason in no_feed|electrical_only|parcel_resolution_failed|source_incomplete; portal_url (the por…
- `parcel_id` (string|null): County-namespaced parcel id, e.g. 'king:7222000353' or 'pierce:5985002900', when the query was or resolved to a parcel
- `permit_count` (integer): Unique permits found before any since/types filter (= summary.total)
- `permits` (array): Up to `limit` permit records, newest first (applied_date, else issued_date).
- `routing_by_type` (object): Per permit type (building, mechanical_plumbing, electrical, land_use, engineering_row, fire, grading, septic) for the resolved jurisdiction: {system, portal, live, note}. live=true means that system…
- `searched` (array): Jurisdictions searched (e.g. ['King County', 'Renton (EnerGov)']).
- `separate_portal` (object): Present when manual follow-up at a city portal is needed, including when a live city search is incomplete. Includes city, portal URL, note.
- `summary` (object): Computed over every permit matching since/types (not just the returned rows): total, matched, returned, truncated, open, closed, status_unknown, open_basis_counts {finaled_date, status-vocabulary} (h…
- `trust_level` (string): live — every applicable source answered; partial — a source errored or hit its result cap (see errors); fallback — nothing searchable, use next_step. A city needing manual follow-up (next_step) does…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chaoz23-king-county-permit-status/permits-api#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-11: 70

## Common questions

### What is the io.github.chaoz23/king-county-permit-status MCP server?

io.github.chaoz23/king-county-permit-status is an MCP server listed in the public MCP registry as io.github.chaoz23/king-county-permit-status. Live permit history + status for any King County, WA address, parcel or permit number. Read-only. This page covers its hosted endpoint (https://permits-api.secondlandings.ai/mcp).

### Is the io.github.chaoz23/king-county-permit-status MCP server safe to use?

io.github.chaoz23/king-county-permit-status scores 81 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 io.github.chaoz23/king-county-permit-status MCP server expose?

io.github.chaoz23/king-county-permit-status exposes 1 tool: king_county_permit_status. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.

### Does the io.github.chaoz23/king-county-permit-status MCP server require authentication?

No. We connected to io.github.chaoz23/king-county-permit-status without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.chaoz23/king-county-permit-status MCP server still maintained?

io.github.chaoz23/king-county-permit-status 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://permits-api.secondlandings.ai/mcp
- Repository: https://github.com/chaoz23/king-county-permit-status
- Changelog RSS feed: https://verifymcp.io/servers/chaoz23-king-county-permit-status/permits-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/chaoz23-king-county-permit-status/permits-api.json
- HTML version of this page: https://verifymcp.io/servers/chaoz23-king-county-permit-status/permits-api