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 →
add_content_check Add the planned content check ~99
Use this when the user has confirmed a plan_content_check plan. Returns the content check created, with its id. Spends one monitor. Safe to repeat: the same plan id returns the first result. Not for changing an existing check: use update_monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_content_check plan's id. |
No output schema declared.
No examples provided.
add_cron_monitor Add the planned cron job monitor ~136
Use this when the user has confirmed a plan_cron_monitor plan. Returns the job's ping URL and ready-to-paste code for crontab, start/complete/fail reporting, GitHub Actions, a Kubernetes CronJob and a systemd timer. Spends one monitor. Safe to repeat: the same plan id returns the first result and the same URL. Not for changing an existing job's schedule: use update_monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_cron_monitor plan's id. |
No output schema declared.
No examples provided.
add_dependency Add the planned dependency ~112
Use this when the user has confirmed a plan_dependency plan for a site already monitored. Returns the dependency created, with its id and how it is watched. Spends one monitor. Safe to repeat: the same plan id returns the first result. Not for a dependency inside a plan_site plan: create_site adds those with the site.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_dependency plan's id. |
No output schema declared.
No examples provided.
add_dns_watch Add the planned DNS watch ~110
Use this when the user has confirmed a plan_dns_watch plan. Returns the watch with the values it starts from. It costs no monitors. Safe to repeat: the same plan id returns the first result. Not for removing or changing a watch: that is done on the site's DNS page, which the result links.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_dns_watch plan's id. |
No output schema declared.
No examples provided.
add_status_page_component Add a site or group to a status page ~249
Use this when the user wants another of their sites, or a group heading, shown on one of their status pages. Returns what was added: a site with the checks chosen under it, placed in a group if one is named. A site already on the page gains only the checks it did not show, and a group that exists is not added twice. Not for creating a page: use plan_status_page.
| Name | Type | Req | Description |
|---|---|---|---|
| children | array | – | Only these of the site's checks, by id or name. |
| description | string | – | Optional text visitors see under the name. |
| group | string | – | The group heading to put the site under, by name or id; created when the page has none of that name. |
| include_children | boolean | – | True to show every content check, dependency and cron job of the site under it. |
| name | string | – | The name visitors see; the site's name when left out. Required for a group. |
| site | string | – | The site to show, by id, name or part of its URL. Leave out to add a group heading named name. |
| status_page | string | yes | The page's id, name or address. |
No output schema declared.
No examples provided.
add_webhook Add a webhook ~363
Use this when the user wants FlareWarden to send alert events to their own HTTPS endpoint (a generic, signed JSON webhook), or to connect Slack, Discord, Google Chat or Microsoft Teams. Each event FlareWarden then sends there carries the monitor's name and URL and what happened, such as an incident's times and error message or a certificate's dates. For an endpoint: creates the webhook and returns a one-time link where the user sees its signing secret (the secret never appears in the chat). For a chat destination: returns the page where the user pastes the channel's webhook URL, which works as a password and is never a tool argument. Owners and admins only. Not for the user's own alert emails: use update_my_notifications. The webhook format, events and signature are documented at https://flarewarden.com/docs/alerts/webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | custom (default): the user's own HTTPS endpoint. slack, discord, googlechat or teams (Microsoft Teams): returns the page to connect that channel. |
| events | array | – | For destination custom, required: the events to send, at least one, such as incident.started and incident.recovered (the Webhooks page asks for them too). |
| idempotency_key | string | – | Optional. Send the same key again after a lost reply and the change is not made twice. |
| name | string | – | A name for the webhook, as the Webhooks page lists it. |
| sites | array | – | Limit the webhook to these sites, each by id, name or part of its URL. Leave out for every site. |
| url | string | – | For destination custom: the HTTPS endpoint. Never a Slack, Discord, Google Chat or Microsoft Teams URL. |
No output schema declared.
No examples provided.
apply_bulk_pause Pause or resume the planned sites ~125
Use this when the user has confirmed a plan_bulk_pause plan. Returns each site's outcome: paused or resumed, already so, or refused with the website's reason (a resume that does not fit the plan's running monitors is refused, the others still go ahead). Safe to repeat: the same plan id returns the first result. Not for deciding which sites: call plan_bulk_pause first.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_bulk_pause plan's id. |
No output schema declared.
No examples provided.
apply_dependency_change Change a dependency's components ~118
Use this when the user has confirmed a plan_dependency plan that changes which components of a dependency the site already watches, or how serious each is. Returns the dependency as it now watches. Spends no monitors. Safe to repeat: the same plan id returns the first result. Not for adding a dependency the site does not watch yet: add_dependency adds one.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_dependency plan's id. |
No output schema declared.
No examples provided.
cancel_maintenance Cancel a maintenance window ~133
Use this when the user calls off planned work: a scheduled or running maintenance window, or a recurring schedule as a whole. Cancels it as the dashboard's Maintenance page does; the subscribers who were told about it are emailed that it will not happen. Returns the cancelled window. A window already cancelled is left as it is. Not for an incident: use draft_incident_post with kind resolve.
| Name | Type | Req | Description |
|---|---|---|---|
| maintenance | string | yes | The window: its id from list_incidents with kind maintenance, or its title. |
| site | string | yes | The window's site: its id, name or part of its URL. |
No output schema declared.
No examples provided.
change_member_access Change which sites a member can see ~252
Use this when the user wants a monitor-only member, such as a client, to see more of the account's sites, to view or edit a site they can see, or to stop seeing one. Returns the sites the member can see after the change. A site is added at once, with no invitation or email; removing one asks the user to type the site's name where the client can show a form, as the team page does. Owners and admins only. Not for someone not on the team (use invite_member), an account-level member (change_member_role changes their role; the website makes one monitor-only only by removing them in the dashboard and inviting them again with sites), or a member's last site, whose removal removes them from the team (done in the dashboard).
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | view or edit: the member sees, or edits, these sites; a site they could not see is added. remove: they stop seeing the site. |
| member | string | yes | The member's email address, or their user id from list_team. |
| sites | array | yes | The sites to change, each by id, name or part of its URL. To remove, one site. |
No output schema declared.
No examples provided.
change_member_role Change a member's role ~183
Use this when the user wants a team member to have a different role (admin, editor or viewer) or to cover different monitors. Returns the member's old and new role; FlareWarden emails the member about the change. Owners and admins only: nobody changes their own role or the owner's, and only the owner changes an admin's. Not for inviting someone new (use invite_member) or removing a member (done in the dashboard).
| Name | Type | Req | Description |
|---|---|---|---|
| member | string | yes | The member's email address, or their user id from list_team. |
| role | string | yes | The new role: admin (everything but billing), editor (manages monitors in their scope) or viewer (sees everything and gets alerts). |
| scope | string | – | Which monitors the role covers. Leave out to keep the member's current scope (all for a monitor-only member). |
No output schema declared.
No examples provided.
check_service_status Check whether a service is down ~176
Use this when the user asks whether a third-party service such as Stripe, AWS, GitHub, Slack, OpenAI or Cloudflare is down, slow or having an outage, or why something that depends on one is failing. Returns what FlareWarden's public status page for the service shows: the vendor's own status page and FlareWarden's checks from several regions side by side, the verdict (the worse of the two), open and recent incidents, response times and 7, 30 and 90-day uptime. Covers hundreds of popular services, by name or domain. Not for a specific URL or the user's own website: use check_service_status_url.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | The service's name ("Stripe", "GitHub Actions"), its domain ("stripe.com") or its status page URL. |
No output schema declared.
No examples provided.
check_service_status_url Check whether a website is down ~215
Use this when the user asks whether a specific website, URL or API endpoint is down, unreachable or slow: "is my site down or is it just me?", "is api.example.com reachable from Europe?". Requests the URL once from six regions (Ashburn, San Jose, London, Frankfurt, Singapore and Sydney) and returns each region's result (up, down, blocked or inconclusive), status code and timings, with an overall verdict. A host is checked at most once every 5 minutes; a repeat returns that result and its age. Never returns page content. Not for named third-party services like Stripe or AWS: use check_service_status, which also reads the vendor's own status page. Not for a site the user monitors with FlareWarden: diagnose_site checks it from every region FlareWarden checks from, as its own monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website or endpoint to check, such as https://example.com or api.example.com/health. Query strings are ignored. |
No output schema declared.
No examples provided.
create_site Create the planned sites ~135
Use this when the user has confirmed a plan_site plan and its cost. Returns what was created for each site (the site, its page checks and dependencies, with ids), anything left out because the plan filled up, and what to set up next. Spends the monitors the plan priced. Safe to repeat: the same plan id returns the first result. Not for a plan the user has not seen: show them plan_site's summary first.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_site plan's id. |
No output schema declared.
No examples provided.
create_status_page Create the planned status page ~117
Use this when the user has confirmed a plan_status_page plan, including publishing it. Returns the new page's public address and what it shows. The page is public as soon as it is created. Safe to repeat: the same plan id returns the first result and never a second page. Not for changing an existing page: use update_status_page.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The plan's confirm sentence, exactly as returned; show it to the user first. |
| plan_id | string | yes | The plan_status_page plan's id. |
No output schema declared.
No examples provided.
diagnose_site Diagnose a site now ~227
Use this when one of the user's own sites is down, failing from some places, slow or alerting, and they want to know why right now, or want it checked from everywhere: "why is shop.acme.com down?", "is it failing everywhere or just in Asia?", "is our site reachable from every region?", "is it our certificate?". Requests the site once from every region FlareWarden checks from and returns each region's result, status code, DNS, connect, TLS and first-byte times, where a failure stopped, and the certificate's issuer and expiry, with a one-line finding such as "fails only from Singapore: TLS handshake timed out". At most 10 an hour for one site; a repeat within a minute returns the same result. Never returns page content. Not for past outages or why a site keeps alerting: use get_incident or review_noise. Not for a site outside the user's FlareWarden account: use check_service_status_url.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site: its id, name or part of its URL. |
No output schema declared.
No examples provided.
dismiss_anomaly Mark an anomaly as expected ~147
Use this when the user says an unusual response or run time was expected (a deploy, a sale, a migration). Returns the anomaly's new state. A dismissed anomaly no longer counts and is left out of future baselines; dismissed false restores it. Not for turning anomaly detection off: use set_anomaly_detection.
| Name | Type | Req | Description |
|---|---|---|---|
| dismissed | boolean | – | False to restore a dismissed anomaly; true by default. |
| event | integer | yes | The anomaly's event number, from set_anomaly_detection or get_site. |
| note | string | – | Why it was expected, up to 200 characters. |
| site | string | yes | The site, by id, name or part of its URL. |
No output schema declared.
No examples provided.
dismiss_suggestion Stop a suggestion ~99
Use this when the user says not to suggest something again: a status page, an alert channel, inviting a teammate, cron monitoring, subdomains or anomaly detection. Returns which suggestion is off. It stays off for this member in every assistant's conversations; the dashboard's own prompts are dismissed on the dashboard. Not for declining once: leaving a suggestion unanswered is enough.
| Name | Type | Req | Description |
|---|---|---|---|
| suggestion | string | yes | The suggestion's key, as results give it. |
No output schema declared.
No examples provided.
draft_incident_post Draft a status page incident post ~406
Use this when the user wants to tell customers about a problem on one of their sites: declare a new incident, post an update on one, or resolve one. Returns the exact text, every status page it will appear on, how many subscribers, members and webhooks will be notified, and any conflict (such as an incident already open on that site), with a draft id. Saves the draft and posts nothing. Not for reading what happened: use get_incident.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | For new: what the incident is about: site for the site itself (the default), or a dependency, content check or cron job of it by name or id. The first check named decides the incident's type. |
| incident | string | – | For update or resolve: the incident's id (list_incidents gives it). Leave out when the site has one open incident. |
| internal_only | boolean | – | For update: a note only the team sees; no status page shows it and nobody is emailed. |
| kind | string | yes | new declares an incident, update posts on an open one, resolve closes one. |
| message | string | – | For new (needed): the first public message. For update: the update. For resolve: an optional closing message. |
| severity | string | – | For new: critical (an outage: the site shows Down and the time counts as downtime), degraded (slow, or part of the site), or notify_only (shown, never counted as downtime, no subscriber email). Defau… |
| site | string | yes | The site: its id, name or part of its URL. |
| status | string | – | For update: where the incident stands. Default: its latest status. A new incident always starts as investigating. |
| title | string | – | For new (needed, as on the Incidents tab): the incident's public title, as the user wants it shown. |
No output schema declared.
No examples provided.
draft_maintenance Draft a maintenance window ~391
Use this when the user plans work on a site (a deploy, an upgrade, a migration) and wants it marked as maintenance, once or on a schedule, optionally telling status page subscribers. Returns the window in the user's time zone (and the next occurrences of a recurring one), the status pages it shows on and how many subscribers would be emailed, with a draft id. Saves the draft and schedules nothing. Not for an outage that is already happening: use draft_incident_post.
| Name | Type | Req | Description |
|---|---|---|---|
| day_of_month | integer | – | For monthly on a date: the day, 1 to 31. |
| days | array | – | For weekly or biweekly: the weekdays, such as saturday. Default: the weekday of when's date. |
| description | string | – | Optional details shown with the window. |
| duration_minutes | integer | yes | How long it lasts, 1 to 720 minutes (12 hours). |
| notify_subscribers | boolean | – | Email the status page subscribers about it. Only when the user asks; default false. |
| recurrence | string | – | none (once, the default), daily, weekly, biweekly or monthly. |
| site | string | yes | The site: its id, name or part of its URL. |
| timezone | string | – | The IANA time zone the time is in, such as Europe/London. Default: the user's own zone. |
| title | string | yes | What the work is, as subscribers will read it. |
| week_of_month | string | – | For monthly on a weekday: which one. |
| weekday | string | – | For monthly on a weekday: the day. |
| when | string | yes | When it starts: 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 such as 02:00. |
No output schema declared.
No examples provided.
explain_features Explain what FlareWarden does ~157
Use this when the user asks what FlareWarden can do or what it costs: "can FlareWarden watch cron jobs?", "how do you confirm an outage?", "what does a status page cost?", SSL certificate expiry, DNS changes, heartbeats, third-party dependencies, SLA and uptime reports, maintenance windows, alerts to Slack. Returns a catalogue of features (what each does, when it helps, how it works, its limits and plans) and the plans with their prices and limits. Pass a topic to get only the matching features; leave it out for all of them.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional: what the user asked about, such as "cron jobs", "status pages" or "false alarms". |
No output schema declared.
No examples provided.
get_account_overview Get the account overview ~141
Use this when starting any conversation about the user's own FlareWarden account, or when they ask what is wrong, what needs attention, or what they could set up next. It needs that account: on a connection not yet signed in, the call starts FlareWarden sign-in. Returns who is connected (account, plan, role, permissions), how much monitor room is left, sites by status, open incidents with how they were confirmed, an attention list worst-first, and up to three suggestions. Not for someone with no FlareWarden account who wants a site monitored. Not for another company's service status: use check_service_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_incident Get an incident with its evidence ~198
Use this when the user asks whether an outage was real, how it was confirmed, when it started and ended, what else it affected, or who was told. Returns the incident with its evidence: the regions that confirmed it and how, which region failed first and when, false alarms overturned around it, checks rolled into it, its updates, and who was notified (member emails, webhook deliveries, status page subscriber notices). Also what was happening outside the site at that time, with a one-line finding: the site's dependency checks by region, and for each third-party service it relies on, what the vendor's status page reported and what FlareWarden's own checks of that service recorded. Not for listing incidents: use list_incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| incident | string | yes | The incident id, from list_incidents or get_site. |
| site | string | yes | The incident's site: its id, name or part of its URL. |
No output schema declared.
No examples provided.
get_monitor_history Get recent checks ~257
Use this when the user asks what a site's recent checks, response times or failures looked like, or how a cron job, content check or dependency has been running. Returns the most recent checks of the site, or of one of its content checks, dependencies or cron jobs (runs, durations, late or failed runs), newest first. Not for uptime percentages or totals over a range: use get_report.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | – | A content check, dependency or cron job on the site, by id or name. Leave out for the site's own uptime checks. |
| from | string | – | Instead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339. Goes with to. A window is at most 90 days, within the history your plan keeps. |
| limit | integer | – | Most checks to return (default 25). |
| range | string | – | How far back (default 24h). |
| site | string | yes | The site's id, name or part of its URL. |
| to | string | – | Instead of range: where the window ends, a date (the whole day is included) or RFC 3339. |
No output schema declared.
No examples provided.
get_my_notifications Get my alert emails ~218
Use this when the user asks which alert emails they get from FlareWarden, or before changing them. Returns their own switches for this account: monitor_down (a monitor goes down), monitor_recovered (a monitor comes back up), ssl_expiring (warnings before an SSL certificate expires, at the ssl_expiry_warning_days), domain_expiring (reminders before a site's domain registration expires), certificate_changed (a site's SSL/TLS certificate has been replaced), issuer_changed (a certificate for the site's domain from an issuer it does not expect appears in public Certificate Transparency logs), ssl_tls_changes (protocol version or cipher suite changes), dns_failures (one switch for DNS resolution failures, changes to a site's DNS records and alerts from the DNS records the user watches), performance_anomalies (an unusual slowdown while the monitor is still up, for monitors with anomaly detection on); the master email switch; and their SSL expiry warning days. Not for webhooks or Slack, Discord, Google Chat and Microsoft Teams alerts: use list_webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_report Get an uptime report ~302
Use this when the user wants an uptime, SLA or incident report for a site, a group (an agency's client) or the whole account, for a week, month or quarter. Returns uptime over the time FlareWarden measured (unknown is shown as unknown), downtime minutes (the time that uptime counts as down), degraded minutes (affected but up, not downtime), incident count, longest incident and mean time to recover, response time p50 and p95, and certificate and domain expiry; for one site, also uptime, downtime and degraded time by day, response times over the range and each incident. Not for the latest checks: use get_monitor_history.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Instead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339. Goes with to. A window is at most 90 days, within the history your plan keeps. |
| group | string | – | For scope group: the group's exact name. |
| range | string | – | How far back (default 30d). Clamped to the history your plan keeps. |
| scope | string | yes | What the report covers. |
| site | string | – | For scope site: the site's id, name or part of its URL. |
| to | string | – | Instead of range: where the window ends, a date (the whole day is included) or RFC 3339. |
No output schema declared.
No examples provided.
get_site Get one site ~212
Use this when the user asks about one of their websites or APIs: is it up, why is it down, what is checked on it, when its certificate or domain expires. Returns status and last check; its content checks, dependencies and cron jobs (children, each with when it last and next runs, and a check's interval); SSL and domain expiry; anomaly detection; maintenance now and in the next 7 days; and open incidents; with include, its DNS records and DNS watches, the subdomains found in certificate logs, or the certificates those logs list for its domain and which issuers it expects. Not for past checks or uptime over a range: use get_monitor_history or get_report.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Extra sections: dns (the site's records and its DNS watches), subdomains (names found in certificate logs), certificates (certificates those logs list for the site's domain, and its certificate alert… |
| site | string | yes | The site's id, name or part of its URL. |
No output schema declared.
No examples provided.
get_status_page Get one status page ~104
Use this when the user asks what one of their status pages shows, which sites and checks are on it, or why its custom domain is not working. Returns the page with its components in order (with the ids the component tools take), its public URL, its subscriber count, and its custom domain's DNS record, verification and certificate state. Not for incidents posted on it: use list_incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| status_page | string | yes | The page's id or name. |
No output schema declared.
No examples provided.
get_usage Get plan usage and limits ~86
Use this when the user asks how many monitors they have left, what their plan includes, or why they cannot add more. Returns the monitor pool (used, allowed, left; websites, child checks and anomaly detection), status pages, seats, webhooks, subscribers, history kept and the fastest check interval. Not for which sites are down: use get_account_overview or list_sites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
invite_member Invite someone to the account ~316
Use this when the user wants to give a person access to their FlareWarden account: a teammate at a role (admin, editor or viewer), or a client who should see only some sites (a monitor-only invitation with sites). Emails the person an invitation link and returns exactly who was emailed; inviting the same address again replaces its pending invitation of the same kind (a site invitation only one for exactly the same sites) and emails it again. Owners and admins only; an admin cannot invite an admin. Not for changing the role of someone already on the team: use change_member_role.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The address to invite, exactly as the user gave it. | |
| idempotency_key | string | – | Optional. Send the same key again after a lost reply and the change is not made twice. |
| level | string | – | For a monitor-only invitation: view (default) or edit. |
| role | string | – | For an account invitation: admin (everything but billing), editor (manages monitors in their scope) or viewer (sees everything and gets alerts). Leave out for a monitor-only invitation. |
| scope | string | – | For an account invitation: which monitors the role covers. Default all. |
| site_checks | string | – | For a monitor-only invitation: which checks of each site are shared. Default all. |
| sites | array | – | For a monitor-only invitation: the sites to share, each by id, name or part of its URL. The person sees only these sites. |
No output schema declared.
No examples provided.
list_incidents List incidents and maintenance ~274
Use this when the user asks what went down, whether anything is down now, what happened last night or this month, or what maintenance is planned. Returns incidents (open or resolved, with how each was confirmed) or maintenance windows, for one site, a group or the account, newest first. Not for one incident's full evidence: use get_incident.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Instead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339. Goes with to. A window is at most 90 days, within the history your plan keeps. |
| group | string | – | Only sites in this group (exact name). |
| kind | string | – | Incidents or maintenance windows (default incident). |
| limit | integer | – | Most items to return (default 25). |
| range | string | – | How far back (default 30d). Clamped to the history your plan keeps. |
| site | string | – | Only this site: its id, name or part of its URL. |
| status | string | – | Open, resolved or both (default all). |
| to | string | – | Instead of range: where the window ends, a date (the whole day is included) or RFC 3339. |
No output schema declared.
No examples provided.
list_sites List monitored sites ~145
Use this when the user asks which websites or APIs they monitor, which are down, slow or paused, or what is in a group. Returns each site's status, last check, response time, 24-hour uptime, group, interval and SSL days left, filtered and paged. Not for one site's detail: use get_site.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The next_cursor of a previous page. |
| group | string | – | Only sites in this group (exact name). |
| limit | integer | – | Sites per page (default 50). |
| status | string | – | Only sites in this state. |
| text | string | – | Only sites whose name or URL contains this. |
No output schema declared.
No examples provided.
list_status_pages List status pages ~74
Use this when the user asks about their public status pages: which they have, their addresses, how many subscribers, or whether a custom domain works. Returns each page with its public URL, custom domain state, component and subscriber counts, and the plan's page limit. Not for another company's status: use check_service_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_team List the team ~102
Use this when the user asks who has access to the account, what roles people have, who was invited, or how many seats are left. Returns members with role, scope, the sites shared with them and when they joined and were last active (on the website or through an AI agent), pending invitations with the role or sites each gives, and seats used and allowed. Owners and admins only. Not for who was alerted about an incident: use get_incident.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhook_deliveries List a webhook's deliveries ~160
Use this when the user asks whether a webhook or chat channel got a particular alert, why one is failing, or what was sent to it lately. Returns its latest deliveries, newest first: each one's event, when, whether it arrived, the HTTP status, how long it took, which attempt it was and, for a failure, what went wrong in a few words. Never the payload or what the endpoint answered. Not for the account's webhooks as a whole (use list_webhooks) or sending one again (use retry_webhook_delivery).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many deliveries, newest first. Default 20. |
| webhook | string | yes | The webhook's id (from list_webhooks) or its name. |
No output schema declared.
No examples provided.
list_webhooks List webhooks and chat alerts ~101
Use this when the user asks where FlareWarden sends alerts besides email: their webhooks and Slack, Discord, Google Chat or Microsoft Teams channels, which events and sites each covers, and whether deliveries are failing. Returns each destination with its host (never the full URL, which often carries a credential), events, sites, active or paused, and delivery health. Owners and admins only. Not for the user's own alert emails: use get_my_notifications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_bulk_pause Plan pausing or resuming several sites ~238
Use this when the user wants to pause or resume several sites at once: a group, a list of sites, or every site, for example during a migration or a move to a new host. Returns exactly which sites would change, which are already paused or running, and which can't be changed (no permission, shared from another account, or no room on the plan to resume), with a plan id. Saves the plan and changes nothing in the account. Not for one site or one of its checks (use set_monitor_paused), or for planned work with an end time on one site (draft_maintenance).
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | True for every site the user can change. |
| answers | object | – | The user's answers, by decision id: which sites a name that matched several means. |
| group | string | – | Every site in this group. |
| paused | boolean | – | True to pause, false to resume. |
| plan_id | string | – | An earlier plan_bulk_pause plan, to answer its decisions. |
| sites | array | – | Sites by id, name or part of their URL, up to 100. |
No output schema declared.
No examples provided.
plan_content_check Plan a content check ~473
Use this when the user wants FlareWarden to watch what a page of their site says or shows: that a text or button is there, an error message is not, a price stays in a range, or the page changes. Returns the check tried against the live page right now (passes or not) and where the page holds its text, or the automatic checks that hold there when no check is named; any check of the site that already looks for the same text; its cost in monitors against the room the plan has left; and the decisions to put to the user: how serious a failure is and how often to check. Saves the plan and changes nothing in the account. Not for whether the site is up: plan_site watches that.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_recommended | boolean | – | True when the user asked FlareWarden to choose. |
| answers | object | – | The user's answers, by decision id: check, severity, interval, name. |
| attribute | string | – | For attribute_check: the attribute to read. |
| case_sensitive | boolean | – | Match the text's case exactly. |
| check_type | string | – | What to check. |
| max | number | – | For numeric_range or element_count: the highest value allowed. |
| min | number | – | For numeric_range or element_count: the lowest value allowed. |
| name | string | – | A name for the check. |
| page | string | – | The page's path on the site, such as /pricing; the home page by default. |
| plan_id | string | – | An earlier plan_content_check plan, to change it or answer its decisions. |
| selector | string | – | A CSS selector narrowing where to look, such as #buy-button (no :has()); an empty string clears it. A plan of a text with no selector lists each place the page shows it, with a selector for each; a f… |
| site | string | – | The site, by id, name or part of its URL. |
| text | string | – | The text (or, for regex, the pattern) the check looks for. |
No output schema declared.
No examples provided.
plan_cron_monitor Plan a cron job monitor ~299
Use this when the user wants to know if a scheduled job, backup, queue worker or other background task stops running, runs late or fails. Returns the schedule understood (with the next five runs in the user's time zone), its cost in monitors against the room the plan has left, and the decisions to put to the user: when the job runs, if the schedule given could not be read; then how late is too late (with a recommended grace period), the longest normal run and how serious a miss is. Cron expressions are read in UTC: there is no time zone setting. Saves the plan and changes nothing in the account. Not for checking a website or API endpoint: use plan_site.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_recommended | boolean | – | True when the user asked FlareWarden to choose. |
| answers | object | – | The user's answers, by decision id: schedule, interval, grace, max_run, severity. |
| job | string | – | What the job is, as the user put it, such as nightly backup. |
| plan_id | string | – | An earlier plan_cron_monitor plan, to change it or answer its decisions. |
| schedule | string | – | When it runs: a cron expression (read in UTC), every N minutes, hours or days, or heartbeat for a process that checks in. |
| site | string | – | The site the job belongs to, by id, name or part of its URL. |
No output schema declared.
No examples provided.
plan_dependency Plan a dependency ~512
Use this when the user wants FlareWarden to watch a third-party service a site relies on (a cloud provider, CDN, payment, email or auth service), either while planning a new site or for a site already monitored. A service FlareWarden's catalogue does not list is watched through its status page (url), or a URL checked over plain HTTP. Returns how the service will be watched (its status page integration, or a plain HTTP check), its cost in monitors against the room the plan has left, then the decisions one step at a time: regions (recommended from the site's DNS), which components count, then, once they are chosen, how serious each one's failure is; the interval is the recommended one unless the user names another. Credentials such as an API token are entered on a secure link it returns, never in the chat. Saves the plan and changes nothing in the account. Not for checking whether a service is down right now: use check_service_status.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_recommended | boolean | – | True when the user asked FlareWarden to choose: every open decision that has a recommendation takes it. Never covers credentials. |
| answers | object | – | The user's answers, by decision id (deps.<service>.regions, .components, .severity.<component>, .interval, .url), or service when choosing among detected ones. |
| component_query | string | – | Searches a long component list (more than 50) by name. |
| dependency | string | – | The service: its key from a plan_site plan, or its name, such as Stripe or AWS, or a service the catalogue does not list (with url). On a one-site plan_site plan, a service detection did not find is… |
| integration | string | – | The integration to use when the user said which (their own monitoring's status page). |
| plan_id | string | – | A plan_site plan (with dependency, the service's key from it) or an earlier plan_dependency plan. |
| regions | array | – | Region ids the site runs in for this service, such as iad or us-east-1, when the user's code or the user says so: the service's locations there are recommended. |
| site | string | – | A site already monitored, by id, name or part of its URL, to add the dependency to. |
| url | string | – | The service's status page, or a URL to check over plain HTTP, when the user gave one. |
No output schema declared.
No examples provided.
plan_dns_watch Plan a DNS watch ~314
Use this when the user wants to know if DNS records under one of their sites change or stop resolving: their MX records, _dmarc, SPF, or the CNAME a subdomain points at (such as www pointing at Vercel). Returns the name's values today for the record types asked (or all of them), and the decisions to put to the user: which record types, and whether to alert when the values change or when the name stops resolving. Watches cost no monitors; a site can have 20. Saves the plan and changes nothing in the account. Not for the site's own uptime, DNS health or certificate: FlareWarden checks those already.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_recommended | boolean | – | True when the user asked FlareWarden to choose. |
| answers | object | – | The user's answers, by decision id: record_types, alert_on. |
| host | string | – | The name to watch: a label under the site's domain (www, _dmarc, mail), @ for the domain itself, or a full name such as mail.acme.com. |
| plan_id | string | – | An earlier plan_dns_watch plan, to answer its decisions. |
| record_types | array | – | The record types to watch: A, AAAA, CNAME, MX, TXT, NS or CAA. Leave out to see them all and decide. |
| site | string | – | The site whose domain the name is under, by id, name or part of its URL. |
No output schema declared.
No examples provided.
plan_site Plan monitoring for websites ~496
Use this when the user wants FlareWarden to monitor a website or API they run, or up to 50 of them at once. Returns a plan: what each site runs on (hosting, CDN, cloud regions, payments and other services, found from its DNS and page), which automatic page checks hold on it now, and the decisions to put to the user with recommendations and their cost in monitors. Saves the plan and changes nothing in the account; call again with the plan id and the user's answers. Not for adding a check to a site already monitored: use plan_dependency, plan_content_check or plan_cron_monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_recommended | boolean | – | True when the user asked FlareWarden to choose: every open decision that has a recommendation takes it. |
| answers | object | – | The user's answers, by decision id: services, checks, interval, group, anomaly, fit, exclude_sites, and deps.<service>.* for a service's configuration. Also timeout, never asked: the seconds each sit… |
| component_query | string | – | Searches a dependency's long component list (more than 50) by name. |
| from_workspace | array | – | For one site only: services the site uses that are visible in the user's own workspace and not from outside, such as its infrastructure config, package manifests or environment variable names. Each i… |
| group | string | – | A group to put the sites in. |
| name | string | – | The site's name, for one site; the host name by default. |
| plan_id | string | – | An earlier plan_site plan's id, to read it again or answer its decisions. |
| url | string | – | The site's URL, such as https://acme.com, for one site. |
| urls | array | – | Up to 50 site URLs, for adding many at once. |
No output schema declared.
No examples provided.
plan_status_page Plan a status page ~329
Use this when the user wants a public status page for their customers, made from one of their sites or empty. Returns a suggested address (with free alternatives when one is taken), the branding found on the site, the components the page would show grouped as the editor groups them, what the plan allows (components per page, custom domains), and the decisions for the user: the address, which of the site's services to show, and whether to publish. Saves the plan and changes nothing in the account. Not for another company's status: use check_service_status.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_recommended | boolean | – | True when the user asked FlareWarden to choose. It never publishes: that needs the user's yes. |
| answers | object | – | The user's answers, by decision id: name, slug, dependencies (ids to show), publish (true once the user confirms creating the public page). |
| brand_color | string | – | The user's brand colour as #rrggbb, if they gave one: the page's colours are made from it instead of the colour found on the site. A page made from a site only. |
| from_site | string | – | The site to make the page from, by id, name or part of its URL. Leave out for an empty page. |
| name | string | – | The page's name, if the user gave one. |
| plan_id | string | – | An earlier plan_status_page plan, to answer its decisions. |
| slug | string | – | The page's address, if the user gave one: the part before .status.flarewarden.com. |
No output schema declared.
No examples provided.
publish_incident_post Publish a drafted incident post ~140
Use this when the user has approved a draft_incident_post draft's exact text and recipients. Posts it as the dashboard's Incidents tab does: it shows on the status pages and FlareWarden emails the subscribers, members and webhooks the draft named. Returns the incident. Safe to repeat: the same draft id posts once and returns the first result. Not for changing the text: make a new draft.
| 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_incident_post (it starts with pl_). |
No output schema declared.
No examples provided.
recommend_monitoring Recommend what to monitor for a website ~251
Use this when the user asks what they should monitor for a website, what could take their site down, or which third-party services (hosting, CDN, DNS, payments, email, analytics) a site depends on, and when someone with no FlareWarden account asks what monitoring a site would get before signing up. Reads the site's DNS records, home page and certificate and checks it from six regions. Returns the services it recognizes with the evidence for each and their status now, the certificate's expiry, a DNS summary, whether the site is up now, the page checks that would work on it, and what FlareWarden would create and how many monitors that is, on each FlareWarden plan. Needs no sign-in and stores nothing about the user; results are cached per site for a day. Not for whether a site is up right now on its own: use check_service_status_url. Not for creating monitoring: once the user is signed in, the account tools plan and create it. What it detects is documented at https://flarewarden.com/docs/smart-setup.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website to analyze, such as https://example.com or example.com. |
No output schema declared.
No examples provided.
remove_status_page_component Remove a component from a status page ~221
Use this when the user wants a site, check or group heading taken off one of their public status pages. A site goes with its own content, dependency and cron rows, wherever they are placed. A group goes alone and its items move to the top level where it was, unless group_contents is remove, which takes everything in it off the page too. The sites and checks themselves stay monitored. Returns what was removed and the page's components after. Not for deleting a site, a check or the page itself, which is done in the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | The component's id or name, as get_status_page lists them. |
| group_contents | string | – | For a group only. keep (the default): only the group goes, and its items stay on the page at the top level where it was. remove: everything in the group comes off the page too, each item as removing… |
| status_page | string | yes | The page's id, name or address. |
No output schema declared.
No examples provided.
rename_account Rename the account ~101
Use this when the user wants the FlareWarden account's own name changed: the name its members see in the sidebar and account switcher, and invitations carry. Renames it as the Account page does and returns the old and new name. Owners and admins only. Not for a site's name (use update_monitor) or a status page's (use update_status_page).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The new name, 1 to 100 characters. |
No output schema declared.
No examples provided.
retry_webhook_delivery Send a webhook delivery again ~117
Use this when the user wants a delivery a webhook or chat channel missed sent again, once the endpoint is fixed. Sends the same event again as a new attempt, as the Webhooks page's Retry does, and returns whether it arrived and the HTTP status. Owners and admins only. Not for a test event (use test_webhook).
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | string | yes | The delivery's id, from list_webhook_deliveries. |
| webhook | string | yes | The webhook's id (from list_webhooks) or its name. |
No output schema declared.
No examples provided.
review_coverage Review what is not monitored ~218
Use this when the user asks what they are not monitoring, what could break without them knowing, whether their monitoring is complete, or what to set up next. Returns the gaps in what the user can see, worst first, each with the tool that fixes it and, where the user may turn that suggestion off, the dismiss_suggestion key: services FlareWarden found a site relying on that no dependency watches, certificates expiring within 30 days (tracked subdomains included), sites on no status page, sites whose alerts reach one person or nobody, and monitors paused for weeks. Changes nothing in the account. A site whose services FlareWarden has not looked at in the last week has its DNS records and home page read in the background, and a later call includes what that finds. Not for what is down now: use get_account_overview.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Only sites in this group (exact name). |
| site | string | – | Only this site: its id, name or part of its URL. |
No output schema declared.
No examples provided.
review_noise Review noisy monitors ~207
Use this when the user asks why a site keeps alerting, which monitors are noisy or flapping, whether alerts were false alarms, or how to get fewer pointless alerts: "why does FlareWarden keep emailing us about the API?", "which of our monitors are flaky?". Returns, over the last 7 and 30 days for the sites the user can see, worst first: alerts for outages the next check found over, content checks, dependencies and cron jobs that alert often, anomaly alerts, sites whose status keeps changing, and failed checks other regions overturned as false alarms (by region); each with a suggested change and the tool that makes it. Changes nothing. Not for what is down now: use get_account_overview or diagnose_site. Not for what is not monitored: use review_coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Only sites in this group (exact name). |
| site | string | – | Only this site: its id, name or part of its URL. |
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.