Remote MCP · Endpoint

com.netentropyscore/coherence-signal MCP server

No. com.netentropyscore/coherence-signal answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.netentropyscore.com/mcp

The last check completed an MCP handshake.

Registry name
com.netentropyscore/coherence-signal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
140 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
A brand's claim (website coherence) vs its reality (recent news), and the divergence.
Listing
From the official MCP registry (active).
Recent checks of com.netentropyscore/coherence-signal
CheckedResultHandshake
1 hour agoHandshake completed140 ms
2 days agoHandshake completed259 ms
4 days agoHandshake completed313 ms
5 days agoHandshake completed289 ms
7 days agoHandshake completed287 ms
8 days agoHandshake completed310 ms
9 days agoHandshake completed187 ms
12 days agoHandshake completed138 ms
13 days agoHandshake completed1.43 s
15 days agoHandshake completed273 ms
16 days agoHandshake completed270 ms
17 days agoHandshake completed271 ms
18 days agoHandshake completed296 ms
19 days agoHandshake completed114 ms
20 days agoHandshake completed129 ms
21 days agoHandshake completed130 ms
22 days agoHandshake completed198 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.

Listing data comes from the official MCP registry. Glide is not affiliated with com.netentropyscore/coherence-signal and makes no claim about it beyond what these checks measured.