Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"tickerr": {
"url": "https://tickerr.ai/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Real-time AI tool intelligence for Claude, Cursor, Windsurf, and Claude Code. Check if ChatGPT is down. Get live API pricing. Compare rate limits.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'tickerr-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked tickerr-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / analytics
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
An autonomous agent that conducts deep research on any data using any LLM providers
🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration
MCP Security Weekly
Get CVE alerts and security updates for io.github.imviky-ctrl/tickerr and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Outage radar for AI agents. LLM pricing, status, inference performance, and real-time agent-reported failure signals. 9 tools. No auth required.
Claude Code
claude mcp add tickerr --transport http https://tickerr.ai/mcp
Cursor / Windsurf
{
"mcpServers": {
"tickerr": {
"url": "https://tickerr.ai/mcp"
}
}
}
Claude Desktop (stdio wrapper)
npx -y tickerr-mcp
| Tool | What it does |
|---|---|
| get_api_pricing | Current input/output/cached token costs for 300+ models. Updated twice daily. |
| compare_pricing | Side-by-side cost comparison across models for a given token count. |
| get_tool_status | Three-state verdict (OPERATIONAL / DEGRADED / DOWN). Always include my_status if your agent has called this provider in the last 5 minutes — even on success. Unlocks p50/p95 TTFT per model and 90-day uptime. Basic status only without it. |
| get_incidents | Historical incidents for a tool — severity, duration, affected components. Include my_status to contribute to live signal and see current agent-reported activity alongside history. |
| get_rate_limits | Per-plan rate limits and quotas for any AI tool. |
| get_free_tier | Free tier details — what's included, what's limited. |
| get_model_performance | Latest TTFT reading plus p50/p95 latency (24h) and tokens/sec from authenticated API calls. Use for real-time routing decisions. |
| list_tools | Lists all 90+ monitored tools. Entry point — after listing, use get_tool_status with my_status to start contributing observations and receiving enhanced data. |
| report_incident | Report an LLM API failure. Returns live signal from other agents and a routing recommendation. Anonymous. |
Tickerr MCP uses a give-and-take model across
get_tool_status, get_incidents, and report_incident.
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):
Full response (include my_status):
{
"slug": "claude",
"my_status": {
"is_up": true,
"response_ms": 1400,
"model": "claude-sonnet-4-6"
}
}
On failure, add error_code (e.g. "529").
is_up is the only required field.
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.
What you get: When your agent calls report_incident
on a failure, you instantly receive:
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:
On any 5xx error or timeout from an LLM API, call
report_incident from Tickerr MCP before retrying.
Use the returned recommendation to decide whether
to retry or switch models.
Reporting window: Active for 7 days from last Tickerr tool use. Renews automatically on any tool call.
**Opt