mcpbeat

AI Rate Limit Tracker MCP Server

io.github.lazymac2x/ai-rate-limit-tracker
answering

AI Rate Limit Tracker is answering right now. Last checked 5 min ago. It exposes 4 tools. Last commit 17 May 2026.

Cloudflare Workers MCP server: ai-rate-limit-tracker

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
147 ms
Response time
average over 24h
0
Stars
last commit 17 May 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add ai-rate-limit-tracker --transport http https://api.lazy-mac.com/ai-rate-limit-tracker/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-rate-limit-tracker": {
      "url": "https://api.lazy-mac.com/ai-rate-limit-tracker/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai-rate-limit-tracker]
url = "https://api.lazy-mac.com/ai-rate-limit-tracker/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-rate-limit-tracker": {
      "url": "https://api.lazy-mac.com/ai-rate-limit-tracker/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai-rate-limit-tracker": {
      "url": "https://api.lazy-mac.com/ai-rate-limit-tracker/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

forecast
get_forecast
Forecast when rate limits will be exhausted and get scheduling recommendations.
provider
get_provider_limits
Get published rate limit specs (RPM, TPM, RPD, context window) for an AI provider and optional model.
providers
list_providers
List all AI providers supported by the tracker with their models and default limits.
track
track_usage
Record an AI API call and get real-time usage counters plus warnings if approaching limits.

Endpoints

URLTransportStateLatencyChecked
https://api.lazy-mac.com/ai-rate-limit-tracker/mcp streamable-http answering 174 ms 5 min ago

AI Rate Limit Tracker — questions

Answers built from our own checks of this server.

What can AI Rate Limit Tracker do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_forecast, get_provider_limits, list_providers, track_usage. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AI Rate Limit Tracker working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 147 ms. The bar chart above shows every period we have measured.
How do I connect AI Rate Limit Tracker?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AI Rate Limit Tracker need an API key?
No. AI Rate Limit Tracker completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AI Rate Limit Tracker?
It answers our handshake in 147 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is AI Rate Limit Tracker open source?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.