Remote MCP · Endpoint

SignOps MCP server

No. SignOps answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.signops.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.signops/signops
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
138 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Send push to Android, iOS and the web, and ask a trusted phone to approve a login, from your agent.
Listing
From the official MCP registry (active).
Recent checks of SignOps
CheckedResultHandshake
7 hours agoHandshake completed138 ms
4 days agoHandshake completed795 ms
14 days agoHandshake completed236 ms
15 days agoHandshake completed177 ms
15 days agoHandshake completed139 ms
17 days agoHandshake completed113 ms
18 days agoHandshake completed192 ms
19 days agoHandshake completed104 ms
20 days agoHandshake completed116 ms
21 days agoHandshake completed55 ms
23 days agoHandshake completed116 ms
26 days agoHandshake completed225 ms

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

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