Remote MCP · Endpoint

com.entitysearchhq/site MCP server

No. com.entitysearchhq/site answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://entitysearchhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.entitysearchhq/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
545 ms
Tools exposed
10 tools
Uptime, last 30 days
78.9% from 19 checks
Described by its publisher as
EntitySearch HQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
Website
https://entitysearchhq.com/
Listing
From the official MCP registry (active).
Recent checks of com.entitysearchhq/site
CheckedResultHandshake
1 hour agoHandshake completed545 ms
18 hours agoHandshake completed755 ms
2 days agoHandshake completed508 ms
3 days agoHandshake completed706 ms
4 days agoHandshake completed1.15 s
5 days agoHandshake completed1.02 s
6 days agoHandshake completed1.22 s
7 days agoHandshake completed1.33 s
10 days agoHandshake completed512 ms
13 days agoHandshake completed1.85 s
15 days agoHandshake completed921 ms
17 days agoFailed - the check failed for an unclassified reason—
19 days agoFailed - the check failed for an unclassified reason—
21 days agoHandshake completed589 ms
23 days agoHandshake completed1.16 s
25 days agoHandshake completed652 ms
27 days agoFailed - the check failed for an unclassified reason—
28 days agoHandshake completed829 ms
29 days agoFailed - the check failed for an unclassified reason—

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

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