FlareWarden
REMOTE · MCP.FLAREWARDEN.COM
Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.
Available components
Last scanned (22 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (invite_member). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 17045 tokens (~227/item across 75 items; 65 tools + 10 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 67 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 0
- Server version: fw-89c97f34 → fw-40b4f44b functional
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.flarewarden.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.flarewarden.com | CN=YE1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 67fc47e8e88dbdd702c490d8ac7846d55b5 |
| SANs: mcp.flarewarden.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.flarewarden.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| flarewarden.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.flarewarden.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.flarewarden.com/mcp | HTTPS enforced | 301 | https://mcp.flarewarden.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
revoke_invitation Cancel an invitation ~92
Use this when the user wants to withdraw an invitation that has not been accepted yet. Returns which invitation was cancelled; the link in its email stops working and nobody is emailed. Owners and admins only. Not for removing someone who already joined: that is done in the dashboard, and the result gives the link.
| Name | Type | Req | Description |
|---|---|---|---|
| invitation | string | yes | The invitation's id (from list_team) or the invited email address. |
No output schema declared.
No examples provided.
schedule_maintenance Schedule a drafted maintenance window ~135
Use this when the user has approved a draft_maintenance draft. Schedules it as the dashboard's Maintenance page does: it shows on the status pages, and subscribers are emailed only if the draft said so. Returns the window and its id. Safe to repeat: the same draft id schedules once. Not for changing a window already scheduled: update_maintenance moves, extends, renames or ends it.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| draft_id | string | yes | The draft's id from draft_maintenance (it starts with pl_). |
No output schema declared.
No examples provided.
search_audit_log Search the audit log ~218
Use this when the user asks who changed something in the account and when: who paused a site, who invited someone, what an AI agent did. Returns entries newest first with the time, the member, the action, what it changed and, for changes made through an AI agent, which one (via). Owners and admins only. Not for monitoring history or incidents: use get_monitor_history or list_incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Only this action, as entries name it (for example monitor.pause or invitation.create). |
| from | string | – | Only entries on or after this date, YYYY-MM-DD. |
| member | string | – | Only changes made by this member, by email address. |
| page | integer | – | Page of results, 25 a page. Default 1. |
| text | string | – | Words to find in the entry: a site or member name, an email address, an action such as "paused". |
| to | string | – | Only entries on or before this date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
search_help Search FlareWarden's help docs ~109
Use this when the user asks how to do something in FlareWarden, such as adding a custom domain to a status page, sending alerts to Slack, adding a cron job heartbeat, allowlisting probe IPs or inviting a teammate. Searches the documentation at flarewarden.com/docs and returns the best-matching passages with links to their pages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many passages to return (default 5). |
| query | string | yes | The question or keywords, in the user's words. |
No output schema declared.
No examples provided.
search_service_catalog Search the services FlareWarden can watch ~99
Use this when the user asks whether FlareWarden can watch a third-party service their site depends on (a payment provider, cloud, CDN, email or auth service). Returns matching services with their category and status page, and FlareWarden's public status page when there is one. Not for whether a service is down now: use check_service_status.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The service's name, such as Stripe or AWS. |
No output schema declared.
No examples provided.
set_anomaly_detection Turn anomaly detection on or off ~183
Use this when the user wants FlareWarden to alert on unusual response times of a site, or unusual run times of a cron job, or to stop doing so or change how sensitive it is. Returns whether it is on, its sensitivity, and its recent anomalies. Turning it on costs one monitor; turning it off frees it. It learns for 3 days before reporting. Not for ordinary up or down alerts, which every monitor sends.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | – | A cron job on the site, by id or name; leave out for the site's response times. |
| enabled | boolean | yes | True to turn it on (or change sensitivity), false to turn it off. |
| sensitivity | string | – | low (fewer alerts), normal or high. |
| site | string | yes | The site, by id, name or part of its URL. |
No output schema declared.
No examples provided.
set_monitor_paused Pause or resume a monitor ~181
Use this when the user wants to stop or restart checks of a site or one of its checks, for example during planned work. Returns the new state and what it means: pausing a site stops its checks, content checks and dependencies, holds its DNS watch alerts, and resolves its open automatic incidents, but its cron jobs keep alerting until each is paused; pausing frees no room on the plan; resuming must fit the plan's active monitors. Not for scheduling maintenance windows or deleting a monitor: those are in the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | – | One of the site's content checks, dependencies or cron jobs, by id or name; leave out for the whole site. |
| paused | boolean | yes | True to pause, false to resume. |
| site | string | yes | The site, by id, name or part of its URL. |
No output schema declared.
No examples provided.
test_webhook Send a test to a webhook ~96
Use this when the user wants to check that a webhook or chat channel receives FlareWarden's alerts. Sends one test event to the destination now, records the delivery, and returns whether it arrived and the HTTP status. Owners and admins only. Not for the delivery history of real alerts: use list_webhook_deliveries.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook | string | yes | The webhook's id (from list_webhooks) or its name. |
No output schema declared.
No examples provided.
track_subdomain_certificate Track a subdomain's certificate ~165
Use this when the user wants FlareWarden to watch the TLS certificate of a subdomain it found under a site (from public certificate logs), or to stop. Returns the subdomain's tracking state and, when tracking starts, its certificate's issuer and expiry. A tracked subdomain gets a daily certificate check and expiry alerts, at no cost to the plan. Not for checking the subdomain itself is up: plan it as a site with plan_site.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site the subdomain was found under, by id, name or part of its URL. |
| subdomain | string | yes | The subdomain, such as api.acme.com, or its id. |
| tracked | boolean | – | False to stop tracking; true by default. |
No output schema declared.
No examples provided.
update_maintenance Change a maintenance window ~384
Use this when the user wants to change planned or running maintenance: end it early or start it now, extend or move it, rename it, or pause or resume a recurring schedule. Changes it as the dashboard's Maintenance page does and returns the window as it is now. A window that asked to tell subscribers emails them as the page's would: the new time when a one-time window moves, and that it started or ended. Not for new work (use draft_maintenance), calling it off (use cancel_maintenance) or an outage (use draft_incident_post).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | edit changes the fields given and keeps the rest; start begins a scheduled window now; end finishes one in progress now; pause and resume a recurring schedule. |
| description | string | – | For edit: new details shown with the window; an empty string clears them. |
| duration_minutes | integer | – | For edit: the new length, 1 to 720 minutes; a window in progress ends this long after it started. |
| maintenance | string | yes | The window: its id from list_incidents with kind maintenance, or its title. |
| notify_subscribers | boolean | – | For edit: whether status page subscribers are emailed about the window. Only when the user asks. |
| site | string | yes | The window's site: its id, name or part of its URL. |
| timezone | string | – | For edit: the IANA time zone when is read in. Default: the window's own zone. |
| title | string | – | For edit: the new title, as subscribers will read it. |
| when | string | – | For edit: the new start, a date and time such as 2026-11-02 02:00 (read in timezone), or RFC 3339; for a recurring window, the time of day. |
No output schema declared.
No examples provided.
update_monitor Change a monitor's settings ~612
Use this when the user wants to change how a site or one of its checks is watched: a site's name, interval, timeout or group; a content check's text, selector, page, kind, attribute, limits, description, severity or interval; a dependency's name, description, severity or interval, and a plain HTTP dependency's URL and expected text; a cron job's schedule, grace period, longest run, description or severity. Returns the settings now in force. Only the fields given change. Not for pausing (use set_monitor_paused), deleting (the dashboard does that), or a dependency's components (plan it again with plan_dependency). Each setting is documented at https://flarewarden.com/docs/monitors.
| Name | Type | Req | Description |
|---|---|---|---|
| attribute | string | – | A content check's attribute to read, for attribute_check. |
| case_sensitive | boolean | – | Whether a content check matches case exactly. |
| check | string | – | One of the site's content checks, dependencies or cron jobs, by id or name; leave out to change the site itself. |
| check_type | string | – | A content check's kind. |
| description | string | – | A check's description. |
| expected_text | string | – | A plain HTTP dependency's text its answer must hold (or, with match, must not hold or match); an empty string stops checking it. |
| grace | integer | – | A cron job's grace period in seconds. |
| group | string | – | A site's group; an empty string removes it. |
| interval | integer | – | Seconds between checks (30, 60, 300, 600, 1800 or 3600, as the plan allows). |
| match | string | – | How expected_text is matched. Default contains. |
| max | number | – | A content check's highest value allowed, for numeric_range or element_count. |
| max_run | integer | – | A cron job's longest normal run in seconds; 0 turns it off. |
| min | number | – | A content check's lowest value allowed, for numeric_range or element_count. |
| name | string | – | The site's new name, or with check, the check's. |
| page | string | – | A content check's page path. |
| schedule | string | – | A cron job's schedule: a cron expression (UTC), every N minutes, hours or days, or heartbeat. |
| selector | string | – | A content check's CSS selector. |
| severity | string | – | How serious a failure is. |
| site | string | yes | The site, by id, name or part of its URL. |
| text | string | – | A content check's text or pattern. |
| timeout | integer | – | Seconds a site's checks wait for an answer before they count as failed (5, 10, 15 or 30; 10 unless changed). A longer one lets a slow page pass. |
| url | string | – | A plain HTTP dependency's URL; a status page dependency is changed with plan_dependency. |
No output schema declared.
No examples provided.
update_my_notifications Change my alert emails ~322
Use this when the user wants FlareWarden to email them more or fewer kinds of alert, pause or resume all alert emails, or change when SSL expiry warnings arrive. Changes only the settings given, for the user alone, and returns all of them after the change. Not for teammates' alerts, webhooks or chat channels.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate_changed | boolean | – | Email the user about Certificate Changed. |
| dns_failures | boolean | – | Email the user about DNS Failures and Changes. |
| domain_expiring | boolean | – | Email the user about Domain Expiring. |
| email_alerts | boolean | – | The master switch: false pauses every alert email to the user from this account. |
| issuer_changed | boolean | – | Email the user about Certificate Issuer Changed. |
| monitor_down | boolean | – | Email the user about Monitor Down. |
| monitor_recovered | boolean | – | Email the user about Monitor Recovered. |
| performance_anomalies | boolean | – | Email the user about Performance Anomalies. |
| ssl_critical_days | integer | – | Last SSL expiry warning, in days (1-365). |
| ssl_expiring | boolean | – | Email the user about SSL Certificate Expiring. |
| ssl_tls_changes | boolean | – | Email the user about SSL/TLS Changes. |
| ssl_urgent_days | integer | – | Second SSL expiry warning, in days (1-365). At least the critical days. |
| ssl_warning_days | integer | – | First SSL expiry warning, in days before expiry (1-365). At least the urgent days. |
No output schema declared.
No examples provided.
update_status_page Change a status page's settings ~423
Use this when the user wants to change an existing status page's name, description or custom domain, its colours or logo, what it displays (time zone, incident history, uptime days, subscribe form), or its search title and description. Changes one section at a time (general, branding, display or seo) with the editor's own checks and returns the section as saved; setting a custom domain returns the DNS record to create. The page's address (slug) never changes. Not for the services it shows: use add_status_page_component or update_status_page_component.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Only the settings to change. general: name, description (the same field as seo's meta_description: saving either sets both), custom_domain ("" removes it). branding: header_bg_color, header_text_colo… |
| section | string | yes | Which settings to change. |
| status_page | string | yes | The page's id, name or address. |
No output schema declared.
No examples provided.
update_status_page_component Change a status page component ~189
Use this when the user wants a service or group on one of their status pages renamed, described differently, moved into or out of a group, or moved up or down. Returns the component as saved and the page's components in order. Not for taking one off the page: use remove_status_page_component.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | The component's id or name, as get_status_page lists them. |
| description | string | – | The new text under the name; "" removes it. |
| group | string | – | The group to move it into, by name or id; "" moves it out of its group to the top level. |
| name | string | – | The new name visitors see. |
| order | integer | – | Its position within its group, or the top level: 0 is first. |
| status_page | string | yes | The page's id, name or address. |
No output schema declared.
No examples provided.
update_webhook Change a webhook ~309
Use this when the user wants a webhook or chat channel to get different alerts: rename it, change the events or sites it is sent, turn it off or on, or move a custom webhook to a new URL. Changes it as the Webhooks page's edit does and returns it as it is now; only the fields given change. Turning one on is held to the plan's active webhooks. Owners and admins only. Not for a chat channel's URL, its request headers or its signing secret, which stay on the Webhooks page, or for adding one (use add_webhook). The webhook format, events and signature are documented at https://flarewarden.com/docs/alerts/webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | False turns it off (nothing is sent until it is turned on), true turns it on. |
| events | array | – | The events it is sent, replacing the current ones, such as incident.started and incident.recovered (list_webhooks shows each webhook's; a chat channel is never sent monitor, maintenance or cron event… |
| every_site | boolean | – | True sends it every site's events again. |
| name | string | – | A new name. |
| sites | array | – | Send it only these sites' events, each by id, name or part of its URL. |
| url | string | – | For a custom webhook only: the new https endpoint. |
| webhook | string | yes | The webhook's id (from list_webhooks) or its name. |
No output schema declared.
No examples provided.
How do I install the FlareWarden MCP server?
FlareWarden is a hosted endpoint at https://mcp.flarewarden.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.flarewarden.com
claude mcp add --transport http com-flarewarden-website-monitoring 'https://mcp.flarewarden.com/mcp'
What is the FlareWarden MCP server?
FlareWarden is an MCP server listed in the public MCP registry as com.flarewarden/website-monitoring. Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages. This page covers its hosted endpoint (https://mcp.flarewarden.com/mcp).
Is the FlareWarden MCP server safe to use?
FlareWarden scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FlareWarden MCP server expose?
FlareWarden exposes 65 tools: check_service_status, check_service_status_url, recommend_monitoring, explain_features, search_help, and 60 more. Their descriptions and schemas cost roughly 14,073 tokens of context every time the server is loaded.
Does the FlareWarden MCP server require authentication?
No. We connected to FlareWarden without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FlareWarden MCP server still maintained?
FlareWarden is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FlareWarden MCP server?
VerifyMCP ran 13 checks on FlareWarden, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.