
Tickerr
io.github.imviky-ctrlPublished by GitHub account imviky-ctrlv1.0.1Updated Oct 27, 2026
Live status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools.
Overview
Tickerr gives an assistant live status, pricing, rate limits and latency data for 90+ AI tools and 300+ models, plus anonymous failure reporting.
- What you can do
- List monitored AI tools and check their three-state status (operational, degraded, down)
- Look up token pricing per model and compare costs side by side for a given token count
- Retrieve rate limits, quotas and free-tier details per tool and plan
- Read incident history with severity, duration and affected components
- Check model latency and throughput figures, including p50/p95 time-to-first-token
- Report an API failure and get back live signal state plus a fallback recommendation
- When to use it
- Useful when an assistant routes between LLM providers and needs current pricing, rate limits or outage information before choosing a model, or wants a fallback suggestion after a 5xx error or timeout.
- Requirements
- Either the remote endpoint at tickerr.ai over streamable HTTP, or the npm package tickerr-mcp run locally with npx for stdio clients. No authentication, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Tickerr in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.imviky-ctrl%2Ftickerr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"tickerr": {
"type": "http",
"url": "https://tickerr.ai/mcp"
}
}
}README
Tickerr MCP
Outage radar for AI agents. LLM pricing, status, inference performance, and real-time agent-reported failure signals. 9 tools. No auth required.
Install
Claude Code
Cursor / Windsurf
Claude Desktop (stdio wrapper)
Tools (9)
Give and Take
Tickerr MCP uses a give-and-take model across
get_tool_status, get_incidents, and report_incident.
get_tool_status — Unlock per-model latency
Always include my_status if your agent has made
any call to this provider in the last 5 minutes —
even successful calls. Pass is_up: true,
your response_ms, and the model name.
Basic response (no my_status):
- Operational verdict (OPERATIONAL / DEGRADED / DOWN)
- Response time, last check time, 30-day uptime
Full response (include my_status):
- Everything above +
- Per-model p50/p95 TTFT latency (last 24h)
- 90-day uptime, user reports signal
On failure, add error_code (e.g. "529").
is_up is the only required field.
get_incidents — Contribute to live signal
Include my_status when fetching incident history
to record your observation and see current
agent-reported activity alongside historical data.
Without my_status: incident list + prompt to contribute.
With my_status: incident list + live agent reports count + confirmation your signal was recorded.
report_incident — Get routing intelligence
report_incident — Get routing intelligence
What you get: When your agent calls report_incident
on a failure, you instantly receive:
- How many other agents reported the same issue
- Current signal state (detecting / confirmed / recovering)
- Which model to fall back to
What you give: Anonymous failure signal — provider, model, error code, latency only. No request content. No personal data.
How to use it (Claude Code):
report_incident fires automatically when your agent
hits a 5xx error. No configuration needed — the tool
description instructs Claude Code to call it.
How to use it (other agents): Add this to your system prompt:
Reporting window: Active for 7 days from last Tickerr tool use. Renews automatically on any tool call.
Opt out any time: tickerr.ai/mcp/opt-out
Signal States
Example Return Payload (report_incident)
Data Coverage
- Status: 90+ AI tools monitored every 5 minutes
- Pricing: 300+ models, updated twice daily from OpenRouter and official provider docs
- Performance: Authenticated API latency checks every 5 minutes
- Agent signals: Live feed at tickerr.ai/agent-reports
Links
- Docs: tickerr.ai/mcp-server
- Status: tickerr.ai/status
- Pricing: tickerr.ai/pricing
- Agent reports: tickerr.ai/agent-reports
- Opt out: tickerr.ai/mcp/opt-out
Source: README.md at commit 6c817ad
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.