Agent Daily

io.github.gregpunch由 GitHub 帳號 gregpunch 發布v0.3.0更新於 Nov 2, 2026

Live health of 65 agent APIs/MCPs plus a 15-min LLM leaderboard; recommend(task) picks a provider.

發布方自己的服務:daily.dev

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

概覽

AI 產生的概覽

唯讀狀態服務,告訴助理哪些 AI API 與 MCP 伺服器目前可用,並為指定任務推薦健康的供應商。

可以做什麼
  • 依類別查詢受監控 API 與 MCP 伺服器的上線狀態、延遲、廠商狀態與 7 天可用率
  • 查看某個指定工具的完整狀態紀錄
  • 依「寄送郵件」「網頁搜尋」「向量資料庫」等任務描述推薦首選供應商與備援
  • 列出近期中斷與廠商事故,含 UTC 起訖時間
  • 依 15 分鐘探測的排行榜,按正確率與速度排序熱門大型語言模型
適用情境
適合助理需要呼叫外部 API 或 MCP 伺服器、希望避開故障服務時使用;也適合在選擇供應商前快速做健康檢查並取得備援建議,或比較各模型的可用性與延遲。
執行需求
遠端 Streamable HTTP 端點,不需驗證、API 金鑰或環境變數,只要能連上該託管端點即可。
安裝前請注意
服務本身唯讀且無狀態,但資料僅反映可達性,不代表正確性或品質,且來自單一探測點、每小時更新,可能已過時。路由前應視為參考而非保證。

安裝

在 SourceWeft 中

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

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.gregpunch%2Fagent-daily/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "agent-daily": {
      "type": "http",
      "url": "https://agent-daily.agentdaily.workers.dev/mcp"
    }
  }
}

README

Agent Daily: is this tool up right now?

A free, hourly reliability index for the APIs and MCP servers AI agents call: 65 providers across LLMs, search, scraping, email, vector DBs, voice, payments, messaging, maps, CRM, storage and public remote MCP servers, with 7-day uptime, p50/p95 latency and incident history.

Built for agent builders. Check before your agent calls a tool, fall back when a tool is down, and stop burning retries on outages.

claude mcp add --transport http agent-daily https://agent-daily.agentdaily.workers.dev/mcp

Consume status.json

python
import requestss = requests.get("https://gregpunch.github.io/agent-daily/status.json", timeout=5).json()tool = next(t for t in s["tools"] if t["name"] == "OpenAI API")if not tool["up"] or tool["vendor_status"] in ("major", "critical"):    ...  # route to a fallback provider

Fields: schema_version, generated_at (UTC), summary.{up,total}, and tools[] with name, category, up, http_status, latency_ms, vendor_status, uptime_24h_pct, checks_24h, error. Data is refreshed hourly; treat it as stale if older than about 2h. Please cache.

Limits: these are reachability checks only (an expected HTTP code), not correctness or quality tests. There is a single probe location.

A free public status page for 65 tools AI agents depend on. This is Phase 1, a two-week validation.

Run locally

python3 check.py   # probe all tools -> results.db (SQLite)python3 build.py   # render site/index.html

Files: tools.json (config), tools.md (list + method), check.py, build.py, site/ (static output), preview.png.

Deploy plan (free tiers)

Recommended: GitHub Actions + GitHub Pages ($0).

  1. Push this folder to a public GitHub repo.
  2. Add .github/workflows/check.yml with schedule: cron: "0 * * * *" (hourly). Steps: checkout, pip install requests, python check.py && python build.py, commit results.db back (or store it as an artifact), then deploy site/ with actions/deploy-pages.
  3. Turn on Pages (source: GitHub Actions). Public repos get unlimited Actions minutes.

Alternative: Cloudflare Worker cron + D1 + Pages ($0). Port check.py to a Worker scheduled() handler (free tier: 100k requests/day, cron triggers included). Store rows in D1 (free 5 GB), and render the page or serve JSON from the Worker or Pages. This option is the better base for the paid MCP/API later.

