"Information about Cloudflare Workers" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Ask your AI about your product's events, delivery health and usage
Vigilia watches your live app, explains every problem in plain language and writes the fix prompt. Your AI fixes it; Vigilia confirms with real traffic. Vigilia watches web apps that are live with real users, including apps built with Lovable, Bolt, v0, Cursor and Claude Code. It catches errors, failed requests and downtime, explains each problem in plain language, and writes a fix prompt for it. Connect Vigilia to Claude and ask what's broken. Claude lists your open incidents worst first. For each one it reads the plain-language diagnosis, who it affects, the technical evidence (error, page, failing request, stack frames and what the visitor did right before) and Vigilia's fix prompt. In Claude Code or another coding agent, Claude can then fix the cause in your own codebase. Once you've deployed, it marks the incident fixed, and Vigilia watches real traffic to confirm the error stayed away. If it comes back, the incident reopens as a regression. You can also ask how an app is doing (uptime, open incidents, today's traffic), get the exact install snippet for a new project, and check that a live site is running Vigilia. Vigilia never reads or changes your code: the fixing happens in your session, by your AI, in front of you. The only tool that changes anything is marking an incident fixed (the install check just records its result on the app), and you can connect with read-only access. Your data is stored in the EU. Emails, tokens and card numbers are stripped from what visitors' browsers send, and only that scrubbed error context is sent to Anthropic to write the diagnosis. Requires a Vigilia account. The free plan covers one app; reporting backend errors (Supabase, Next.js routes, Workers) is part of Pro.
Real-time error logging for Cloudflare Workers, Next.js & Vercel. Catch silent crashes, $500 cost spikes, and every AI call with logs inside Cursor & Claude.
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Check if any website is up (status, latency, redirects, security headers) and set uptime alerts.
Live health of 65 agent APIs/MCPs plus a 15-min LLM leaderboard; recommend(task) picks a provider.
Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
Read-only watchtower for AI agents on-chain: decoded receipts, plan vs execution, Safe audits.
Four x402 tools: endpoint checks, extraction, evidence verification, domain intelligence.
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key
Diagnose AI workflows for failure, security, and handoff risks — RED/AMBER/GREEN per node.
X-Correlation-Id charset, value discarded
W3C traceparent 4-part shape, value discarded
Hydra operation count, body discarded
UTC nanosecond 9-digit band
Cloudflare Workers MCP server: cron-monitor
NetFlow version nibble, bytes discarded
journald cursor shape, value discarded
X-Forwarded-For comma count, value discarded
LEEF attr count, line discarded
