Back to Browse

Agent Daily MCP Server

Developer ToolsModerate6.3MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://agent-daily.agentdaily.workers.dev/mcp

Security Report

6.3
Moderate6.3Moderate Risk

This is a read-only, unauthenticated status-monitoring MCP server whose network access matches its purpose of probing public APIs and status pages. The main concerns are low-severity: the server logs client names, user agents, country codes and tool arguments for analytics, and it uses a wildcard CORS policy on the public MCP endpoint. No malicious patterns, data exfiltration, shell execution, or hardcoded secrets were found. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity).

8 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub 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

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 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   # local
npm test                                           # MCP SDK client check against localhost:8787
npx 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.

Reviews

No reviews yet

Be the first to review this server!