
Tickerr
io.github.imviky-ctrl由 GitHub 账号 imviky-ctrl 发布v1.0.1更新于 Oct 27, 2026
Live status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools.
概览
Tickerr 为助手提供 90+ 款 AI 工具、300+ 个模型的实时状态、价格、速率限制与延迟数据,并支持匿名故障上报。
- 可以做什么
- 列出受监控的 AI 工具并查询其三态状态(正常、降级、宕机)
- 查询各模型的 token 价格,并按给定 token 数并排比较成本
- 获取各工具与套餐的速率限制、配额和免费额度详情
- 读取故障历史,含严重程度、持续时间和受影响组件
- 查看模型延迟与吞吐数据,包括 p50/p95 首字延迟
- 上报 API 故障,获取实时信号状态与备用模型建议
- 适用场景
- 适合需要在多个大模型供应商之间做路由、在选模型前了解当前价格、速率限制或宕机情况的助手,或在遇到 5xx 错误、超时后希望获得切换建议的场景。
- 运行要求
- 可使用 tickerr.ai 的远程 streamable HTTP 端点,或通过 npx 在本地运行 npm 包 tickerr-mcp 以支持 stdio 客户端。未声明需要认证、API 密钥或环境变量。
安装
在 SourceWeft 中
- 打开 控制台中的 Tickerr,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.imviky-ctrl%2Ftickerr/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"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
来源:README.md,提交 6c817ad
工具
0版本历史
1- v1.0.1最新Sep 16, 2026
评分
已满足适用检查项的 75%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具必需15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。