Remote MCP · Endpoint

com.datahyena/signals MCP server

No. com.datahyena/signals answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.datahyena.com/mcp

The last check completed an MCP handshake.

Registry name
com.datahyena/signals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
440 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deduplicated, entity-resolved funding rounds, acquisitions, and exec moves as MCP tools.
Website
https://datahyena.com/mcp
Listing
From the official MCP registry (active).
Recent checks of com.datahyena/signals
CheckedResultHandshake
1 hour agoHandshake completed440 ms
2 days agoHandshake completed444 ms
4 days agoHandshake completed460 ms
5 days agoHandshake completed451 ms
7 days agoHandshake completed164 ms
8 days agoHandshake completed336 ms
9 days agoHandshake completed441 ms
12 days agoHandshake completed446 ms
13 days agoHandshake completed442 ms
15 days agoHandshake completed458 ms
16 days agoHandshake completed142 ms
17 days agoHandshake completed443 ms
18 days agoHandshake completed422 ms
19 days agoHandshake completed432 ms
20 days agoHandshake completed142 ms
21 days agoHandshake completed448 ms
22 days agoHandshake completed141 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 com.datahyena/signals and makes no claim about it beyond what these checks measured.