Remote MCP · Endpoint

Quidli Connect MCP server

No. Quidli Connect answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.connect.quid.li/

The last check completed an MCP handshake.

Registry name
io.github.Quidli/connect-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Resolve social handles to wallets, score onchain reputation, pay in any ERC-20, SPL or native.
Listing
From the official MCP registry (active).
Recent checks of Quidli Connect
CheckedResultHandshake
1 hour agoHandshake completed66 ms
8 days agoHandshake completed69 ms
9 days agoHandshake completed72 ms
11 days agoHandshake completed70 ms
12 days agoHandshake completed64 ms
13 days agoHandshake completed67 ms
14 days agoHandshake completed74 ms
14 days agoHandshake completed264 ms
16 days agoHandshake completed148 ms
19 days agoHandshake completed70 ms
21 days agoHandshake completed93 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed64 ms
28 days agoHandshake completed74 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 Quidli Connect and makes no claim about it beyond what these checks measured.