Remote MCP · Endpoint

SignalDock MCP server

No. SignalDock answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://www.signaldock.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.homeaccount7/signaldock
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
342 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 5 checks
Described by its publisher as
Market reports, earnings history, research, portfolio analysis and read-only Workspace tools.
Listing
From the official MCP registry (active).
Recent checks of SignalDock
CheckedResultHandshake
53 minutes agoHandshake completed342 ms
3 days agoHandshake completed315 ms
12 days agoHandshake completed439 ms
13 days agoHandshake completed556 ms
14 days agoHandshake completed2.23 s

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

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