Close API
REMOTE · MCP.CLOSE.CITY · SCANNED SEP 20
Walk, bike, and transit travel times from every US census block to nearby amenities.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1260 tokens (~126/item across 10 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Close API MCP server?
Close API is a hosted endpoint at https://mcp.close.city/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 · mcp.close.city
claude mcp add --transport http city-close-close-api 'https://mcp.close.city/mcp'
{
"mcpServers": {
"city-close-close-api": {
"url": "https://mcp.close.city/mcp"
}
}
} {
"servers": {
"city-close-close-api": {
"type": "http",
"url": "https://mcp.close.city/mcp"
}
}
} [mcp_servers.city-close-close-api] url = "https://mcp.close.city/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"city-close-close-api": {
"type": "remote",
"url": "https://mcp.close.city/mcp",
"enabled": true
}
}
} openclaw mcp add city-close-close-api --url 'https://mcp.close.city/mcp' --transport streamable-http
mcp_servers:
city-close-close-api:
url: "https://mcp.close.city/mcp" {
"McpServers": {
"city-close-close-api": {
"Transport": "http",
"Url": "https://mcp.close.city/mcp"
}
}
} assistant mcp add city-close-close-api -t streamable-http -u 'https://mcp.close.city/mcp'
{
"mcpServers": {
"city-close-close-api": {
"type": "http",
"url": "https://mcp.close.city/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://mcp.close.city/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=close.city | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fff37514c498bda30e41ea15648318cd |
| SANs: close.city, mcp.close.city, *.mcp.close.city | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.close.city. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| city. | present | 32800 | 8 | Verified |
| close.city. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.close.city/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.close.city/mcp | HTTPS enforced | 301 | https://mcp.close.city/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 →
blocks_in_area ~163
Per-block travel times for every census block in an area (metered: 1 token per returned row). Give place_geoid (from find_place) for a whole city, or center {lat, lon} + radius_m. Rows carry a numeric mode_id.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Circle centre latitude (with lon + radius_m). |
| limit | integer | – | Max rows (first page). |
| lon | number | – | Circle centre longitude. |
| mode | string | – | walk, bike, or transit. |
| place_geoid | string | – | Census place GEOID (a whole city/town). |
| radius_m | number | – | Circle radius in metres (<=28000). |
| type | integer | – | Destination type id (see get_catalog). |
No output schema declared.
No examples provided.
find_place ~91
Look up a US city or town by name (free, no key). Returns matches with their census place GEOID and centre point (lon/lat). The entry point: feed a GEOID to blocks_in_area, or a centre to walkability_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches (1-20). |
| query | string | yes | City or town name, e.g. 'Providence'. |
No output schema declared.
No examples provided.
get_catalog ~52
List the travel modes and the destination-type taxonomy (free, no key). Use it to resolve type names to the numeric ids the other tools take. Modes are walk, bike, transit — there is no drive mode.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_balance ~38
Check the token balance of the API key in use, without spending any tokens. Works even at a zero balance. Requires the Authorization bearer key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
isochrone ~151
The area reachable from a location within a time budget, as GeoJSON contours (metered: 10 tokens per contour). Give block_geoid or lat+lon. Defaults to a single 30-minute contour; ask for more only when needed (bodies can be large).
| Name | Type | Req | Description |
|---|---|---|---|
| block_geoid | string | – | – |
| contours | array | – | Up to four ascending thresholds, instead of minutes. |
| direction | string | – | 'from' the origin (default) or 'to' it. |
| lat | number | – | – |
| lon | number | – | – |
| minutes | integer | – | A single threshold (1-60). |
| mode | string | – | walk, bike, or transit. |
No output schema declared.
No examples provided.
join_close_plus ~97
Get a Stripe Checkout URL for the Close+ membership ($10/month: 5,000 API tokens granted monthly plus member features on the close.city map). The user pays in their own browser: give them the returned URL and stop. Needs a fresh six-digit code from request_sign_in, read by the user from their own inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The six-digit code from the email. |
| string | yes | – |
No output schema declared.
No examples provided.
nearby_pois ~243
Nearby points of interest and the travel time to each, from a location (metered: 1 token per returned row). One origin: block_geoid or lat+lon; keep limit small to control spend and context size. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, rows tagged by origin, no limit/pagination, so filter with type/mode/max_minutes. Batching saves requests and context, not tokens: it still charges per row. A non-empty truncated (+ truncated_reason) means the balance or row budget cut the batch short.
| Name | Type | Req | Description |
|---|---|---|---|
| block_geoid | string | – | – |
| block_geoids | array | – | Many block GEOIDs — one batch call. |
| lat | number | – | – |
| limit | integer | – | Max rows (first page). |
| lon | number | – | – |
| max_minutes | integer | – | Upper bound on travel time (<=30). |
| mode | string | – | walk, bike, or transit. |
| points | array | – | Many lat/lon points — one batch call. |
| type | integer | – | Destination type id (see get_catalog). |
No output schema declared.
No examples provided.
redeem_code ~92
Complete sign-up with the six-digit code the user received, and return a new API key (shown once). Call request_sign_in first. The key grants 5,000 free tokens; store it and pass it as the Authorization bearer on future calls.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The six-digit code from the email. |
| string | yes | – | |
| label | string | – | Optional label for the key. |
No output schema declared.
No examples provided.
request_sign_in ~77
Start free sign-up for the user: email them a six-digit code. The user must read the code from their own inbox and give it to you, then call redeem_code. This is how an agent gets the user an API key (5,000 free tokens, no card).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address. |
No output schema declared.
No examples provided.
walkability_summary ~204
Fastest travel time from a location to each destination category, by mode (metered: 1 token per returned row). One origin: block_geoid or lat+lon. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, with rows tagged by origin. Batching saves requests and context, not tokens: it still charges per row. A non-empty truncated (+ truncated_reason) means the balance or row budget cut the batch short. A missing category means it is not reachable within 30 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| block_geoid | string | – | 15-digit census block GEOID. |
| block_geoids | array | – | Many block GEOIDs — one batch call. |
| lat | number | – | – |
| lon | number | – | – |
| mode | string | – | walk, bike, or transit. Omit for all three. |
| points | array | – | Many lat/lon points — one batch call. |
No output schema declared.
No examples provided.
What is the Close API MCP server?
Close API is an MCP server listed in the public MCP registry as city.close/close-api. Walk, bike, and transit travel times from every US census block to nearby amenities. This page covers its hosted endpoint (https://mcp.close.city/mcp).
Is the Close API MCP server safe to use?
Close API scores 76 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 Close API MCP server expose?
Close API exposes 10 tools: find_place, get_catalog, walkability_summary, nearby_pois, isochrone, and 5 more. Their descriptions and schemas cost roughly 1,208 tokens of context every time the server is loaded.
Does the Close API MCP server require authentication?
No. We connected to Close API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Close API MCP server still maintained?
Close API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.