MCP servers › com.flarewarden › website-monitoring

MCP server · registry snapshot 2026-11-02 · last tested 2026-11-02

com.flarewarden/website-monitoring

FlareWarden — the publisher's title

by flarewarden.com · domain (the registry's namespace rule)Website ↗

Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-02version 0.1.0streamable HTTP65 tools

Summary

com.flarewarden/website-monitoring is a remote MCP server listed in the official MCP registry at version 0.1.0, under the namespace of the domain flarewarden.com. On 2026-11-02 ProtocolProbe connected to it in read-only mode and read its inventory: 65 tools, 10 resources and 5 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Tools: 65
Last tested: 2026-11-02

Tool list size

27,626 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (65 tools). Counted with Anthropic's token counter on 2026-11-02, from the tool list we read on 2026-11-02. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-02 (mcp.flarewarden.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.1.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 28 tools whose name or declaration suggests they change data (revoke_invitation, change_member_role, change_member_access, rename_account, update_my_notifications and 23 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-02.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-11-02
Mode: read-only (no tool calls)
Latest version: 0.1.0, published 2026-11-01 (registry, as of the 2026-11-02 snapshot)
First listed version: 2026-11-01 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-11-02
Package and repository: checked 2026-11-02
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-01, listed on 2026-11-02 with version 0.1.0 (published 2026-11-01).

Source: the official MCP Registry list on 2026-11-01 and on 2026-11-02.

What it is

What does this server offer?

Observed inventory

65tools

10resources

5prompts

None of its 65 tools are described as changing anything. For 65 the reading was uncertain, so no mark is shown.

check_service_statuson 2 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- servicestringrequired“The service's name ("Stripe", "GitHub Actions"), its domain ("stripe.com") or its status page URL.”
check_service_status_url
“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?".”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- urlstringrequired“The website or endpoint to check, such as https://example.com or api.example.com/health.”
recommend_monitoring
“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, a…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- urlstringrequired“The website to analyze, such as https://example.com or example.com.”
explain_features
“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…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input
- topicstring“Optional: what the user asked about, such as "cron jobs", "status page pricing" or "false alarms".”
search_helpon 11 other servers
“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 inviti…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- limitinteger“How many passages to return (default 5).”
- querystringrequired“The question or keywords, in the user's words.”
get_account_overviewon 3 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
get_usageon 106 other servers
“Use this when the user asks how many monitors they have left, what their plan includes, or why they cannot add more.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
list_siteson 44 other servers
“Use this when the user asks which websites or APIs they monitor, which are down, slow or paused, or what is in a group.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
5 inputs
- cursorstring“The next_cursor of a previous page.”
- groupstring“Only sites in this group (exact name).”
- limitinteger“Sites per page (default 50).”
- statusstring“Only sites in this state.”
- textstring“Only sites whose name or URL contains this.”
get_siteon 28 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- includearray“Extra sections: dns (the site's records and its DNS watches), subdomains (names found in certificate logs), certificates (certificates those logs list for the …”
- sitestringrequired“The site's id, name or part of its URL.”
get_monitor_historyon 1 other server
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
6 inputs, 1 required
- checkstring“A content check, dependency or cron job on the site, by id or name.”
- fromstring“Instead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339.”
- limitinteger“Most checks to return (default 25).”
- rangestring“How far back (default 24h).”
- sitestringrequired“The site's id, name or part of its URL.”
- tostring“Instead of range: where the window ends, a date (the whole day is included) or RFC 3339.”
get_reporton 69 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
6 inputs, 1 required
- fromstring“Instead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339.”
- groupstring“For scope group: the group's exact name.”
- rangestring“How far back (default 30d).”
- scopestringrequired“What the report covers.”
- sitestring“For scope site: the site's id, name or part of its URL.”
- tostring“Instead of range: where the window ends, a date (the whole day is included) or RFC 3339.”
list_incidentson 13 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
8 inputs
- fromstring“Instead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339.”
- groupstring“Only sites in this group (exact name).”
- kindstring“Incidents or maintenance windows (default incident).”
- limitinteger“Most items to return (default 25).”
- rangestring“How far back (default 30d).”
- sitestring“Only this site: its id, name or part of its URL.”
- statusstring“Open, resolved or both (default all).”
- tostring“Instead of range: where the window ends, a date (the whole day is included) or RFC 3339.”

Show 53 more tools

get_incidenton 12 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 2 required
- incidentstringrequired“The incident id, from list_incidents or get_site.”
- sitestringrequired“The incident's site: its id, name or part of its URL.”
diagnose_site
“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?", "…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- sitestringrequired“The site: its id, name or part of its URL.”
review_coverage
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs
- groupstring“Only sites in this group (exact name).”
- sitestring“Only this site: its id, name or part of its URL.”
review_noise
“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 emailin…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs
- groupstring“Only sites in this group (exact name).”
- sitestring“Only this site: its id, name or part of its URL.”
list_status_pageson 7 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
get_status_pageon 4 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input, 1 required
- status_pagestringrequired“The page's id or name.”
list_teamon 4 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
search_service_catalog
“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).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input, 1 required
- querystringrequired“The service's name, such as Stripe or AWS.”
invite_memberon 8 other servers
“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 invitatio…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
7 inputs, 1 required
- emailstringrequired“The address to invite, exactly as the user gave it.”
- idempotency_keystring“Optional.”
- levelstring“For a monitor-only invitation: view (default) or edit.”
- rolestring“For an account invitation: admin (everything but billing), editor (manages monitors in their scope) or viewer (sees everything and gets alerts).”
- scopestring“For an account invitation: which monitors the role covers.”
- site_checksstring“For a monitor-only invitation: which checks of each site are shared.”
- sitesarray“For a monitor-only invitation: the sites to share, each by id, name or part of its URL.”
revoke_invitationon 2 other servers
“Use this when the user wants to withdraw an invitation that has not been accepted yet.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- invitationstringrequired“The invitation's id (from list_team) or the invited email address.”
change_member_role
“Use this when the user wants a team member to have a different role (admin, editor or viewer) or to cover different monitors.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 2 required
- memberstringrequired“The member's email address, or their user id from list_team.”
- rolestringrequired“The new role: admin (everything but billing), editor (manages monitors in their scope) or viewer (sees everything and gets alerts).”
- scopestring“Which monitors the role covers.”
change_member_access
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
3 inputs, 3 required
- accessstringrequired“view or edit: the member sees, or edits, these sites; a site they could not see is added.”
- memberstringrequired“The member's email address, or their user id from list_team.”
- sitesarrayrequired“The sites to change, each by id, name or part of its URL.”
rename_account
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- namestringrequired“The new name, 1 to 100 characters.”
get_my_notificationson 1 other server
“Use this when the user asks which alert emails they get from FlareWarden, or before changing them.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
update_my_notifications
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
13 inputs
- certificate_changedboolean“Email the user about Certificate Changed.”
- dns_failuresboolean“Email the user about DNS Failures and Changes.”
- domain_expiringboolean“Email the user about Domain Expiring.”
- email_alertsboolean“The master switch: false pauses every alert email to the user from this account.”
- issuer_changedboolean“Email the user about Certificate Issuer Changed.”
- monitor_downboolean“Email the user about Monitor Down.”
- monitor_recoveredboolean“Email the user about Monitor Recovered.”
- performance_anomaliesboolean“Email the user about Performance Anomalies.”
- ssl_critical_daysinteger“Last SSL expiry warning, in days (1-365).”
- ssl_expiringboolean“Email the user about SSL Certificate Expiring.”
- ssl_tls_changesboolean“Email the user about SSL/TLS Changes.”
- ssl_urgent_daysinteger“Second SSL expiry warning, in days (1-365).”
- ssl_warning_daysinteger“First SSL expiry warning, in days before expiry (1-365).”
list_webhookson 62 other servers
“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 d…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.
list_webhook_deliverieson 8 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- limitinteger“How many deliveries, newest first.”
- webhookstringrequired“The webhook's id (from list_webhooks) or its name.”
add_webhookon 1 other server
“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.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs
- destinationstring“custom (default): the user's own HTTPS endpoint.”
- eventsarray“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_keystring“Optional.”
- namestring“A name for the webhook, as the Webhooks page lists it.”
- sitesarray“Limit the webhook to these sites, each by id, name or part of its URL.”
- urlstring“For destination custom: the HTTPS endpoint.”
update_webhookon 22 other servers
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
7 inputs, 1 required
- enabledboolean“False turns it off (nothing is sent until it is turned on), true turns it on.”
- eventsarray“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…”
- every_siteboolean“True sends it every site's events again.”
- namestring“A new name.”
- sitesarray“Send it only these sites' events, each by id, name or part of its URL.”
- urlstring“For a custom webhook only: the new https endpoint.”
- webhookstringrequired“The webhook's id (from list_webhooks) or its name.”
test_webhookon 23 other servers
“Use this when the user wants to check that a webhook or chat channel receives FlareWarden's alerts.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- webhookstringrequired“The webhook's id (from list_webhooks) or its name.”
retry_webhook_deliveryon 1 other server
“Use this when the user wants a delivery a webhook or chat channel missed sent again, once the endpoint is fixed.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- deliverystringrequired“The delivery's id, from list_webhook_deliveries.”
- webhookstringrequired“The webhook's id (from list_webhooks) or its name.”
search_audit_log
“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.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
6 inputs
- actionstring“Only this action, as entries name it (for example monitor.pause or invitation.create).”
- fromstring“Only entries on or after this date, YYYY-MM-DD.”
- memberstring“Only changes made by this member, by email address.”
- pageinteger“Page of results, 25 a page.”
- textstring“Words to find in the entry: a site or member name, an email address, an action such as "paused".”
- tostring“Only entries on or before this date, YYYY-MM-DD.”
plan_site
“Use this when the user wants FlareWarden to monitor a website or API they run, or up to 50 of them at once.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs
- accept_recommendedboolean“True when the user asked FlareWarden to choose: every open decision that has a recommendation takes it.”
- answersobject“The user's answers, by decision id: services, checks, interval, group, anomaly, fit, exclude_sites, and deps.<service>.* for a service's configuration.”
- component_querystring“Searches a dependency's long component list (more than 50) by name.”
- from_workspacearray“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 manifes…”
- groupstring“A group to put the sites in.”
- namestring“The site's name, for one site; the host name by default.”
- plan_idstring“An earlier plan_site plan's id, to read it again or answer its decisions.”
- urlstring“The site's URL, such as https://acme.com, for one site.”
- urlsarray“Up to 50 site URLs, for adding many at once.”
create_siteon 21 other servers
“Use this when the user has confirmed a plan_site plan and its cost.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_site plan's id.”
plan_dependency
“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 alread…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs
- accept_recommendedboolean“True when the user asked FlareWarden to choose: every open decision that has a recommendation takes it.”
- answersobject“The user's answers, by decision id (deps.<service>.regions, .components, .severity.<component>, .interval, .url), or service when choosing among detected ones.”
- component_querystring“Searches a long component list (more than 50) by name.”
- dependencystring“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).”
- integrationstring“The integration to use when the user said which (their own monitoring's status page).”
- plan_idstring“A plan_site plan (with dependency, the service's key from it) or an earlier plan_dependency plan.”
- regionsarray“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.”
- sitestring“A site already monitored, by id, name or part of its URL, to add the dependency to.”
- urlstring“The service's status page, or a URL to check over plain HTTP, when the user gave one.”
add_dependencyon 1 other server
“Use this when the user has confirmed a plan_dependency plan for a site already monitored.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_dependency plan's id.”
apply_dependency_change
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_dependency plan's id.”
plan_content_check
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
13 inputs
- accept_recommendedboolean“True when the user asked FlareWarden to choose.”
- answersobject“The user's answers, by decision id: check, severity, interval, name.”
- attributestring“For attribute_check: the attribute to read.”
- case_sensitiveboolean“Match the text's case exactly.”
- check_typestring“What to check.”
- maxnumber“For numeric_range or element_count: the highest value allowed.”
- minnumber“For numeric_range or element_count: the lowest value allowed.”
- namestring“A name for the check.”
- pagestring“The page's path on the site, such as /pricing; the home page by default.”
- plan_idstring“An earlier plan_content_check plan, to change it or answer its decisions.”
- selectorstring“A CSS selector narrowing where to look, such as #buy-button (no :has()); an empty string clears it.”
- sitestring“The site, by id, name or part of its URL.”
- textstring“The text (or, for regex, the pattern) the check looks for.”
add_content_check
“Use this when the user has confirmed a plan_content_check plan.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_content_check plan's id.”
plan_cron_monitor
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
- accept_recommendedboolean“True when the user asked FlareWarden to choose.”
- answersobject“The user's answers, by decision id: schedule, interval, grace, max_run, severity.”
- jobstring“What the job is, as the user put it, such as nightly backup.”
- plan_idstring“An earlier plan_cron_monitor plan, to change it or answer its decisions.”
- schedulestring“When it runs: a cron expression (read in UTC), every N minutes, hours or days, or heartbeat for a process that checks in.”
- sitestring“The site the job belongs to, by id, name or part of its URL.”
add_cron_monitor
“Use this when the user has confirmed a plan_cron_monitor plan.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_cron_monitor plan's id.”
update_monitoron 11 other servers
“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, descript…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
22 inputs, 1 required
- attributestring“A content check's attribute to read, for attribute_check.”
- case_sensitiveboolean“Whether a content check matches case exactly.”
- checkstring“One of the site's content checks, dependencies or cron jobs, by id or name; leave out to change the site itself.”
- check_typestring“A content check's kind.”
- descriptionstring“A check's description.”
- expected_textstring“A plain HTTP dependency's text its answer must hold (or, with match, must not hold or match); an empty string stops checking it.”
- graceinteger“A cron job's grace period in seconds.”
- groupstring“A site's group; an empty string removes it.”
- intervalinteger“Seconds between checks (30, 60, 300, 600, 1800 or 3600, as the plan allows).”
- matchstring“How expected_text is matched.”
- maxnumber“A content check's highest value allowed, for numeric_range or element_count.”
- max_runinteger“A cron job's longest normal run in seconds; 0 turns it off.”
- minnumber“A content check's lowest value allowed, for numeric_range or element_count.”
- namestring“The site's new name, or with check, the check's.”
- pagestring“A content check's page path.”
- schedulestring“A cron job's schedule: a cron expression (UTC), every N minutes, hours or days, or heartbeat.”
- selectorstring“A content check's CSS selector.”
- severitystring“How serious a failure is.”
- sitestringrequired“The site, by id, name or part of its URL.”
- textstring“A content check's text or pattern.”
- timeoutinteger“Seconds a site's checks wait for an answer before they count as failed (5, 10, 15 or 30; 10 unless changed).”
- urlstring“A plain HTTP dependency's URL; a status page dependency is changed with plan_dependency.”
set_monitor_paused
“Use this when the user wants to stop or restart checks of a site or one of its checks, for example during planned work.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
3 inputs, 2 required
- checkstring“One of the site's content checks, dependencies or cron jobs, by id or name; leave out for the whole site.”
- pausedbooleanrequired“True to pause, false to resume.”
- sitestringrequired“The site, by id, name or part of its URL.”
plan_bulk_pause
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
- allboolean“True for every site the user can change.”
- answersobject“The user's answers, by decision id: which sites a name that matched several means.”
- groupstring“Every site in this group.”
- pausedboolean“True to pause, false to resume.”
- plan_idstring“An earlier plan_bulk_pause plan, to answer its decisions.”
- sitesarray“Sites by id, name or part of their URL, up to 100.”
apply_bulk_pause
“Use this when the user has confirmed a plan_bulk_pause plan.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_bulk_pause plan's id.”
set_anomaly_detection
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs, 2 required
- checkstring“A cron job on the site, by id or name; leave out for the site's response times.”
- enabledbooleanrequired“True to turn it on (or change sensitivity), false to turn it off.”
- sensitivitystring“low (fewer alerts), normal or high.”
- sitestringrequired“The site, by id, name or part of its URL.”
dismiss_anomaly
“Use this when the user says an unusual response or run time was expected (a deploy, a sale, a migration).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs, 2 required
- dismissedboolean“False to restore a dismissed anomaly; true by default.”
- eventintegerrequired“The anomaly's event number, from set_anomaly_detection or get_site.”
- notestring“Why it was expected, up to 200 characters.”
- sitestringrequired“The site, by id, name or part of its URL.”
track_subdomain_certificate
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
3 inputs, 2 required
- sitestringrequired“The site the subdomain was found under, by id, name or part of its URL.”
- subdomainstringrequired“The subdomain, such as api.acme.com, or its id.”
- trackedboolean“False to stop tracking; true by default.”
plan_dns_watch
“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 Verce…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs
- accept_recommendedboolean“True when the user asked FlareWarden to choose.”
- answersobject“The user's answers, by decision id: record_types, alert_on.”
- hoststring“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_idstring“An earlier plan_dns_watch plan, to answer its decisions.”
- record_typesarray“The record types to watch: A, AAAA, CNAME, MX, TXT, NS or CAA.”
- sitestring“The site whose domain the name is under, by id, name or part of its URL.”
add_dns_watch
“Use this when the user has confirmed a plan_dns_watch plan.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_dns_watch plan's id.”
dismiss_suggestionon 1 other server
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- suggestionstringrequired“The suggestion's key, as results give it.”
plan_status_page
“Use this when the user wants a public status page for their customers, made from one of their sites or empty.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs
- accept_recommendedboolean“True when the user asked FlareWarden to choose.”
- answersobject“The user's answers, by decision id: name, slug, dependencies (ids to show), publish (true once the user confirms creating the public page).”
- brand_colorstring“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.”
- from_sitestring“The site to make the page from, by id, name or part of its URL.”
- namestring“The page's name, if the user gave one.”
- plan_idstring“An earlier plan_status_page plan, to answer its decisions.”
- slugstring“The page's address, if the user gave one: the part before .status.flarewarden.com.”
create_status_pageon 4 other servers
“Use this when the user has confirmed a plan_status_page plan, including publishing it.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- plan_idstringrequired“The plan_status_page plan's id.”
update_status_pageon 3 other servers
“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), …”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
3 inputs, 3 required
- fieldsobjectrequired“Only the settings to change.”
- sectionstringrequired“Which settings to change.”
- status_pagestringrequired“The page's id, name or address.”
add_status_page_component
“Use this when the user wants another of their sites, or a group heading, shown on one of their status pages.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
7 inputs, 1 required
- childrenarray“Only these of the site's checks, by id or name.”
- descriptionstring“Optional text visitors see under the name.”
- groupstring“The group heading to put the site under, by name or id; created when the page has none of that name.”
- include_childrenboolean“True to show every content check, dependency and cron job of the site under it.”
- namestring“The name visitors see; the site's name when left out.”
- sitestring“The site to show, by id, name or part of its URL.”
- status_pagestringrequired“The page's id, name or address.”
update_status_page_componenton 1 other server
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
6 inputs, 2 required
- componentstringrequired“The component's id or name, as get_status_page lists them.”
- descriptionstring“The new text under the name; "" removes it.”
- groupstring“The group to move it into, by name or id; "" moves it out of its group to the top level.”
- namestring“The new name visitors see.”
- orderinteger“Its position within its group, or the top level: 0 is first.”
- status_pagestringrequired“The page's id, name or address.”
remove_status_page_component
“Use this when the user wants a site, check or group heading taken off one of their public status pages.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
3 inputs, 2 required
- componentstringrequired“The component's id or name, as get_status_page lists them.”
- group_contentsstring“For a group only.”
- status_pagestringrequired“The page's id, name or address.”
draft_incident_post
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs, 2 required
- componentsarray“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.”
- incidentstring“For update or resolve: the incident's id (list_incidents gives it).”
- internal_onlyboolean“For update: a note only the team sees; no status page shows it and nobody is emailed.”
- kindstringrequired“new declares an incident, update posts on an open one, resolve closes one.”
- messagestring“For new (needed): the first public message.”
- severitystring“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 …”
- sitestringrequired“The site: its id, name or part of its URL.”
- statusstring“For update: where the incident stands.”
- titlestring“For new (needed, as on the Incidents tab): the incident's public title, as the user wants it shown.”
publish_incident_post
“Use this when the user has approved a draft_incident_post draft's exact text and recipients.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- draft_idstringrequired“The draft's id from draft_incident_post (it starts with pl_).”
draft_maintenance
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
12 inputs, 4 required
- day_of_monthinteger“For monthly on a date: the day, 1 to 31.”
- daysarray“For weekly or biweekly: the weekdays, such as saturday.”
- descriptionstring“Optional details shown with the window.”
- duration_minutesintegerrequired“How long it lasts, 1 to 720 minutes (12 hours).”
- notify_subscribersboolean“Email the status page subscribers about it.”
- recurrencestring“none (once, the default), daily, weekly, biweekly or monthly.”
- sitestringrequired“The site: its id, name or part of its URL.”
- timezonestring“The IANA time zone the time is in, such as Europe/London.”
- titlestringrequired“What the work is, as subscribers will read it.”
- week_of_monthstring“For monthly on a weekday: which one.”
- weekdaystring“For monthly on a weekday: the day.”
- whenstringrequired“When it starts: a date and time such as 2026-11-02 02:00 (read in timezone), or RFC 3339.”
schedule_maintenanceon 1 other server
“Use this when the user has approved a draft_maintenance draft.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- confirmstringrequired“The plan's confirm sentence, exactly as returned; show it to the user first.”
- draft_idstringrequired“The draft's id from draft_maintenance (it starts with pl_).”
update_maintenanceon 3 other servers
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
9 inputs, 3 required
- actionstringrequired“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.”
- descriptionstring“For edit: new details shown with the window; an empty string clears them.”
- duration_minutesinteger“For edit: the new length, 1 to 720 minutes; a window in progress ends this long after it started.”
- maintenancestringrequired“The window: its id from list_incidents with kind maintenance, or its title.”
- notify_subscribersboolean“For edit: whether status page subscribers are emailed about the window.”
- sitestringrequired“The window's site: its id, name or part of its URL.”
- timezonestring“For edit: the IANA time zone when is read in.”
- titlestring“For edit: the new title, as subscribers will read it.”
- whenstring“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.”
cancel_maintenanceon 1 other server
“Use this when the user calls off planned work: a scheduled or running maintenance window, or a recurring schedule as a whole.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs, 2 required
- maintenancestringrequired“The window: its id from list_incidents with kind maintenance, or its title.”
- sitestringrequired“The window's site: its id, name or part of its URL.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-02.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 258
Tools with a description: 100% of 65
Typical description length: 498 characters

The tool set

Counted from the listing

Tools: 65
Size of the list: about 23,263 tokens for an agent to load (characters ÷ 4)
Naming: 65 of 65 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 65 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-02 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.flarewarden.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

{
  "servers": {
    "website-monitoring": {
      "type": "http",
      "url": "https://mcp.flarewarden.com/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "website-monitoring": {
      "type": "streamableHttp",
      "url": "https://mcp.flarewarden.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

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

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.website-monitoring]
url = "https://mcp.flarewarden.com/mcp"

Zed · Zed settings file (command: zed: open settings file)

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.flarewarden.com/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.flarewarden.com/mcp	Session opened	matches	our test · 2026-11-02
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-02

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-02. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.flarewarden/website-monitoring

Answered from the data above

Who publishes com.flarewarden/website-monitoring?

The registry ties the namespace com.flarewarden to the domain flarewarden.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.flarewarden/website-monitoring need an API key or sign-in?

It opened a session without any credential on 2026-11-02. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.flarewarden/website-monitoring been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-02

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-02, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
580 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 65 tools, 10 resources, 5 prompts.
3,093 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-11-02; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-11-02

MCP capability

prompts, resources, tools, extensions

our test · 2026-11-02

Transport

streamable HTTP

registry · 2026-11-02

Required credentials

none declared

registry · 2026-11-02 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-02

Lifecycle status

active

registry · 2026-11-02

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-02

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.flarewarden/website-monitoring: MCP server record.” Data checked 2026-11-02. https://protocolprobe.com/mcp/servers/com.flarewarden/website-monitoring

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.flarewarden/website-monitoring)](https://protocolprobe.com/mcp/servers/com.flarewarden/website-monitoring)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology