Remote MCP · Endpoint

sol-defi-desk MCP server

No. sol-defi-desk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://95.216.126.169.sslip.io/mcp

The last check completed an MCP handshake.

Registry name
io.sslip.169.126.216.95/sol-defi-desk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
330 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paid Solana token safety checks over Streamable HTTP MCP (x402 USDC on Solana + Base).
Listing
From the official MCP registry (active).
Recent checks of sol-defi-desk
CheckedResultHandshake
1 hour agoHandshake completed330 ms
2 days agoHandshake completed335 ms
5 days agoHandshake completed418 ms
7 days agoHandshake completed339 ms
9 days agoHandshake completed358 ms
11 days agoHandshake completed439 ms
13 days agoHandshake completed326 ms
15 days agoHandshake completed331 ms
17 days agoHandshake completed325 ms
19 days agoHandshake completed333 ms
20 days agoHandshake completed333 ms
22 days agoHandshake completed337 ms
23 days agoHandshake completed335 ms
25 days agoHandshake completed337 ms

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

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