Back to Browse

Jw3 Mcp Cli MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

JW3.ai remote MCP server for market reads and confirm-gated trading execution.

About

JW3.ai remote MCP server for market reads and confirm-gated trading execution.

Remote endpoints: streamable-http: https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

26 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-agnostic4321-ops-jw3-mcp-cli": {
      "url": "https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

JW3 MCP + CLI

mcptry

Listed in the official MCP Registry as io.github.agnostic4321-ops/jw3-mcp-cli (remote, Streamable HTTP). Discovery (initialize, tools/list) is open; every tool call needs OAuth sign-in or a scoped PAT.

Standalone harness repo: the MCP tool server (Supabase edge functions) and the jw3 command-line thin wrapper over its JSON-RPC surface.

Split out of jw3_ai (2026-10-26) to keep app and harness lifecycles separate. The deployed function URLs are unchanged — same Supabase project, same slugs.

Layout

  • cli/ — @jw3/cli (jw3 / jw3d bins). Pure HTTP client of the mcp-server surface; no app imports. cd cli && npm run build (typecheck + emit) / cd cli && npm test (build + node --test).
  • edge-functions/ — Supabase edge functions, deployed to the same project:
    • mcp-server (gateway JWT off — harness PATs are the gate)
    • mcp-auth, mcp-token, mcp-oauth (token issuance / OAuth)

Deploying functions

# Syncs edge-functions/{_shared,agent-chat} from the ../jw3_ai checkout
# (override with JW3_AI_DIR), runs deno check, then stages the standard
# supabase/functions layout in a temp dir and deploys.
scripts/sync-edge-shared.sh --deploy mcp-server

Direct supabase functions deploy from this root does NOT work: sources live under edge-functions/ (not supabase/functions/), and the ../_shared + ../agent-chat imports only resolve after the sync step above (previously a throwaway-symlink step — now this committed script; the copies are gitignored, never committed). Sync-only (no deploy): run the script with no args.

supabase/config.toml pins the gateway flags (verify_jwt = false where the harness PAT — not a JWT — is the credential).

Parity contract

jw3_ai/src/test/read-tool-parity.test.ts reads this repo at the sibling path ../jw3-mcp-cli/edge-functions/mcp-server/* when present and skips otherwise. Keep read_live_datum kinds and shared readers (fetchOnchainSnapshot, executeScreenerRead, no inline buildOnchainAggregate) in sync with jw3_ai's agent-chat/read-tools.ts — the test enforces it locally.

Reviews

No reviews yet

Be the first to review this server!