mcpField
A
Agent Daily

Agent Daily

Remote
gregpunch.github.ioCloud & Infra0Updated 2d ago

About Agent Daily

Agent Daily is an hourly reliability index for APIs and MCP servers used by AI agents. Agent builders can check reachability and route around outages; its read-only MCP server exposes status queries backed by cached status data.

Key features

  1. 01Hourly reachability checks
  2. 02Public status page and JSON
  3. 03Uptime, latency, and vendor status fields
  4. 04Read-only MCP status tools
  5. 05Category-based tool listing

Use cases

  1. 01Check a dependency before an agent call
  2. 02Choose a fallback when a service is down
  3. 03Inspect tool status from an MCP host

MCP support

Provides a read-only Streamable HTTP MCP server with `list_tools` and `tool_status`. Both tools read status data with a five-minute cache.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://agent-daily.agentdaily.workers.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Agent Daily: is this tool up right now?

A free, hourly reliability index for the APIs and MCP servers AI agents call: OpenAI, Anthropic, GitHub (API + MCP), Stripe, Slack, Cloudflare, Brave/Serper search, Linear and DeepWiki MCP, and more (20 tools).

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

import requests
s = 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 20 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   # local
npm test                                           # MCP SDK client check against localhost:8787
npx wrangler deploy                                # needs CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.