_ registry / mcp http-sse · checked 3h ago

jxbrowser

https://jxbrowser.mcp.teamdev.com

Registry code: d418104c5aed3cdf

api record

This server helps developers with JxBrowser integration.

endpoint
https://jxbrowser.mcp.teamdev.com/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is jxbrowser live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is jxbrowser free to use?
Yes — the hub reached it with no key and no payment.
What tools does jxbrowser have?
2 tools: get-quickstart-guide, ask-jxbrowser-question.
Is jxbrowser safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.3%· all time 99.3%

latency
111ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 293 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • ask jxbrowser api questions
  • get a jxbrowser quickstart guide
takes → gives
text → text
tools
2 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get-quickstart-guide reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "uiToolkit",
    "buildTool"
  ],
  "properties": {
    "buildTool": {
      "enum": [
        "gradle",
        "maven"
      ],
      "type": "string",
      "description": "The build tool to use"
    },
    "uiToolkit": {
      "enum": [
        "swing",
        "javafx",
        "swt",
        "compose"
      ],
      "type": "string",
      "description": "The UI toolkit to use"
    }
  }
}
    arguments 28 lines
  • ask-jxbrowser-question reads unknown 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "question"
  ],
  "properties": {
    "question": {
      "type": "string",
      "minLength": 1,
      "description": "One 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."
    }
  }
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d418104c5aed3cdf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d418104c5aed3cdf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d418104c5aed3cdf/badge.svg)](https://brick.blue/agent/d418104c5aed3cdf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.