Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

JxBrowser MCP Server

REMOTE · JXBROWSER.MCP.TEAMDEV.COM · SCANNED SEP 20

MCP server to assist with JxBrowser development.

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 196 tokens (~98/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the JxBrowser MCP Server server?

JxBrowser MCP Server is a hosted endpoint at https://jxbrowser.mcp.teamdev.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · jxbrowser.mcp.teamdev.com

# add to Claude Code
claude mcp add --transport http teamdev-ip-jxbrowser-mcp 'https://jxbrowser.mcp.teamdev.com/'
// .cursor/mcp.json
{
  "mcpServers": {
    "teamdev-ip-jxbrowser-mcp": {
      "url": "https://jxbrowser.mcp.teamdev.com/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "teamdev-ip-jxbrowser-mcp": {
      "type": "http",
      "url": "https://jxbrowser.mcp.teamdev.com/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.teamdev-ip-jxbrowser-mcp]
url = "https://jxbrowser.mcp.teamdev.com/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "teamdev-ip-jxbrowser-mcp": {
      "type": "remote",
      "url": "https://jxbrowser.mcp.teamdev.com/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add teamdev-ip-jxbrowser-mcp --url 'https://jxbrowser.mcp.teamdev.com/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  teamdev-ip-jxbrowser-mcp:
    url: "https://jxbrowser.mcp.teamdev.com/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "teamdev-ip-jxbrowser-mcp": {
      "Transport": "http",
      "Url": "https://jxbrowser.mcp.teamdev.com/"
    }
  }
}
# add to Vellum
assistant mcp add teamdev-ip-jxbrowser-mcp -t streamable-http -u 'https://jxbrowser.mcp.teamdev.com/'
// mcp.json
{
  "mcpServers": {
    "teamdev-ip-jxbrowser-mcp": {
      "type": "http",
      "url": "https://jxbrowser.mcp.teamdev.com/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Sept 26 +1
    • Tool “ask-jxbrowser-question” rewrote its description, which is the text the model reads security
    • Tool “get-quickstart-guide” rewrote its description, which is the text the model reads security
    • Schema quality: fail → pass functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 1.0.0 → 1.1.0 functional
    • “ask-jxbrowser-question” reworded the description of “question” cosmetic
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://jxbrowser.mcp.teamdev.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jxbrowser.mcp.teamdev.com CN=WR3,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 RSA 2048 SHA256-RSA b3e5425b39cc88a21202859b00ded581
SANs: jxbrowser.mcp.teamdev.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jxbrowser.mcp.teamdev.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
teamdev.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jxbrowser.mcp.teamdev.com/ Verified 200
http (plaintext) http://jxbrowser.mcp.teamdev.com/ HTTPS enforced 302 https://jxbrowser.mcp.teamdev.com/
MCP tools · 2 exposed · ~183 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask-jxbrowser-question ~94

Get documentation-based help with JxBrowser APIs, examples, integration, and troubleshooting. Ask one focused question when JxBrowser-specific information is needed. Each call is independent.

NameTypeReqDescription
questionstringyesOne focused JxBrowser question, usually 1–3 short sentences. Include only essential API names, version details, or a short error excerpt. Omit full files, long logs, and unrelated requirements.

No output schema declared.

No examples provided.

get-quickstart-guide ~89

Get setup instructions and trial-license information for a new JxBrowser project. Infer the toolkit and build tool from the project or conversation; ask only when unresolved. Compose Desktop requires Gradle. This tool returns instructions; it does not create files or run commands.

NameTypeReqDescription
buildToolstringyesThe build tool to use
uiToolkitstringyesThe UI toolkit to use

No output schema declared.

No examples provided.

Common questions

What is the JxBrowser MCP Server server?

JxBrowser MCP Server is listed in the public MCP registry as io.github.TeamDev-IP/jxbrowser-mcp. MCP server to assist with JxBrowser development. This page covers its hosted endpoint (https://jxbrowser.mcp.teamdev.com/).

Is the JxBrowser MCP Server server safe to use?

JxBrowser MCP Server scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the JxBrowser MCP Server server expose?

JxBrowser MCP Server exposes 2 tools: get-quickstart-guide, ask-jxbrowser-question. Their descriptions and schemas cost roughly 183 tokens of context every time the server is loaded.

Does the JxBrowser MCP Server server require authentication?

No. We connected to JxBrowser MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the JxBrowser MCP Server server still maintained?

JxBrowser MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.