Nearby Permits

by nearbypermits.com · remote · no sign-in to list tools · v0.1.1 · published by com.nearbypermits

Building permits by address for a growing list of US cities and counties, from city open data.

Changes · 4

Compare Registry entry

6 tools: 4 change things and 2 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone0Claude Code: ask
Changes things4Claude Code: ask: see these tools
Only reads2Claude Code: allow: see these tools

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http permits https://nearbypermits.com/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn

Warnzoning_requests_near
The server marks "zoning_requests_near" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "zoning_requests_near" says "request": a word for a change.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 4Creates or changes something that can be changed back.Claude Code: ask

permits_at_addressUse 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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 every building permit 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): type of work, description, date, status and reported cost, from city and county open data checked around the clock. 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
permits_nearUse 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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. 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
recent_permitsUse when someone asks what is being built in their neighborhood or ZIP code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
zoning_requests_nearUse 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.1 finding
Why it is in this group
- The name "zoning_requests_near" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "zoning_requests_near" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "zoning_requests_near" says "request": a word for a change.
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true

Only reads 2Looks things up and changes nothing.Claude Code: allow

get_permitLook up one building permit by its city permit number: work, date, status, cost and address.No findings
Why it is in this group
- The name "get_permit" says "get": a word for reading.
Description, as the server wrote it
Look up one building permit by its city permit number: work, date, status, cost and address.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_citiesList the US cities and counties with building permit data, with each one's slug for the other tools.No findings
Why it is in this group
- The name "list_cities" says "list": a word for reading.
Description, as the server wrote it
List the US cities and counties with building permit data, with each one's slug for the other tools.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http permits https://nearbypermits.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__permits__list_cities",
      "mcp__permits__get_permit"
    ],
    "ask": [
      "mcp__permits__permits_at_address",
      "mcp__permits__permits_near",
      "mcp__permits__recent_permits",
      "mcp__permits__zoning_requests_near"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as permits. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.nearbypermits/permits/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.

For agents: Markdown · JSON · report this listing