Agent Daily

io.github.gregpunchPublished by GitHub account gregpunchv0.3.0Updated Nov 2, 2026

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

The publisher's own server: daily.dev

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Read-only status service that tells an assistant which AI APIs and MCP servers are up, and recommends a healthy provider for a given task.

What you can do
  • Check live up/down, latency, vendor status and 7-day uptime for monitored APIs and MCP servers, filtered by category
  • Look up the full status record for one named tool
  • Get a recommended provider plus fallbacks for a task phrase such as send email, web search or vector db
  • List recent outages and vendor incidents with UTC start and end times
  • Rank popular LLMs by a 15-minute probe leaderboard scoring correctness and speed
When to use it
Useful when an agent calls external APIs or MCP servers and should avoid ones that are down, or when you want a quick health check and fallback suggestion before choosing a provider. Also handy for comparing LLM availability and latency.
Requirements
Remote Streamable HTTP endpoint; no authentication, API key or environment variable is needed. Network access to the hosted endpoint is required.
Before you install
Read-only and stateless, but the data is reachability only, not correctness or quality, comes from a single probe location, and is refreshed hourly, so it can be stale. Treat it as a hint, not a guarantee, before routing traffic.

Installation

In SourceWeft

  1. Open Agent Daily in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.gregpunch%2Fagent-daily/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Source: README.md at commit 200fac9

Tools

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.

Parameterssortlimit

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.

Parameterstaskrequired

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.

Parametersdaysname

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).

Parameterscategory

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.

Parametersnamerequired

Version history

2
  1. v0.3.0LatestOct 26, 2026
  2. v0.1.0Oct 23, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Daily integrations