Remote MCP · Endpoint

io.github.lazymac2x/ai-cost-optimizer MCP server

No. io.github.lazymac2x/ai-cost-optimizer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.lazy-mac.com/ai-cost-optimizer/mcp

The last check completed an MCP handshake.

Registry name
io.github.lazymac2x/ai-cost-optimizer
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
199 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Cloudflare Workers MCP server: ai-cost-optimizer
Listing
From the official MCP registry (active).
Recent checks of io.github.lazymac2x/ai-cost-optimizer
CheckedResultHandshake
1 hour agoHandshake completed199 ms
18 hours agoHandshake completed161 ms
2 days agoHandshake completed224 ms
3 days agoHandshake completed158 ms
4 days agoHandshake completed187 ms
5 days agoHandshake completed165 ms
6 days agoHandshake completed211 ms
7 days agoHandshake completed226 ms
10 days agoHandshake completed453 ms
13 days agoHandshake completed248 ms
15 days agoHandshake completed174 ms
17 days agoHandshake completed289 ms
19 days agoHandshake completed157 ms
21 days agoHandshake completed143 ms
23 days agoHandshake completed195 ms
25 days agoHandshake completed185 ms
27 days agoHandshake completed236 ms
28 days agoHandshake completed173 ms
29 days agoHandshake completed358 ms

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

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.lazymac2x/ai-cost-optimizer and makes no claim about it beyond what these checks measured.