Jsmon MCP Server

by jsmon Your server? Claim it

answering

Jsmon is answering right now. Last checked 9 min ago.

Discover exposed assets, leaked secrets, APIs & client-side vulns across your attack surface

Uptime history 49 days of history · worst day 96%

49 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

591 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Jsmon every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.jsmon.sh/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.jsmon.sh/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.jsmon.sh/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.jsmon.sh/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.jsmon.sh/mcp"
    }
  }
}

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

URL	Transport	State	Latency	Checked
https://mcp.jsmon.sh/mcp	streamable-http	sign-in	598 ms	9 min ago

Alternatives to Jsmon

same job, measured the same way

LaunchTrust

by launchtrust

Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.

9 tools answering

Stackurity

by stackurity

Installed software, vulnerabilities and end-of-life components across your servers, apps and repos

answering

Trestle

by trestlescan

Detects leaked secrets (API keys, tokens, private keys) in source code.

42 installs/wk local only

Env Secret Exposure Analyzer MCP

by vola-trebla

Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.

69 installs/wk local only

Flare

by flarehq

Scan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys

67 installs/wk local only

ConnectSecure MCP

by servosity

Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots

local only

Secret Scanner

by guardbee

Scans files for leaked secrets and API keys

529 installs/wk local only

Secret Scanner

by 4hmetuyar

Scans files for leaked secrets and API keys

local only

Jsmon — questions

Answers built from our own checks of this server.

Why is there no tool list for Jsmon?

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 Jsmon 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 591 ms. The bar chart above shows every period we have measured.

How do I connect Jsmon?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Jsmon?

No API key is involved. Jsmon 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 Jsmon?

It answers our handshake in 591 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.