Remote MCP · Endpoint

Model Ruler — AI Cost Calculators MCP server

No. Model Ruler — AI Cost Calculators answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://modelruler.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.helphub369/model-ruler
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
491 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Deterministic AI/LLM cost calculators with one-command setup across major agent clients.
Listing
From the official MCP registry (active).
Recent checks of Model Ruler — AI Cost Calculators
CheckedResultHandshake
1 hour agoHandshake completed491 ms
1 day agoHandshake completed752 ms
4 days agoHandshake completed628 ms
6 days agoHandshake completed554 ms
9 days agoHandshake completed556 ms
11 days agoHandshake completed1.91 s
13 days agoHandshake completed584 ms
15 days agoHandshake completed882 ms
17 days agoHandshake completed619 ms
19 days agoHandshake completed483 ms
21 days agoHandshake completed525 ms
22 days agoHandshake completed545 ms
23 days agoHandshake completed630 ms
25 days agoHandshake completed312 ms

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

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 Model Ruler — AI Cost Calculators and makes no claim about it beyond what these checks measured.