Remote MCP · Endpoint

Close Knit MCP server

No. Close Knit answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://getcloseknit.com/mcp

The last check completed an MCP handshake.

Registry name
com.getcloseknit/close-knit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
268 ms
Tools exposed
18 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Neighbourhood and home evidence for England, London in depth: prices, rents, schools, crime, travel.
Listing
From the official MCP registry (active).
Recent checks of Close Knit
CheckedResultHandshake
39 minutes agoHandshake completed268 ms
3 days agoHandshake completed335 ms
13 days agoHandshake completed282 ms
13 days agoHandshake completed263 ms
15 days agoHandshake completed285 ms
16 days agoFailed - the connection was refused or dropped—
17 days agoHandshake completed255 ms
18 days agoHandshake completed254 ms
18 days agoHandshake completed345 ms
20 days agoHandshake completed252 ms
22 days agoHandshake completed254 ms
25 days agoHandshake completed716 ms
27 days agoHandshake completed257 ms

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

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 Knit and makes no claim about it beyond what these checks measured.