Jsmon

sh.jsmonPublished by jsmon.shOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Jsmon is a remote MCP server that lets an assistant surface exposed assets, leaked secrets, APIs and client-side vulnerabilities across an attack surface.

What you can do
  • Discover exposed assets and APIs across an attack surface
  • Surface leaked secrets and client-side vulnerabilities
  • Report findings from the Jsmon platform to the assistant
  • No tool list is published, so exact operations are not documented
When to use it
Useful for security and asset-discovery work where you want an assistant to pull Jsmon's findings on exposed assets, leaked secrets and client-side issues into a conversation instead of checking the dashboard by hand.
Requirements
Remote streamable HTTP endpoint at mcp.jsmon.sh; OAuth sign-in is required. No environment variables or headers are declared. A Jsmon account with access to the relevant attack surface is implied.
Before you install
OAuth grants the server access to your Jsmon account data, which covers security findings such as leaked secrets; review the scopes requested. Findings may contain sensitive credentials, so treat results as confidential. No tool list is published, so what the assistant can read or change is unverified.

Installation

In SourceWeft

  1. Open Jsmon 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/sh.jsmon%2Fmcp/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": {
    "jsmon": {
      "type": "http",
      "url": "https://mcp.jsmon.sh/mcp"
    }
  }
}

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. v1.0.0LatestSep 21, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.