mcpbeat Sign in

Jamp MCP Server

by jdwilliums Your server? Claim it
answering

Jamp is answering right now. Last checked 2 min ago. 25 installs a week from npm.

Agent-run site monitoring: install JAMP, read errors, uptime, vitals and traffic, resolve fixes.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 238 · avg 11 · -81% w/w
a month agotoday
Uptime history 51 days of history · worst day 7%
51 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
371 ms
Response time
average over 24h
25
Installs / week
npm and PyPI

Jamp does not always answer

Over the last week it answered 90.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add jamp --transport http https://mcp.jamp.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "jamp": {
      "url": "https://mcp.jamp.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.jamp]
url = "https://mcp.jamp.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "jamp": {
      "url": "https://mcp.jamp.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "jamp": {
      "url": "https://mcp.jamp.io/mcp"
    }
  }
}

This one needs environment variables set before it will start: JAMP_API_TOKEN (JAMP API token from Settings > API & MCP access (tick write access for the setup tools)). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.jamp.io/mcp streamable-http sign-in 285 ms 2 min ago

Alternatives to Jamp

same job, measured the same way
Uptimemonitoring
by uptimemonitoring

Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.

answering
Vantaj
by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering
HostTracker
by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering
Betterstack
by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering
Uptimely
by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering
UptimeRobot
by uptimerobot

Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.

answering
Fettle
by fettle

Uptime monitoring for developers — monitors, incidents, heartbeats and status pages

26 installs/wk answering
Hyperping
by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

26 tools answering

Jamp — questions

Answers built from our own checks of this server.

Why is there no tool list for Jamp?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Jamp working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 371 ms. The bar chart above shows every period we have measured.
Is Jamp still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Jamp?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Jamp?
No API key is involved. Jamp answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Jamp?
It answers our handshake in 371 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Jamp?
The npm package jamp-mcp was installed 25 times in the last week. Week over week that is -81%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.