Exit1 Uptime Monitori… vs Website monitoring AP… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Exit1 Uptime Monitoring vs Website monitoring API & MCP server
In-depth architectural comparison of the Exit1 Uptime Monitoring and Website monitoring API & MCP server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Exit1 Uptime Monitoring
Monitoring · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Website monitoring API & MCP server
Monitoring · Remote HTTP/SSE
Quality: 54/100 (Good) | Auth: API Key required
Verdict Summary: Choose Exit1 Uptime Monitoring if you need specialized Monitoring tools running via a local process. Choose Website monitoring API & MCP server if your workspace requires Monitoring integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Exit1 Uptime Monitoring when:
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: EXIT1_API_KEY, EXIT1_API_URL.
Plan, limits and current usage. Call this first when setting things up.
list_checks
List checks with current status.
get_check
Detail for one check, including SSL state.
get_check_history
Individual results over time.
get_check_stats
Uptime % and response times across ranges.
get_status_page
Snapshot of a public status page.
create_check
Create a monitor (website, API, ping, TCP, DNS, domain, heartbeat).
update_check
Change an existing check's settings.
toggle_check
Pause or resume a check.
delete_check
Permanently remove a check.
get_alert_settings
See where alerts currently go.
set_email_alerts
Set email recipients and events.
+2 more tools listed on main page
Website monitoring API & MCP server Tools (57)
list_sites
List the websites in this Relvato account, with whether each is ready to run monitors.
add_site
Start monitoring a website. Returns the site and the setup step the owner must complete before any monitor runs: connect the WordPress plugin, or verify the domain (the only option for non-WordPress sites). If the account already has a site on the same domain, that site is returned instead of a duplicate. How ownership is proven: https://www.relvato.com/docs/verify-site-ownership
verify_site
Check whether the site's ownership is proven: probes the WordPress plugin connection and/or looks for the domain-verification DNS TXT record / meta tag, or (method gsc / bing) asks Google Search Console / Bing Webmaster Tools. Returns the updated setup state. Docs: https://www.relvato.com/docs/verify-site-ownership
start_monitoring_for_goals
The onboarding shortcut: pick what matters and Relvato adds the monitors that cover it on the current plan (plus uptime, SSL, errors, maintenance mode and structure). Goals: flows (checkout and sign-in), security, search, design, compliance (law compliance — accessibility today), speed, domain, custom, ai.
list_checks
The monitors that can be added to a site: key, what it catches, whether the current plan allows it, whether it's recommended for this site, and whether it's already added.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Exit1 Uptime Monitoring is categorized under Monitoring and uses a local stdio subprocess. In contrast, Website monitoring API & MCP server belongs to Monitoring using remote streaming HTTP/SSE transport. Select Exit1 Uptime Monitoring when you need capabilities focused on monitoring and Website monitoring API & MCP server when you require tools for monitoring.
Add monitors to a site by key (from list_checks). Each key reports added / exists / rejected with the reason (plan, active-monitor limit, needs the WordPress plugin). New monitors run on their default triggers: a weekly (some daily) schedule, plus a re-run when the site changes (WordPress plugin updates, or pushes via the GitHub App).
dismiss_recommendation
Stop recommending a monitor for a site (list_checks marks recommendations), or bring every dismissed recommendation back with restoreAll.
calibrate_site
WordPress / WooCommerce: have Relvato read the store again (a product to buy, checkout type, guest checkout, currency) after the store changed. Runs in the background.
verify_vitals_beacon
Check that the real-user Web Vitals beacon is on the site (its homepage, or data already arriving). get_site_settings has the snippet to install.
site_overview
Plain-language health verdict for a site: what needs attention (real issues vs likely false positives), each monitor with its latest run and schedule, setup state, recommended monitors not yet added, and the account's run usage. On WordPress 6.9+ it also lists the site's AI abilities (WordPress Abilities API) from the latest exposure scan: which plugin registered each, whether AI assistants (MCP Adapter) or REST clients can use it, which ones anyone can run without signing in, and which can delete data.
get_site_health
How a site has been doing: the pass rate now and each of the last 30 days, the trend over 28, 90 or 182 days, each monitoring group's briefing (what needs attention, its likely cause and fix), and — on paid plans — uptime from Relvato's own probes (availability % and incidents over 30 days).
get_performance
A site's speed: the performance summary, lab Core Web Vitals, real visitors' LCP / INP / CLS (p75, last 7 days against the 28 before, per page type and device), what slows it (the elements, images and scripts behind slow visits) and the top fixes with steps.