Remote MCP · Endpoint

Nearwick business directory MCP server

No. Nearwick business directory answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://nearwick.com/mcp

The last check completed an MCP handshake.

Registry name
com.nearwick/nearwick
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Businesses in every country, each with dated facts and no ratings. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Nearwick business directory
CheckedResultHandshake
2 hours agoHandshake completed114 ms
2 days agoHandshake completed114 ms
4 days agoHandshake completed102 ms
6 days agoHandshake completed134 ms
8 days agoHandshake completed140 ms
9 days agoHandshake completed107 ms
11 days agoHandshake completed151 ms
11 days agoHandshake completed104 ms
14 days agoHandshake completed101 ms
15 days agoHandshake completed109 ms
17 days agoHandshake completed87 ms
19 days agoHandshake completed89 ms
20 days agoHandshake completed88 ms
21 days agoHandshake completed102 ms
22 days agoHandshake completed106 ms

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

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