Warden by Project Helena · MCP
Ask your AI what is down.
Warden is open-source uptime monitoring for agencies, operated through the assistant you already use. Ask about every client, diagnose an incident and configure routine checks through a role-scoped MCP connection.
One operational loop
Connect. Ask. Act. Verify.
-
1.0
Connect the assistant
Create a role-scoped API key and point an MCP-compatible assistant at /api/mcp. Start with viewer access for investigation.
Viewer key · Streamable HTTP · Bearer auth
-
2.0
Ask what happened
Query current state, uptime over 24 hours, 7 days or 30 days, incident history, check events, latency and the reason an alert fired.
State · incidents · events · latency · certificates
-
3.0
Configure routine work
With a separate editor key, create HTTP, TCP, ping or DNS monitors in batches, create and rename groups, move monitors and pause checks.
Editor key · no delete tool
-
4.0
Verify the fix
Run a check immediately, then compare the result with recent events and the learned latency baseline instead of waiting for the next interval.
check_now · history · P50/P95 baseline
Safe by default.
Give the assistant a viewer key for everyday questions and incident diagnosis. Warden does not return users, sessions, passwords, API keys or webhook URLs.
- List and inspect monitors
- List incidents and monitor events
- Read latency history and notification policy
- List SSL expiry warnings
- Run a check now
- Read operational insights
Intentional control.
Use a separate editor key only for assistants that should change monitoring. MCP cannot delete monitors or administer users, status pages or notification channels.
- Create monitors in batches
- Create or rename groups
- Move monitors between groups
- Pause or resume monitors
One assistant for the team. One status page per client.
Your operators ask across the client portfolio. Each client still gets a branded status page and a private status-only login for their services. The AI interface reduces internal dashboard work; the client experience stays controlled and clear.
Warden reports and configures monitoring. It does not deploy a fix or repair production autonomously. Event tools may include up to 2 KB of response body, so treat monitored content as untrusted and keep write access separate.
Bring the client list. Leave with Warden connected.
We configure the monitors, groups, client access and a least-privilege MCP key with you.
Book a setup call