Remote MCP · Endpoint

dev.fly.solidus-x402/solidus MCP server

No. dev.fly.solidus-x402/solidus answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://solidus-mcp.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.fly.solidus-x402/solidus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
211 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Solana pre-trade safety for agents: rug check, honeypot sell-sim, drainer scan, tx preflight.
Listing
From the official MCP registry (active).
Recent checks of dev.fly.solidus-x402/solidus
CheckedResultHandshake
1 hour agoHandshake completed211 ms
2 days agoHandshake completed226 ms
4 days agoHandshake completed120 ms
5 days agoHandshake completed123 ms
7 days agoHandshake completed130 ms
8 days agoHandshake completed3.63 s
9 days agoHandshake completed4.54 s
12 days agoHandshake completed4.04 s
13 days agoHandshake completed225 ms
15 days agoHandshake completed115 ms
16 days agoHandshake completed121 ms
18 days agoHandshake completed144 ms
19 days agoHandshake completed118 ms
20 days agoHandshake completed3.96 s
20 days agoHandshake completed200 ms
21 days agoHandshake completed133 ms
22 days agoHandshake completed201 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with dev.fly.solidus-x402/solidus and makes no claim about it beyond what these checks measured.