Fluxguard
Fluxguard is an AI-powered website change detection and monitoring tool that helps businesses track, analyze, and respond to critical changes in web-based data.
Verdict
Common use cases
- Catch unauthorized edits to public landing pages
- Track competitor pricing page updates daily
- Monitor vendor terms-of-service for compliance
- Alert team when partner sites go offline
- Archive snapshots of regulatory disclosure pages
Integration
- Vendor
- Fluxguard
- Category
- other
- Auth
- API_KEY
- Tools
- 23
- Composio slug
fluxguard
Tools
- Acknowledge Fluxguard Alert
Tool to acknowledge an alert, marking it as reviewed. Since Fluxguard's public API does not currently expose an acknowledge endpoint, we perform a real API call to the official sample webhook endpoint to validate the alert context and retur
- Add FluxGuard Page
Tool to add a new page for monitoring. Use when you need to start monitoring a URL by adding it to FluxGuard.
- Create FluxGuard Site Category
Tool to create a new site category in FluxGuard. Use when you need to group your sites under custom categories before monitoring. Invoke after authenticating your account.
- Create Webhook
Tool to create a new webhook for receiving notifications about monitored pages. Use when you need to receive change notifications via HTTP POST to your endpoint.
- Delete Fluxguard Pagedestructive
Tool to delete a monitored page. Use when you need to permanently remove a page and its data after confirming the site and session IDs.
- Delete Fluxguard Sitedestructive
Tool to delete a monitored site. Use when you need to permanently remove a site and all its data.
- Delete Webhookdestructive
Tool to delete a webhook. Use when you need to remove a webhook by its ID.
- Fluxguard Webhook Notification
Tool to send change data to your webhook endpoint. Use when a modification is detected.
- Get Alert Details
Tool to retrieve details of a specific alert. Use after obtaining the alert ID. Returns full alert information.
- Get Changes
Tool to retrieve a list of all detected changes across monitored sites. Since there is no public "list changes" endpoint, this action uses the sample webhook endpoint as a surrogate data source.
- Get FluxGuard Account Data
Tool to retrieve general account information for your FluxGuard organization. Use when you need to fetch organization’s account attributes after authenticating.
- Get FluxGuard Alerts
Tool to retrieve all alerts generated by site changes. Since Fluxguard's public API does not expose an alerts listing endpoint, we leverage the sample webhook payload to provide a representative alert item.
- Get Fluxguard Change
Tool to retrieve details of a change by its ID. Use after you have a valid change ID to fetch its details.
- Get FluxGuard Site Categories
Tool to retrieve all site categories. Use when you need to list every category defined in your organization.
- Get FluxGuard Site Details
Tool to retrieve details of a specific monitored site by its ID. Use when you have the site_id and need the site's current configuration and status.
- Get FluxGuard Sites
Tool to retrieve a list of all monitored sites. Use when you need to enumerate all sites after authenticating.
- Get FluxGuard User Details
Tool to retrieve details that represent the current FluxGuard account as a user-like object. FluxGuard does not expose a public users endpoint; we map /account attributes to a user shape.
- Get FluxGuard Users
Tool to retrieve all users in the organization. Since FluxGuard's public API does not expose a users listing endpoint, we leverage a documented endpoint and return an empty list when user data is not available.
- Get FluxGuard Webhooks
Tool to retrieve all configured webhooks. Use when you need a list of webhook configurations.
- Get Sample Webhook Payload
Tool to retrieve a sample webhook payload. Use when you need to inspect the structure of webhook notifications.
- Get Site Snapshots
Tool to retrieve a list of all site snapshots. Use when you need to enumerate available snapshots for your account.
- Get Snapshot
Tool to retrieve details of a specific snapshot by its ID. Since Fluxguard does not expose a public snapshot lookup endpoint, this action searches the sample webhook payload for a matching snapshot.
- Get Webhook Details
Tool to retrieve details of a specific webhook by its ID. Use when you need to fetch up-to-date configuration of a webhook.
Setup
Setup guide
- 11. Log into your Fluxguard account at fluxguard.com and navigate to Settings or API Access to generate an API key. 2. In Switchy, open your workspace settings and click Integrations, then find Fluxguard in the MCP directory. 3. Click Connect and paste your API key when prompted. 4. Switchy will verify the key by calling the Fluxguard API; if successful, you'll see a green checkmark. 5. Open any Space where you want to monitor websites and type '@Fluxguard add page [URL]' to start tracking a site. 6. Test the connection by asking '@Fluxguard list my monitored pages' — you should see the URL you just added. 7. To receive alerts, create a webhook with '@Fluxguard create webhook [your-endpoint-url]' so Fluxguard can POST change notifications to your system.
What teammates see: by default, memories from Fluxguard are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Start Monitoring a Page
@Fluxguard add page https://example.com/pricing to my monitored sites. Set the check frequency to daily and notify me of any content changes.Open in a Space →
Organize Sites by Category
@Fluxguard create a site category called 'Competitor Pricing' so I can organize all the pricing pages I'm tracking under one label.Open in a Space →
Set Up Change Notifications
@Fluxguard create webhook https://hooks.example.com/fluxguard-changes so I get notified in real time when any monitored page updates.Open in a Space →
Review and Acknowledge Alert
@Fluxguard acknowledge alert ID 12345. I've reviewed the change to the terms page and confirmed it's a minor formatting update.Open in a Space →
Remove Outdated Monitoring
@Fluxguard delete page https://old-vendor.com/terms from my monitored sites. We've switched providers and don't need to track this anymore.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Fluxguard show me all alerts from the last 48 hours that haven't been acknowledged yet, grouped by site
Here's a summary of unacknowledged alerts from the past 48 hours: **acme-corp.com** (3 alerts) - Homepage: Content change detected in pricing section (2024-01-15 14:23 UTC) - Terms of Service: Legal text modified (2024-01-15 09:17 UTC) - Contact page: Form fields updated (2024-01-14 22:41 UTC) **partner-site.io** (1 alert) - API docs: New endpoint documentation added (2024-01-15 11:05 UTC) This illustrative example shows how Fluxguard would surface recent change notifications across your monitored pages.
This example demonstrates Fluxguard's core monitoring capability — detecting and surfacing website changes. Note that alert retrieval requires valid API authentication, and the response structure depends on your account's active monitoring configuration. Fluxguard's webhook-based architecture means real-time alerts typically arrive via HTTP POST rather than polling.
@Fluxguard add monitoring for https://competitor.com/pricing and set up a webhook to notify our Slack channel when changes are detected
I've completed the setup: 1. **Page added**: competitor.com/pricing is now being monitored (Page ID: pg_8x7k2m). Fluxguard will check this URL on your account's configured schedule. 2. **Webhook created**: New webhook endpoint configured (Webhook ID: wh_9p4n1q) pointing to your Slack integration URL. You'll receive POST notifications whenever changes are detected on this page. This example shows how you'd initiate monitoring — the actual first scan happens on Fluxguard's next scheduled check cycle.
This write-action example shows Fluxguard's setup workflow. In practice, you'll need to provide a valid webhook URL (like a Slack incoming webhook) and ensure your API key has write permissions. The MCP creates the monitoring configuration but doesn't trigger an immediate scan — Fluxguard operates on scheduled intervals determined by your account plan.
@Fluxguard review all changes detected on our legal pages this month and draft a compliance summary highlighting any modifications to privacy policy or terms of service language
Based on Fluxguard's change detection data for January 2024, here's the compliance summary: **Privacy Policy** (last modified: Jan 12) - Added new section on AI data processing (paragraph 4.2) - Updated data retention period from 24 to 36 months (section 5.1) - Changed third-party processor list: added "Analytics Co." **Terms of Service** (last modified: Jan 8) - Modified arbitration clause language (section 12.3) - No material changes to liability limitations This illustrative synthesis shows how the AI would interpret Fluxguard's raw change data and contextualize it for your compliance review workflow.
This synthesis example pairs Fluxguard's change detection with AI reasoning to produce actionable insights. The MCP provides the raw change data (what text changed, when, where), while the AI interprets significance. Accuracy depends on Fluxguard's diff quality and your monitoring configuration — ensure legal pages are monitored with appropriate sensitivity settings to catch subtle wording changes.
Use-case deep-dives
When Fluxguard catches regulatory changes before your audit
A 6-person compliance team at a fintech startup monitors 40+ regulator websites for policy updates that affect their product. Fluxguard wins here because it watches external pages you don't control—state banking sites, SEC guidance pages, CFPB bulletins—and alerts the team in Slack via webhook when text changes. The 'Add FluxGuard Page' and 'Create Webhook' tools let you script the monitoring setup in a shared AI session, so onboarding a new jurisdiction takes 2 minutes instead of 20. The trade-off: if your compliance process requires screenshot diffs or PDF change tracking, Fluxguard's text-focused detection won't cover you. But for catching surprise rule changes on public HTML pages, this MCP turns a manual daily check into a passive alert feed.
Why this MCP isn't built for traditional uptime monitoring
A 12-person agency monitors 30 client websites for downtime and broken pages. Fluxguard is the wrong tool for this scenario. The MCP's 23 tools focus on content change detection—tracking when a paragraph updates, a form field disappears, or a price changes—not HTTP status codes or response times. If a client's homepage goes down, Fluxguard won't fire an alert until it can fetch the page again and detect a content delta. For uptime and availability monitoring, you need a service that pings endpoints on a schedule and alerts on 500s or timeouts. Fluxguard's strength is catching subtle content drift on live pages, not catching outages. If your agency contract includes 'notify us when the About page text changes without approval,' then this MCP fits.
When Fluxguard scales competitor intel gathering to 50+ pages
A 4-person product team tracks pricing pages, feature lists, and changelog pages across 15 competitors. Fluxguard handles this well because the 'Create FluxGuard Site Category' and 'Add FluxGuard Page' tools let you organize competitors into groups (SaaS, Enterprise, Open Source) and monitor multiple URLs per competitor without manual browser tabs. When a rival launches a new feature or changes pricing, the webhook fires into your team Slack, and you triage in standup. The threshold: if you need to monitor pages behind login walls or SPAs that render client-side, Fluxguard's crawler won't see the content. But for public-facing marketing and product pages, this MCP turns competitive research from a weekly chore into a real-time feed.
Frequently asked
What does the Fluxguard MCP do in Switchy?
It monitors websites for changes and sends alerts when content shifts. Your AI can add pages to watch, create webhooks for notifications, acknowledge alerts, and delete monitoring jobs. Useful for tracking competitor sites, compliance pages, or client deliverables without manual checking. The MCP wraps Fluxguard's API so your team can automate change detection workflows directly in Switchy.
Do I need a Fluxguard account to use this MCP?
Yes. You need an active Fluxguard account and an API key. Generate the key from your Fluxguard dashboard, then paste it into Switchy's connection flow. The MCP authenticates every request with that key. If your key expires or gets revoked, the integration stops working until you update it.
Can the MCP monitor password-protected pages?
No. Fluxguard's API monitors publicly accessible URLs. If your target page sits behind a login or paywall, the service can't reach it. For authenticated monitoring, you'd need to expose a public staging URL or use a different tool that supports credential injection.
Why use this instead of Fluxguard's dashboard directly?
The MCP lets your AI add monitoring jobs, triage alerts, and route notifications without leaving Switchy. If you're already managing workflows in the workspace, the integration saves tab-switching. For one-off checks, the Fluxguard dashboard is faster. For recurring workflows tied to other data sources, the MCP makes more sense.
Does each monitored page count against my Fluxguard plan?
Yes. Fluxguard bills by monitored pages and check frequency. Adding pages via the MCP consumes the same quota as adding them in the dashboard. Check your Fluxguard plan limits before automating bulk monitoring jobs, or you'll hit overages.