Website monitoring API & MCP server vs Tickstem MCP
A side-by-side look at the Website monitoring API & MCP server and Tickstem MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Website monitoring API & MCP server for monitoring work over a hosted endpoint; choose Tickstem MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Website monitoring API & MCP server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
list_sites, add_site, verify_site.
Choose Tickstem MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TICKSTEM_API_KEY, TICKSTEM_BASE_URL. - You want tools like
list_jobs, get_job, register_job.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 54/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | TICKSTEM_API_KEYTICKSTEM_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 2 |
| Directory activity | 3 views 1 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 58 | 26 |
| Full listing | View Website monitoring API & MCP server | View Tickstem MCP |
Tools & capabilities
Website monitoring API & MCP server tools 58
list_sitesList the websites in this Relvato account, with whether each is ready to run monitors.add_siteStart monitoring a website. Returns the site and its setup: until the owner proves ownership (connect the WordPress plugin, or verify the domain — the only option for non-WordPress sites), trigger_scan can run the public monitors by hand 3 times a day (setup.manualRuns); scheduled runs, alerts, update/deploy runs and the monitors that act on the site need the proof (setup.nextStep); setup.afterProof says what proof adds for this site on its plan. 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-ownershipverify_siteCheck 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-ownershipstart_monitoring_for_goalsThe 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. Before the site's ownership is proven the monitors are added but don't run on their schedule yet (scheduleStarts).list_checksThe 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. Before the site's ownership is proven, runsNow says which can run now (started by hand) and which after proof; for a site added as "other", withWordPressPlugin lists what the WordPress plugin adds.add_checksAdd 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). Once the site's ownership is proven, new monitors get a daily schedule on plans that run daily (Pro and up) and a weekly one on Free, plus a re-run when the site changes on Pro and up (WordPress plugin updates, or pushes via the GitHub App). Before proof they're added but only run when trigger_scan starts them (scheduleStarts).dismiss_recommendationStop recommending a monitor for a site (list_checks marks recommendations), or bring every dismissed recommendation back with restoreAll.calibrate_siteWordPress / 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_beaconCheck 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_overviewPlain-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_healthHow a site has been doing: the share of monitors passing now (the Overview's "Monitors passing") 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_performanceA 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.- +46 more on the listing page
Tickstem MCP tools 26
list_jobsList all cron jobs in the accountget_jobGet a cron job by IDregister_jobRegister a new cron job (name, schedule, endpoint)update_jobUpdate an existing job — only provided fields changepause_jobPause a job so it no longer firesresume_jobResume a paused or failing jobdelete_jobPermanently delete a job and its execution historylist_executionsList execution history for a job, most recent firstlist_monitorsList all monitors — status, URL, interval, SSL expiry, assertionscreate_monitorCreate a monitor with optional response assertions (status code, response time, body)get_monitorGet a monitor by IDpause_monitorPause a monitor so it stops polling- +14 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Website monitoring API & MCP server
{
"mcpServers": {
"website-monitoring-api-mcp-server": {
"command": "npx",
"args": [
"-y",
"website-monitoring-api-mcp-server"
]
}
}
}
Tickstem MCP
{
"mcpServers": {
"tickstem-mcp": {
"command": "uvx",
"args": [
"tickstem"
],
"env": {
"TICKSTEM_API_KEY": "YOUR_TICKSTEM_API_KEY_HERE",
"TICKSTEM_BASE_URL": "YOUR_TICKSTEM_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Website monitoring API & MCP server is categorized under Monitoring and uses a remote HTTP/SSE transport. Tickstem MCP belongs to Monitoring and uses a local stdio subprocess. Pick Website monitoring API & MCP server for monitoring work and Tickstem MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Website monitoring API & MCP server is listed as freemium — a free tier with paid plans. Auth: api key required. Tickstem MCP has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add website-monitoring-api-mcp-server and tickstem-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Website monitoring API & MCP server has a quality signal of 54/100 (Good) with 3 views, 1 installs and 0 GitHub stars. Tickstem MCP has 55/100 (Good) with 3 views, 0 installs and 2 GitHub stars.