Remote MCP · Endpoint

io.github.arbonomous/curvecall MCP server

No. io.github.arbonomous/curvecall answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://curvecall.onrender.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.arbonomous/curvecall
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
257 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Pay-per-call market math + token intel: USDC Base/Solana + shielded ZEC HTTP, MCP USDC, $0.001-$0.02
Listing
From the official MCP registry (active).
Recent checks of io.github.arbonomous/curvecall
CheckedResultHandshake
52 minutes agoHandshake completed257 ms
2 days agoHandshake completed141 ms
4 days agoHandshake completed323 ms
5 days agoHandshake completed295 ms
7 days agoHandshake completed226 ms
8 days agoHandshake completed153 ms
9 days agoHandshake completed276 ms
12 days agoHandshake completed133 ms
13 days agoHandshake completed141 ms
15 days agoHandshake completed136 ms
17 days agoHandshake completed113 ms
18 days agoHandshake completed295 ms
19 days agoHandshake completed259 ms
20 days agoHandshake completed270 ms
21 days agoHandshake completed138 ms
21 days agoHandshake completed252 ms

The last 16 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.

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 io.github.arbonomous/curvecall and makes no claim about it beyond what these checks measured.