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.

已驗證Streamable HTTP可網頁執行安全與監控AI 與機器學習

概覽

AI 產生的概覽

Tickerr 讓助理取得 90+ 款 AI 工具、300+ 個模型的即時狀態、價格、速率限制與延遲資料,並可匿名回報故障。

可以做什麼
  • 列出受監控的 AI 工具並查詢其三態狀態(正常、降級、中斷)
  • 查詢各模型的 token 價格,並依指定 token 數並排比較成本
  • 取得各工具與方案的速率限制、配額與免費額度細節
  • 讀取故障歷史,包含嚴重程度、持續時間與受影響元件
  • 查看模型延遲與吞吐量數據,包括 p50/p95 首字延遲
  • 回報 API 故障,取得即時訊號狀態與備援模型建議
適用情境
適合需要在多個大模型供應商之間做路由、在挑選模型前掌握目前價格、速率限制或中斷情況的助理,或在遇到 5xx 錯誤、逾時後想取得切換建議的情境。
執行需求
可使用 tickerr.ai 的遠端 streamable HTTP 端點,或以 npx 在本機執行 npm 套件 tickerr-mcp 以支援 stdio 用戶端。未宣告需要驗證、API 金鑰或環境變數。
安裝前請注意
狀態與故障類工具會要求助理把自身的呼叫結果(是否可用、回應時間、模型名稱、錯誤碼)傳送給該服務;說明稱回報為匿名且不含請求內容,但仍是離開本機的遙測資料。最後一次使用後回報視窗持續 7 天,除非主動退出。價格與狀態資料來自第三方,可能有延遲。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Tickerr,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

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

claude mcp add tickerr --transport http https://tickerr.ai/mcp

Cursor / Windsurf

json
{  "mcpServers": {    "tickerr": {      "url": "https://tickerr.ai/mcp"    }  }}

Claude Desktop (stdio wrapper)

npx -y tickerr-mcp

Tools (9)

ToolWhat it does
get_api_pricingCurrent input/output/cached token costs for 300+ models. Updated twice daily.
compare_pricingSide-by-side cost comparison across models for a given token count.
get_tool_statusThree-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_incidentsHistorical 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_limitsPer-plan rate limits and quotas for any AI tool.
get_free_tierFree tier details — what's included, what's limited.
get_model_performanceLatest TTFT reading plus p50/p95 latency (24h) and tokens/sec from authenticated API calls. Use for real-time routing decisions.
list_toolsLists all 90+ monitored tools. Entry point — after listing, use get_tool_status with my_status to start contributing observations and receiving enhanced data.
report_incidentReport an LLM API failure. Returns live signal from other agents and a routing recommendation. Anonymous.

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
json
{  "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.

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:

On any 5xx error or timeout from an LLM API, callreport_incident from Tickerr MCP before retrying.Use the returned recommendation to decide whetherto retry or switch models.

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

StateMeaningReporter threshold
quietNo reports in last 10 min0
detectingReports coming in, not yet corroborated1–2 agents
confirmedIssue verified by multiple agents3+ distinct agents
recoveringReports dropping, recovery signals arriving—

Example Return Payload (report_incident)

REPORT RECEIVEDProvider: anthropicModel: claude-haiku-3-5Error: 529 overloaded
CURRENT SIGNAL (anthropic/claude-haiku-3-5)Status: CONFIRMEDAgents reporting (last 10 min): 14Total reports (last 10 min): 31
RECOMMENDATIONAction: FALLBACKSwitch to: gpt-4o-mini (openai)
REPORTING CADENCENext report for this model: in 3600 seconds if still failing.Signal confirmed by multiple agents — reduce reporting frequency.

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
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。