MCP Server vs MCP Server
A side-by-side look at the MCP Server and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for monitoring work as a local process; choose MCP Server 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 MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DEVHELM_API_TOKEN. - You want tools like
list_monitors, get_monitor, create_monitor.
Choose MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_monitors, get_monitor, create_http_monitor.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 57/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DEVHELM_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 129 | 15 |
| Full listing | View MCP Server | View MCP Server |
Tools & capabilities
MCP Server tools 129
list_monitorsList all uptime monitors in the workspace.get_monitorGet a single monitor by ID, including its full configuration.create_monitorCreate a new uptime monitor. Required: name and type (HTTP, DNS, TCP, ICMP, HEARTBEAT, MCP_SERVER, BROWSER, MULTI_STEP_API). ``config`` is required for probe types (HTTP, DNS, TCP, ICMP, HEARTBEAT, MCP_SERVER). Browser and multi-step monitors use a type default when ``config`` is omitted. ``frequencySeconds`` is optional (10–86400). Omit it to use the plan minimum. ``managedBy`` is set automatically to ``MCP`` server-side; callers cannot override it. Use the SDK or CLI directly if you need a different attribution.update_monitorUpdate an existing monitor's configuration.delete_monitorDelete a monitor permanently.pause_monitorPause a monitor (stops checking until resumed).resume_monitorResume a paused monitor.test_monitorTrigger an ad-hoc test run for a monitor and return the result.list_monitor_resultsList recent check results for a monitor (cursor-paginated).list_monitor_versionsList version history for a monitor.list_incidentsList all incidents in the workspace.get_incidentGet a single incident by ID with full details.- +117 more on the listing page
MCP Server tools 15
list_monitorsList the monitors on the account, newest first, 30 per page. Each entry carries the id needed by every other tool, plus name, url, type, current status, check frequency and the uptime percentage over the last 24 hours. Start here when the request names a monitor by name rather than by id, and when asked what is broken - filtering by status "down" answers that in one call. Returns an empty list rather than an error when nothing matches.get_monitorRead one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTTP, port and protocol for PORT, certificate or registration expiry date for SSL and DOMAIN. Use it after list_monitors when the answer depends on how the check is configured, for instance whether a timeout is too tight or which port is actually being watched.create_http_monitorWatch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime. This is the right type for anything a browser would open. Choose create_api_monitor instead when the response body matters as well as the status code. Checks run from probes in several countries. Call list_monitors first so you do not create a duplicate of an existing url.create_api_monitorWatch a JSON or REST endpoint where the response itself matters, not only that the host answered. Use it for health endpoints, webhooks and any API whose failure would be invisible to a plain page check. For an ordinary web page, create_http_monitor is lighter and enough.create_ping_monitorWatch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss. Use it for servers, routers and anything with no web service on top. It says nothing about whether a site or service on that host is working - a box can ping perfectly while its web server is down. Some hosting providers block ICMP, in which case the monitor will read as down.create_port_monitorWatch one TCP or UDP port on a host and report it up only when the service behind it actually answers. This is the type for game servers, databases, mail and anything else that speaks its own protocol rather than HTTP - Minecraft, Rust, CS2, FiveM, Postgres, Redis, SMTP. The port must be given as part of the url. Set protocol to UDP for game servers; most of them do not answer on TCP at all.create_ssl_monitorWatch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires. This is about the certificate, not about the site being reachable - pair it with create_http_monitor when you want both. Note that such a monitor carries two independent states, one for reachability and one for expiry, so a certificate can be days from expiring while the check still reads up.create_domain_monitorWatch a domain registration and report how long is left before it lapses, read from WHOIS. This catches the failure no uptime check can see: everything works perfectly right up to the day the domain expires. Distinct from create_ssl_monitor, which watches the certificate rather than the registration; the two expire on different dates and both are worth watching.pause_monitorStop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around planned maintenance so the downtime does not land in the uptime figures or fire alerts. A paused monitor reports neither up nor down, so it is easy to forget one is off.resume_monitorStart checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual interval, so the current state is known within moments. Safe to call on a monitor that is already running.delete_monitorPermanently delete a monitor together with its entire check history, incidents and statistics. This cannot be undone and there is no trash to restore from. Confirm with the user before calling it, and prefer pause_monitor whenever the intent is only to stop the checking for a while.get_incidentsRead the downtime history of one monitor: when each outage began, when it ended, how long it lasted and what the failure actually was - HTTP status, error text, and which probe saw it. This is the tool for "what happened" and "how often does this break". For the shape of response times around an outage, follow up with get_stats_hourly.- +3 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.
MCP Server
{
"mcpServers": {
"mcp-server-113": {
"command": "uvx",
"args": [
"devhelm-mcp-server"
],
"env": {
"DEVHELM_API_TOKEN": "YOUR_DEVHELM_API_TOKEN_HERE"
}
}
}
}
MCP Server
{
"mcpServers": {
"uptybots-mcp-server": {
"command": "npx",
"args": [
"-y",
"uptybots-mcp-server"
]
}
}
}
Frequently asked questions
MCP Server is categorized under Monitoring and uses a local stdio subprocess. MCP Server belongs to Monitoring and uses a local stdio subprocess. Pick MCP Server for monitoring work and MCP Server 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.
MCP Server has no declared pricing — check the project's own site. MCP Server has no declared pricing — check the project's own site. 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 mcp-server-113 and uptybots-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server has a quality signal of 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars. MCP Server has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.