Remote MCP · Endpoint

io.github.Ainode-tech/cache-proxy MCP server

No. io.github.Ainode-tech/cache-proxy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cache.api.ainode.tech/mcp

The last check completed an MCP handshake.

Registry name
io.github.Ainode-tech/cache-proxy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
241 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
LLM caching proxy (x402 USDC on Base) - exact + semantic cache. Free health.
Listing
From the official MCP registry (active).
Recent checks of io.github.Ainode-tech/cache-proxy
CheckedResultHandshake
1 hour agoHandshake completed241 ms
2 days agoHandshake completed240 ms
4 days agoHandshake completed155 ms
5 days agoHandshake completed103 ms
7 days agoHandshake completed174 ms
8 days agoHandshake completed436 ms
9 days agoHandshake completed127 ms
12 days agoHandshake completed168 ms
13 days agoHandshake completed66 ms
15 days agoHandshake completed178 ms
16 days agoHandshake completed348 ms
18 days agoHandshake completed87 ms
19 days agoHandshake completed117 ms
20 days agoHandshake completed67 ms
20 days agoHandshake completed247 ms
21 days agoHandshake completed51 ms
22 days agoHandshake completed333 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 io.github.Ainode-tech/cache-proxy and makes no claim about it beyond what these checks measured.