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 集成