Remote MCP · Endpoint

Close API MCP server

No. Close API answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://mcp.close.city/mcp

The last check completed an MCP handshake.

Registry name
city.close/close-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Walk, bike, and transit travel times from every US census block to nearby amenities.
Listing
From the official MCP registry (active).
Recent checks of Close API
CheckedResultHandshake
9 hours agoHandshake completed55 ms
2 days agoHandshake completed53 ms
4 days agoHandshake completed42 ms
5 days agoHandshake completed44 ms
7 days agoHandshake completed77 ms
8 days agoHandshake completed264 ms
9 days agoHandshake completed288 ms
12 days agoHandshake completed43 ms
14 days agoHandshake completed40 ms
15 days agoHandshake completed456 ms
16 days agoHandshake completed39 ms
18 days agoHandshake completed35 ms
19 days agoHandshake completed34 ms
19 days agoHandshake completed43 ms
20 days agoHandshake completed45 ms
21 days agoHandshake completed91 ms
23 days agoHandshake completed32 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Close API and makes no claim about it beyond what these checks measured.