Estimated monthly cost

ItemCost
GitHub Actions + Pages (public repo) or Cloudflare free tier$0
Domain (optional, e.g. agentdaily.dev)~$1–1.25/mo ($12–15/yr)
Paid-API functional tests (Phase 2 only)$0 now; cap $30–50
Phase 1 total$0–2/mo

MCP server (mcp-worker/)

This is a stateless, read-only MCP server on a Cloudflare Worker. It uses Streamable HTTP at /mcp and offers two tools: list_tools(category?) and tool_status(name). Both read status.json with a 5-minute cache. It also serves /.well-known/mcp/server-card.json.

cd mcp-worker && npm install && npx wrangler dev   # localnpm test                                           # MCP SDK client check against localhost:8787npx wrangler deploy                                # needs CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID

MCP tools (v0.2.0)

Remote endpoint: https://agent-daily.agentdaily.workers.dev/mcp (Streamable HTTP, no auth, read-only)

  • recommend(task): maps a phrase or category ("send email", "web search", "llm", "scrape a page") to a category and returns the healthiest provider plus 1-2 fallbacks, with reasons and freshness.
  • incidents(name?, days=7): outages and vendor incidents with UTC start/end.
  • list_tools(category?): matches either category or routing task.
  • tool_status(name): full record, including 7-day uptime and p50/p95.

Data: status.json (current + 7d stats) and history.json (incidents), both regenerated hourly.

LLM Live Probe (v0.3.0)

https://gregpunch.github.io/agent-daily/llm/: every 15 minutes ~20 popular models (via OpenRouter, plus optional direct OpenAI/Anthropic/Gemini control checks) get "Reply with exactly the word pong". Leaderboard (score = 60% 24h correctness + 40% speed), per-model detail pages and a methods page. Data: llm/leaderboard.json, llm/models/<id>.json. MCP tool: llm_leaderboard(sort?). Probing skips cleanly when no keys are set; spend is capped at $2.50/30 days in llm/models.json.

來源:README.md,提交 200fac9

工具

5

llm_leaderboard

Live LLM leaderboard

Which LLMs are up, correct and fast right now. Every 15 minutes ~20 popular models (OpenAI, Anthropic, Google, Meta, Mistral, DeepSeek, xAI, Qwen, Cohere...) are asked to reply 'pong'; returns rank, score (60% 24h correctness + 40% speed), correct %, p50 time-to-first-token, p50 total time, cost per 1k calls, uptime and last result. Use to pick a fast, reliable model. sort: score (default) | correct | ttft | total | cost.

輸入參數sortlimit

recommend

Recommend a healthy provider for a task

Before calling an external API, ask which provider to use. Give a task phrase or category (e.g. 'send email', 'web search', 'llm', 'scrape a page', 'vector db', 'speech to text', 'payments', 'geocode'). Returns the top healthy pick plus 1-2 fallbacks ranked by live status, vendor status, 7-day uptime and latency, with a reason and data freshness.

輸入參數task必填

incidents

Recent incidents

Outages (consecutive failed probes) and vendor status-page incidents with UTC start/end over the last N days (max 7). Optional provider name filter. Use to judge whether a failing API is a known incident.

輸入參數daysname

list_tools

List monitored tools

List the APIs and MCP servers Agent Daily monitors, with current up/down, latency and vendor status. Call before choosing a provider. Optional category filter (e.g. LLM, MCP, Search, Payments, Comms, Infra).

輸入參數category

tool_status

Get one tool's status

Full status record for one monitored tool (up, http_status, latency_ms, vendor_status, uptime_24h_pct). Case-insensitive name or substring, e.g. 'openai', 'GitHub MCP'. Reachability only, not correctness.

輸入參數name必填

版本歷史

2
  1. v0.3.0最新Oct 26, 2026
  2. v0.1.0Oct 23, 2026

評分

已滿足適用檢查項的 90%

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

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

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

其他 Daily 整合