MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

Nearby Permits

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

Checks passed
15 / 22

0 failed · 7 not measured

Median response
486 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
6

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
103
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 477 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name nearby-permits.

  • Pass
    Lists tools

    tools/list returned 6 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 486 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 493 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    17 of 21 parameters have a description (81%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-10-05T18:25:01.147734Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Nearby Permits

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 6

get_permit

Look up one building permit by its city permit number: work, date, status, cost and address.

Discovered
list_cities

List the US cities and counties with building permit data, with each one's slug for the other tools.

Discovered
permits_at_address

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.

Discovered
permits_near

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.

Discovered
recent_permits

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.

Discovered
zoning_requests_near

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected477 ms6
Connected494 ms6