Remote MCP · Endpoint

OptimToken MCP server

No. OptimToken answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://optimtoken-mcp.optimnow.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.OptimNow/ai-pricing-hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
254 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Compare LLM API and cloud compute pricing, estimate workload costs, pick a model within budget.
Listing
From the official MCP registry (active).
Recent checks of OptimToken
CheckedResultHandshake
56 minutes agoHandshake completed254 ms
1 day agoHandshake completed111 ms
2 days agoHandshake completed199 ms
5 days agoHandshake completed193 ms
8 days agoHandshake completed121 ms
10 days agoHandshake completed194 ms
12 days agoHandshake completed4.81 s
14 days agoHandshake completed198 ms
16 days agoHandshake completed127 ms
18 days agoHandshake completed189 ms
20 days agoHandshake completed112 ms
22 days agoHandshake completed6.70 s
23 days agoHandshake completed7.40 s

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

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 OptimToken and makes no claim about it beyond what these checks measured.