Remote MCP · Endpoint

io.github.arbonomous/curvecall MCP server

No. io.github.arbonomous/curvecall answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
148 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 19 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
1 hour agoHandshake completed148 ms
1 day agoHandshake completed346 ms
2 days agoHandshake completed233 ms
3 days agoHandshake completed115 ms
4 days agoHandshake completed119 ms
5 days agoHandshake completed273 ms
6 days agoHandshake completed134 ms
8 days agoHandshake completed143 ms
11 days agoHandshake completed139 ms
13 days agoHandshake completed142 ms
15 days agoHandshake completed147 ms
18 days agoHandshake completed269 ms
20 days agoHandshake completed257 ms
22 days agoHandshake completed141 ms
24 days agoHandshake completed323 ms
26 days agoHandshake completed295 ms
27 days agoHandshake completed226 ms
29 days agoHandshake completed153 ms
29 days agoHandshake completed276 ms

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

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