A side-by-side look at the Openuptime 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 Openuptime 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.
DATABASE_URL, BETTER_AUTH_SECRET, CRON_SECRET, POSTGRES_PASSWORD, PUBLIC_URL, BETTER_AUTH_URL, WEB_ORIGIN.TICKSTEM_API_KEY, TICKSTEM_BASE_URL.list_jobs, get_job, register_job.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 52/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Free | Not declared |
| Required env vars | DATABASE_URLBETTER_AUTH_SECRETCRON_SECRETPOSTGRES_PASSWORDPUBLIC_URLBETTER_AUTH_URLWEB_ORIGIN | TICKSTEM_API_KEYTICKSTEM_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 26 |
| Full listing | View Openuptime | View Tickstem MCP |
No tool names declared yet. Check the project README from the listing page.
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 pollingPaste 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.
{
"mcpServers": {
"becoolme-openuptime": {
"command": "npx",
"args": [
"-y",
"becoolme-openuptime"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE",
"BETTER_AUTH_SECRET": "YOUR_BETTER_AUTH_SECRET_HERE",
"CRON_SECRET": "YOUR_CRON_SECRET_HERE",
"POSTGRES_PASSWORD": "YOUR_POSTGRES_PASSWORD_HERE",
"PUBLIC_URL": "YOUR_PUBLIC_URL_HERE",
"BETTER_AUTH_URL": "YOUR_BETTER_AUTH_URL_HERE",
"WEB_ORIGIN": "YOUR_WEB_ORIGIN_HERE"
}
}
}
}
{
"mcpServers": {
"tickstem-mcp": {
"command": "uvx",
"args": [
"tickstem"
],
"env": {
"TICKSTEM_API_KEY": "YOUR_TICKSTEM_API_KEY_HERE",
"TICKSTEM_BASE_URL": "YOUR_TICKSTEM_BASE_URL_HERE"
}
}
}
}