Remote MCP · Endpoint

Signo MCP server

No. Signo answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://app.signo.fi/api/mcp

The last check completed an MCP handshake.

Registry name
fi.signo/signo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
282 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI agents that watch DeFi positions: read a wallet report, draft agents for the owner to sign.
Listing
From the official MCP registry (active).
Recent checks of Signo
CheckedResultHandshake
53 minutes agoHandshake completed282 ms
3 days agoHandshake completed88 ms
12 days agoHandshake completed175 ms
13 days agoHandshake completed156 ms
15 days agoHandshake completed246 ms
15 days agoHandshake completed99 ms
17 days agoHandshake completed149 ms
18 days agoHandshake completed90 ms
18 days agoHandshake completed125 ms
20 days agoHandshake completed205 ms
22 days agoHandshake completed113 ms
25 days agoHandshake completed87 ms
27 days agoHandshake completed194 ms
29 days agoHandshake completed210 ms

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

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