mcpbeat Sign in

Jsmon MCP Server

by jsmon Your server? Claim it
answering

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

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

Uptime history 17 hours of history · worst hour 50%
17 hours agonow
96.8%
Uptime 24h
61 of 63 checks
—
Tools
hidden behind auth
901 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Jsmon does not always answer

Over the last week it answered 96.8% 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 4 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.jsmon.sh/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "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
{
  "mcpServers": {
    "mcp": {
      "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

URLTransportStateLatencyChecked
https://mcp.jsmon.sh/mcp streamable-http sign-in 3645 ms 4 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
Trestle
by trestlescan

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

34 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.

30 installs/wk local only
D
Flare
by flarehq

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

43 installs/wk local only
Ghosthunt
by 78degrees

Find every leaked secret on your machine — API keys in .env files, shell history, and configs.

37 installs/wk local only
MCP Codeaudit
by infoinlet-marketplace

Security audit for AI agents — scan code/diffs for leaked secrets, check deps via OSV.

24 installs/wk local only
AI Scanner
by aakashbhardwaj27

Scan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets.

38 installs/wk local only
Husk
by husk-security

Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs

53 installs/wk 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: 96.8% 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 61 of 63 checks got a reply (96.8%), average response time 901 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 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 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 901 ms on average, which is faster than 12% 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.