Jamp

io.github.JDWilliumsPublished by GitHub account JDWilliumsv0.2.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

JAMP lets an assistant monitor websites: read errors, uptime, Core Web Vitals and traffic, then apply fixes through the JAMP platform.

What you can do
  • Read site monitoring data such as errors, uptime, vitals and traffic
  • Investigate reported problems and resolve fixes through the JAMP platform
  • Run setup tasks when the API token carries write access
When to use it
Useful when you want an assistant to watch a site's health and performance and act on issues from the same conversation, rather than switching to a separate monitoring dashboard.
Requirements
A JAMP account and an API token from Settings > API & MCP access, supplied as the JAMP_API_TOKEN environment variable; write access must be enabled on the token for the setup tools. Available as a remote endpoint or as the npm package jamp-mcp over stdio. Authentication uses OAuth.
Before you install
The token is a secret granting access to your JAMP account; enabling write access lets the assistant change things, so grant it only when needed. Monitoring data from your sites is sent to the JAMP service.

Installation

In SourceWeft

  1. Open Jamp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.JDWilliums%2Fjamp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jamp": {
      "type": "http",
      "url": "https://mcp.jamp.io/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.