Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Live permit history + status for any King County, WA address, parcel or permit number. Read-only.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://permits-api.secondlandings.ai/mcpFühre das in deinem Terminal aus
claude mcp add --transport http king-county-permit-status https://permits-api.secondlandings.ai/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"king-county-permit-status": {
"url": "https://permits-api.secondlandings.ai/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"king-county-permit-status": {
"type": "http",
"url": "https://permits-api.secondlandings.ai/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://permits-api.secondlandings.ai/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto chaoz23 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.0.0) kam vor 29 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Tool Guardian
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Too many MCP servers eating your context? A router that loads each tool's schema only when needed.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Look up building permit history and status across King County, WA jurisdictions — county-level permits (septic, critical areas, grading) and city-level permits (building, mechanical, electrical) can all apply to the same address. Coverage is live where a jurisdiction offers an open permit feed, and falls back to the correct municipal portal link everywhere else.
Coverage today: 🟢 20/39 cities live (status + history) · 🟠 19/39 indexed (issued-permit history from the King County Assessor; current status needs the city portal, which next_step names) · plus unincorporated King County. See the coverage scorecard below for the per-city breakdown.
python3 lookup.py "27927 E Main St" # by address
python3 lookup.py "7222000353" # by parcel number python3 lookup.py "B25000947" # by permit number python3 lookup.py "23-127651-LP" # Bellevue permit number python3 lookup.py "6145915-CN" # Seattle SDCI permit number python3 lookup.py --pipe "27927 E Main St" # agent pipeline mode python3 lookup.py --limit 10 --since 2020-01-01 --type electrical "27927 E Main St" # shape: newest 10 electrical since 2020 python3 lookup.py --all "27927 E Main St" # every permit (default is the 50 newest + a summary of all) python3 lookup.py --schema # print tool definition
The same lookup is served read-only, no auth, from permits-api.secondlandings.ai (server.py, zero dependencies; see deploy/README.md):
| MCP (Streamable HTTP) | POST https://permits-api.secondlandings.ai/mcp — tool king_county_permit_status, arg query |
| REST | GET https://permits-api.secondlandings.ai/api/lookup?q=1817+Morris+Ave+S,+Renton+WA — optional limit, since=YYYY-MM-DD, types=electrical,mechanical |
| Vendor map | /vendor-map (and /vendor-map.json) — which permitting system each of the 39 cities runs, how it is queried or why it can't be, electrical authority, per-type routing; generated from the adapter config (scripts/gen_vendor_map.py, also in docs/vendor-map.md) |
| OpenAPI 3.1 (typed) | /openapi.json · agent orientation /llms.txt · CLI definition /tool.json · /healthz |
Results are live; the server caches each query for 15 minutes and rate-limits per client (30/min) to protect the municipal portals. Known hosted-only gap: Tyler's hosted Civic Access (Redmond) returns 403 to datacenter IPs, so from the hosted endpoint a Redmond lookup carries the Assessor index plus a next_step with reason: source_blocked instead of live Redmond records; run lookup.py locally for those. Every other source answers from the droplet. Run it yourself with python3 server.py or docker compose up — server.json is the MCP Registry manifest.
Parcel-number searches query every supported MyBuildingPermit and live city portal because a bare parcel number does not identify its city jurisdiction.
Address searches are routed by geometry, not the mailing city: the address is geocoded with King County's four-county locator and the point is tested against the city-limits polygons. A "Kent, WA" address that sits in unincorporated King County is searched as county, not Kent; an address with no city in it is routed correctly instead of fanning out to every jurisdiction; and Pierce-side addresses of Milton/Pacific/Auburn get a pierce: parcel id. The mailing city is only used when geocoding fails (jurisdiction.basis says which).
{
"action": "found", "permit_count": 2, "searched": ["Renton (EnerGov)"], "permits": [ { "permit_number": "E26000458", "type": "Residential Electrical Permit", "status": "Issued", "description": "Electrical Work (Garage & Garage Exterior): ...", "address": "1817 Morris Ave S Renton WA 98055", "jurisdiction": "Renton", "applied_date": "2026-01-28", "issued_date": "2026-01-28", "finaled_date": null, "expires_date": "2027-07-27", "portal": "https://permitting.rentonwa.gov", "record_url": null, "is_open": true } ], "trust_level": "live", "fetched_at": "2026-10-08T19:02:11+00:00", "parcel_id": "king:7222000353", "cite_as": "King County Permit Status (github.com/chaoz23/king-county-permit-status), queried 2026-10-08 via Renton (EnerGov)" }
| Field | Description |
|---|---|
action | found (permits returned), none (no matches), refine (connection issue) |
permit_count | Unique permits found before any filter (= summary.total) |
summary | Answer from this first. Computed over every permit matching since/types, not just the returned rows: total, matched, returned, truncated, open, closed, status_unknown, by_type, by_status, by_year, years [oldest, newest], latest |
permits | Up to limit records (default 50), newest first — a 356-permit commercial parcel is ~56k tokens unshaped; the summary carries the whole picture |
filters | The limit / since / types that produced this response |
searched | Which jurisdictions were searched |
separate_portal | If the city has an unsupported portal: city name + URL + prose note |
next_step | Structured twin of separate_portal for agents: kind: manual_portal_search, reason (no_feed / electrical_only / parcel_resolution_failed / source_incomplete / source_blocked — the city's live system refused this client with 403), portal_url (the portal's actual search page when known — PermitTrax, LAMA, OpenGov, Kent), vendor, search_by (inputs that page accepts; empty when login-gated), query, query_type, covers_electrical, hint |
errors | Source errors when a search is incomplete; may accompany permits from successful sources |
trust_level | live (every applicable source answered), partial (a source errored or hit its result cap — see errors), fallback (nothing searchable). A city that needs a manual portal visit (next_step) is a scope fact, not distrust, and no longer lowers this |
fetched_at | UTC timestamp of the query — records are live, never cached |
parcel_id | County-namespaced parcel, e.g. king:7222000353 or pierce:5985002900, when the query was or resolved to a parcel |
jurisdiction | Where the query was routed and why: city, basis (city-limits = the geocoded point falls inside that city's polygon — authoritative; geocoder-city; address-text = the mailing city in the query, used only when geocoding fails), county, unincorporated (true → county permits only, even if the mailing city says "Kent") |
routing_by_type | Where each kind of permit lives for the resolved place — building, mechanical_plumbing, electrical, land_use, engineering_row, fire, grading, septic → {system, portal, live, note}. live: true means this tool searched that system; otherwise portal is where to look (e.g. septic is always King County Public Health; electrical is L&I unless the city self-runs it) |
address_resolution | How well the geocoder matched an address: matched_address, score, match_type (point = exact address point; interpolated = number placed along the street; street), partial_match, street_number_snapped, parcel_basis (address-point, parcel-polygon, or nearby-parcel when the PIN came from the parcel layer under/near an interpolated point — then candidate_parcels lists the alternatives) |
cite_as | One-line attribution string for generated text |
Per permit: permit_number, type, status, is_open (heuristic, census-tested weekly; null when the source exposes no status) with is_open_basis (finaled_date = certain, status-vocabulary = regex over the vendor's status word, null = unknown), description, address, jurisdiction, applied_date, issued_date, finaled_date, expires_date, portal, record_url (the specific record's URL when the source exposes one).
| Source | Cities / scope |
|---|---|
| MyBuildingPermit.com | Auburn, Bellevue, Bothell, Burien, Edmonds, Federal Way, Issaquah, Kenmore, King County (unincorporated), Kirkland, Mercer Island, Mill Creek, Newcastle, Sammamish, Snoqualmie |
| Bellevue Open Data (live ArcGIS API) | Daily Bellevue permit snapshot (1998+) for address, parcel, and permit-number searches |
| Seattle Open Data (live Socrata APIs) | Building, electrical, trade, and land-use permits for Seattle address and permit-number searches; parcel-number queries reach it through the Assessor's site address (the datasets have no parcel column) |
| Renton EnerGov (live API) | All Renton permit types including electrical |
| Redmond EnerGov Civic Access (live API) | All Redmond permit types including electrical, for address, parcel, and permit-number searches |
| Accela Citizen Access (live) | Woodinville, and King County's own agency for unincorporated addresses (older history, enforcement and electrical records that MyBuildingPermit lacks), for address, parcel, and permit-number searches |
| SmartGov (live) | Normandy Park and Carnation, for address, parcel, and permit-number searches |
| King County Assessor parcel index | Issued-permit history (number, type, description, issue date, value, issuing city) for every King County parcel — the only source for the 19 cities without a public portal. It is what cities report for *valuation*: building/remodel/addition permits (some electrical), dense since ~2023 and thin before, back to the late 1990s; never trade sub-permits or inspections, and no status. Address queries use the geocoded parcel, parcel queries use it directly |
| LAMA (live) | SeaTac, for address and permit-number searches (incl. SeaTac's self-run electrical; parcel search not offered by the portal; capped at 200 newest per query) |
| Shoreline eTRAKiT (live) | Building, mechanical/plumbing, and land-use permits for Shoreline address, parcel, and permit-number searches (status/description not exposed by the portal's search) |
| WA State L&I | Electrical permits for cities not handling their own (2020+) |
Auto-generated from routing_data.json (python3 scripts/gen_scorecard.py --write). One row per King County city.
Legend — ✅ live (status + history) · 🗂️ index (valuation-reported building history · the number after ✅/🗂️ in Building is the record count at the city's QC address (see qc_addresses.json) — how much is really behind the row from the King County Assessor's parcel index — no status, no sub-permits, dense since ~2023) · ➖ L&I electrical only (2020+) · ⚠️ gap (city self-runs electrical, not yet integrated)
Health = last weekly live probe of the city's source (scripts/source_health.py, 2026-11-02): ✅ answered with records · ⚪ answered, zero rows for a known-good query · ⛔ blocked (403) · ❌ down · ❔ unchecked · — no live source
| City | Status | Source | Health | Building | Electrical | Mech/Plumb | Land Use |
|---|---|---|---|---|---|---|---|
| Algona | 🟠 Indexed | KC Assessor index | ✅ | 🗂️ index 2 | ➖ L&I | 🗂️ index | 🗂️ index |
| Auburn | 🟢 Live | MyBuildingPermit | ✅ | ✅ 133 | ➖ L&I | ✅ | ✅ |
| Beaux Arts Village | 🟠 Indexed | KC Assessor index | ✅ | 🗂️ index 5 | ➖ L&I | 🗂️ index | 🗂️ index |
| Bellevue | 🟢 Live | Bellevue (Open Data) | ✅ | ✅ 361 | ✅ | ✅ | ✅ |
| Black Diamond | 🟠 Indexed | KC Assessor index | ✅ | 🗂️ index 2 | ➖ L&I | 🗂️ index | 🗂️ index |
| Bothell | 🟢 Live | MyBuildingPermit | ✅ | ✅ 117 | ➖ L&I | ✅ | ✅ |
| Burien | 🟢 Live | MyBuildingPermit | ✅ | ✅ 27 | ✅ | ✅ | ✅ |
| Carnation | 🟢 Live |
Nur der Anfang wird gezeigt; den Rest findest du im Repo