Remote MCP · Endpoint

co.heyspark.mcp/server MCP server

No. co.heyspark.mcp/server answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.heyspark.co/mcp

The last check completed an MCP handshake.

Registry name
co.heyspark.mcp/server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and discover local businesses. 30+ categories with verified contact info, hours, and reviews.
Repository
https://github.com/jhibird/HeySpark-MCP
Listing
From the official MCP registry (active).
Recent checks of co.heyspark.mcp/server
CheckedResultHandshake
6 hours agoHandshake completed86 ms
2 days agoHandshake completed51 ms
4 days agoHandshake completed26 ms
5 days agoHandshake completed34 ms
7 days agoHandshake completed116 ms
8 days agoHandshake completed79 ms
9 days agoHandshake completed33 ms
12 days agoHandshake completed73 ms
13 days agoHandshake completed29 ms
15 days agoHandshake completed70 ms
16 days agoHandshake completed29 ms
17 days agoHandshake completed29 ms
18 days agoHandshake completed28 ms
19 days agoHandshake completed48 ms
20 days agoHandshake completed64 ms
21 days agoHandshake completed24 ms
22 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with co.heyspark.mcp/server and makes no claim about it beyond what these checks measured.