Nearby Permits
REMOTE · NEARBYPERMITS.COM
Building permits by address for a growing list of US cities and counties, from city open data.
Available components
Last scanned (22 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 24 Oct 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1168 tokens (~194/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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
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 7 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.
- 24 Oct 26 0
- Tool “permits_at_address” rewrote its description, which is the text the model reads security
- Tool “permits_near” rewrote its description, which is the text the model reads security
- 23 Oct 26 +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.
- 20 Oct 26 +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.
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Oct 2026 · Probed https://nearbypermits.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nearbypermits.com | CN=YR1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 2048 | SHA256-RSA | 6d19c78e2a09106695b33f0fd0c583779dc |
| SANs: nearbypermits.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nearbypermits.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nearbypermits.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self' https://places.googleapis.com; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nearbypermits.com/mcp | Verified | 200 | |
| http (plaintext) | http://nearbypermits.com/mcp | HTTPS enforced | 308 | https://nearbypermits.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_permit Look up a permit number ~45
Look up one building permit by its city permit number: work, date, status, cost and address.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| permit_id | string | yes | – |
No output schema declared.
No examples provided.
list_cities List supported cities ~29
List the US cities and counties with building permit data, with each one's slug for the other tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
permits_at_address Permits at an address ~406
Use this tool when someone asks which building, remodeling or demolition permits exist at an address, whether a house had permitted work, or what is permitted next door. It returns the building permits on record at that street address in a supported city or county (Los Angeles, New York City, Chicago, San Francisco, Seattle, Austin, Cincinnati, Mesa, New Orleans, Fort Worth, Columbus, San Diego, Detroit, Nashville, Raleigh, Phoenix, San Antonio, Minneapolis, Montgomery County, Boston, Pittsburgh, Washington, Denver, Los Angeles County, Wake County, Miami, Miami-Dade County, Hillsborough County, Cape Coral, Port St. Lucie, Alachua County, Kansas City, Baltimore, Sacramento County, Memphis, Las Vegas, Tacoma, Boulder, Cambridge, Somerville, Marin County, Pierce County, Cary, Cleveland, Arlington, Naperville, Tempe, Anaheim, Riverside), newest first and at most 200: type of work, description, date, status and reported cost, from city and county open data checked around the clock. count is how many are listed; when capped is true there are more, and total gives the city's full count when it was read (else null). history_limited means the city's full history didn't load, so the list is our copy only. The address can be typed loosely (a missing N or S, "Drive" for "Dr", a trailing city, state or ZIP, a unit): it is matched to the spelling the city files. When more than one address matches (N and S Holly Dr), the answer lists them in did_you_mean; ask which one is meant and call again with it.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address with house number, e.g. '867 N Iliff St'. New York: include the borough, e.g. '180 West Street, Brooklyn'. |
| city | string | yes | City slug, e.g. los-angeles, new-york, chicago |
No output schema declared.
No examples provided.
permits_near Permits near an address or a point ~318
Use this tool when someone asks what is being built near an address or a place: new buildings next door, construction on the block, what's permitted around a home they might buy or rent. Give a city and street address, or a latitude and longitude. The tool returns building permits within a radius (default 400 meters, about a quarter mile) issued since a date (default about six months back), newest first, each with distance in meters and compass direction from the point. It covers the last 24 months of city open data. counts.total is exact even when the list is capped (null if the count failed). It matches a loosely typed address the same way permits_at_address does. If more than one address matches, the answer has found set to false and lists the addresses in did_you_mean.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with house number, e.g. '2443 W Warren Blvd'. |
| city | string | – | City slug, e.g. chicago. Needed with address; optional with lat and lon. |
| lat | number | – | Latitude, used instead of city and address. |
| limit | integer | – | Most permits to list, default 50. |
| lon | number | – | Longitude, used instead of city and address. |
| radius_m | integer | – | Radius in meters, default 400. |
| since | string | – | Earliest date, YYYY-MM-DD, or 6m, 1y, 2y. Default 6m (the first of the month five months back). |
No output schema declared.
No examples provided.
recent_permits Newest permits in an area ~68
Use when someone asks what is being built in their neighborhood or ZIP code. Returns the newest building permits in a supported city or county, optionally within one ZIP code.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| limit | integer | – | – |
| zip | string | – | 5-digit ZIP code |
No output schema declared.
No examples provided.
zoning_requests_near Zoning requests near an address or a point ~285
Use when someone asks about variances, conditional uses, rezonings or zoning appeals near an address: what a neighbor asked the city for, or whether a hearing is coming up. Covers Boston, Washington DC, San Francisco and Seattle. Give a city and street address, or a latitude and longitude. Each case has the city's own status words, our plain status label (Filed, In review, Hearing scheduled, Approved, Approved with conditions, Denied, Withdrawn or Other), the hearing date when the city publishes one, and a link to the city's case record. We never infer an outcome the city's record doesn't state. Owner and applicant names are left out.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with house number, e.g. '78 Pearl St'. |
| city | string | – | boston, washington-dc, san-francisco or seattle. Needed with address. |
| lat | number | – | Latitude, used instead of city and address. |
| limit | integer | – | Most cases to list, default 50. |
| lon | number | – | Longitude, used instead of city and address. |
| radius_m | integer | – | Radius in meters, default 400. |
| since | string | – | Earliest filing, hearing or decision date, YYYY-MM-DD, or 6m, 1y, 2y. Default 1y. |
No output schema declared.
No examples provided.
How do I install the Nearby Permits MCP server?
Nearby Permits is a hosted endpoint at https://nearbypermits.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 · nearbypermits.com
claude mcp add --transport http com-nearbypermits-permits 'https://nearbypermits.com/mcp'
What is the Nearby Permits MCP server?
Nearby Permits is an MCP server listed in the public MCP registry as com.nearbypermits/permits. Building permits by address for a growing list of US cities and counties, from city open data. This page covers its hosted endpoint (https://nearbypermits.com/mcp).
Is the Nearby Permits MCP server safe to use?
Nearby Permits 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 Nearby Permits MCP server expose?
Nearby Permits exposes 6 tools: list_cities, permits_at_address, permits_near, get_permit, recent_permits, zoning_requests_near. Their descriptions and schemas cost roughly 1,151 tokens of context every time the server is loaded.
Does the Nearby Permits MCP server require authentication?
No. We connected to Nearby Permits without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nearby Permits MCP server still maintained?
Nearby Permits is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.