jamp-mcp

MCPcommunitylive
v0.2.1Jack WilliamsMITUpdated 2mo agonpmGitHub

MCP server for JAMP. Your AI agent installs JAMP on a site, watches errors, uptime, vitals and traffic, and resolves what it fixes.

Endpoint healthlive
checked 3 days ago · 109ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
AuthorJack Williams
LicenseMIT
Version0.2.1
Sourcenpm+mcp-registry
npmjamp-mcp
GitHubJDWilliums/crumbless
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 2 privileged
Security scan✓ Cleanv0.2.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 2 privileged
Statically extracted from the published packagev0.2.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

jamp_create_siteNo description published

This tool published no description. Forge does not invent one.

jamp_verify_installprivilegedNo description published

This tool published no description. Forge does not invent one.

jamp_setup_sourcemapsNo description published

This tool published no description. Forge does not invent one.

jamp_enable_uptimeNo description published

This tool published no description. Forge does not invent one.

jamp_install_doctorprivilegedNo description published

This tool published no description. Forge does not invent one.

jamp_resolve_errorNo description published

This tool published no description. Forge does not invent one.

jamp_list_sitesNo description published

This tool published no description. Forge does not invent one.

jamp_list_errorsNo description published

This tool published no description. Forge does not invent one.

jamp_get_errorNo description published

This tool published no description. Forge does not invent one.

jamp_uptimeNo description published

This tool published no description. Forge does not invent one.

jamp_vitalsNo description published

This tool published no description. Forge does not invent one.

jamp_trafficNo description published

This tool published no description. Forge does not invent one.

jamp_page_auditNo description published

This tool published no description. Forge does not invent one.

jamp_site_auditNo description published

This tool published no description. Forge does not invent one.

jamp_run_auditNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for JAMP. Your AI agent installs JAMP on a site, watches errors, uptime, vitals and traffic, and resolves what it fixes.

Keywords
mcpmodelcontextprotocolmonitoringanalyticserror-trackinguptimeweb-vitalsobservabilityclaudeai-agentsjamp
Alternatives
Comparing tool surfaces…

Tools exposed

15 tools · 2 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in analytics & dashboards