Home / MCP registry index / com.flarewarden/website-monitoring

FlareWarden

com.flarewarden/website-monitoring in the official MCP registry. Endpoint https://mcp.flarewarden.com/mcp.

The registry describes it as: Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http website-monitoring https://mcp.flarewarden.com/mcp

{
  "mcpServers": {
    "website-monitoring": {
      "url": "https://mcp.flarewarden.com/mcp"
    }
  }
}

code --add-mcp '{"name":"website-monitoring","type":"http","url":"https://mcp.flarewarden.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

check_service_status check_service_status_url recommend_monitoring explain_features search_help get_account_overview get_usage list_sites get_site get_monitor_history get_report list_incidents get_incident diagnose_site review_coverage review_noise list_status_pages get_status_page list_team search_service_catalog invite_member revoke_invitation change_member_role change_member_access rename_account get_my_notifications update_my_notifications list_webhooks list_webhook_deliveries add_webhook update_webhook test_webhook retry_webhook_delivery search_audit_log plan_site create_site plan_dependency add_dependency apply_dependency_change plan_content_check add_content_check plan_cron_monitor add_cron_monitor update_monitor set_monitor_paused plan_bulk_pause apply_bulk_pause set_anomaly_detection dismiss_anomaly track_subdomain_certificate plan_dns_watch add_dns_watch dismiss_suggestion plan_status_page create_status_page update_status_page add_status_page_component update_status_page_component remove_status_page_component draft_incident_post and 5 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-02): a3c109117f059af5. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-flarewarden-website-monitoring/badge.svg)](https://lazaretto.dev/mcp-registry/com-flarewarden-website-monitoring)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Stripe MCP servers · Monitoring and observability MCP servers