_ registry / mcp streamable-http · checked 1h ago

javadocs.dev

https://www.javadocs.dev

Registry code: f16e243435c0d226

api record

Access to Java, Kotlin, and Scala library documentation.

from a public catalogue that lists it, not from the operator

endpoint
https://www.javadocs.dev/mcp
protocol
streamable-http ·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 javadocs.dev live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is javadocs.dev free to use?
Yes — the hub reached it with no key and no payment.
What tools does javadocs.dev have?
8 tools: list_javadoc_symbols, search_artifacts, symbol_to_artifact, list_source_files, get_javadoc_index, get_latest_version, get_source_file, get_javadoc_symbol.
Is javadocs.dev 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
100%

90 days 99.3%· all time 99.3%

latency
310ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 282 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • read javadoc for a maven artifact
  • find which artifact contains a class
  • get latest version of a maven library
  • read library source files
takes → gives
text → text, code
tools
8 reads
_ 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 8 tools
8 never probed 0 of 8 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.

  • list_javadoc_symbols reads unknown 1h ago

    Enumerates the public API a library documents — classes, interfaces, traits, objects, enums, and annotations — for a Maven Central artifact version. Each entry includes the fully-qualified class name (`fqn`) and a `link` that can be passed to get_javadoc_symbol to read the rendered API documentation. Use this to answer 'which classes/types does library X have?' or 'find classes related to <topic>' — it is the fastest way to list the API by name without reading code. Prefer this over list_source_files whenever you only need class/type names. Pass `filter` (e.g. a class name) to get only the matching entries: large libraries list hundreds of symbols, so filtering saves a lot of context when you are looking for one type. Only if this returns NotFoundError because no javadoc jar was published, fall back to list_source_files. Works against the live Maven Central catalog with no local install, build, or checkout required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groupId",
        "artifactId",
        "version"
      ],
      "properties": {
        "filter": {
          "type": "string",
          "description": "Optional. Only return symbols whose fully-qualified name contains this text (case-insensitive; several space-separated terms must all match), e.g. \"PolymorphicTypeValidator\" or \"judge Builder\". Omit to list every symbol."
        },
        "groupId": {
          "type": "string",
          "description": "The Maven groupId, e.g. \"dev.zio\"."
        },
        "version": {
          "type": "string",
          "description": "The artifact version, e.g. \"2.1.9\"."
        },
        "artifactId": {
          "type": "string",
          "description": "The Maven artifactId, e.g. \"zio_3\"."
        }
      },
      "description": "A Maven Central artifact version whose documented symbols to list, optionally narrowed by name."
    }
    arguments 27 lines
  • search_artifacts reads unknown 1h ago

    Finds Maven coordinates from part of a library name: searches the javadocs.dev index of Maven Central artifacts for groupId:artifactId values containing every word of the query (case-insensitive). Use this when you know part of a library name (e.g. "jackson", "zio-http", "netty-codec") and need the exact groupId:artifactId coordinates to feed into the other tools. Query with name fragments only — versions are not part of the match. The same artifactId can be published under several groupIds (e.g. jackson-databind: com.fasterxml.jackson.core for 2.x, tools.jackson.core for 3.x), so check each candidate with get_latest_version. To find the library that contains a class, use symbol_to_artifact instead.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "The text to search for — e.g. a class/type name, a package, or part of a groupId/artifactId."
        }
      },
      "description": "A search query."
    }
    arguments 13 lines
  • symbol_to_artifact reads unknown 1h ago

    Finds which Maven artifact contains a given Java/Kotlin/Scala class: resolves a class name, nested type (e.g. Outer.Builder), fully-qualified type, or package name to the Maven Central artifacts (groupId, artifactId) that publish it. Exact case is preferred; a case-insensitive match is tried if that finds nothing. Several artifacts can contain the same simple name (e.g. a Java and a Scala library): check each result rather than assuming the first. Use this when you have a symbol from a stack trace, an import line, or an error message and you need to know which library to look in. From there, chain into get_latest_version, then list_source_files / list_javadoc_symbols to read the code or docs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "The text to search for — e.g. a class/type name, a package, or part of a groupId/artifactId."
        }
      },
      "description": "A search query."
    }
    arguments 13 lines
  • list_source_files reads unknown never probed

    Lists the raw source files (`.java`, `.kt`, and `.scala`) in a Maven Central artifact version's `-sources.jar`. Each returned path can be passed to get_source_file to read the actual source code. Use this only when you need the implementation — for example, to trace behavior or see how something is wired. To discover which classes exist, or to find classes by topic or name, use list_javadoc_symbols instead; do not use this tool just to enumerate classes. Works against the live Maven Central catalog with no local install, build, or checkout required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groupId",
        "artifactId",
        "version"
      ],
      "properties": {
        "groupId": {
          "type": "string",
          "description": "The Maven groupId, e.g. \"dev.zio\"."
        },
        "version": {
          "type": "string",
          "description": "The artifact version, e.g. \"2.1.9\"."
        },
        "artifactId": {
          "type": "string",
          "description": "The Maven artifactId, e.g. \"zio_3\"."
        }
      },
      "description": "A fully-qualified Maven Central artifact coordinate: groupId, artifactId, and version."
    }
    arguments 23 lines
  • get_javadoc_index reads unknown 8h ago

    Fetches the rendered Javadoc/Scaladoc index page for a specific Maven Central artifact version, converted to plain text/markdown. Useful for orienting yourself in an unfamiliar library: it lists the top-level packages, modules, and (for Scaladoc) often a curated overview. Use this before drilling into specific symbols. Works against the live Maven Central catalog — you do not need to download the javadoc jar.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groupId",
        "artifactId",
        "version"
      ],
      "properties": {
        "groupId": {
          "type": "string",
          "description": "The Maven groupId, e.g. \"dev.zio\"."
        },
        "version": {
          "type": "string",
          "description": "The artifact version, e.g. \"2.1.9\"."
        },
        "artifactId": {
          "type": "string",
          "description": "The Maven artifactId, e.g. \"zio_3\"."
        }
      },
      "description": "A fully-qualified Maven Central artifact coordinate: groupId, artifactId, and version."
    }
    arguments 23 lines
  • get_latest_version reads unknown 8h ago

    Resolves the latest published version of a Maven Central artifact (any groupId:artifactId — Java, Kotlin, or Scala library). Call this first when you only know the artifact but not the version: the version it returns feeds into every other tool here that takes a concrete version. By default it returns the latest release, sorted by Maven version order and skipping pre-releases; set `includePreReleases` to true to get the newest version of any kind (milestone, RC, beta...), e.g. when a class or method you are looking for is missing from the latest release. Works against the live Maven Central catalog — no local install, build tool, or repository checkout required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groupId",
        "artifactId"
      ],
      "properties": {
        "groupId": {
          "type": "string",
          "description": "The Maven groupId, e.g. \"dev.zio\"."
        },
        "artifactId": {
          "type": "string",
          "description": "The Maven artifactId, e.g. \"zio_3\"."
        },
        "includePreReleases": {
          "type": "boolean",
          "description": "Optional, default false. When true, also consider pre-releases (milestones, RCs, betas, alphas, snapshots), e.g. to find a new API that only exists in a milestone. When false, returns the latest release (or the newest pre-release if the artifact has no release at all)."
        }
      },
      "description": "A Maven Central artifact (groupId and artifactId) whose latest version to resolve."
    }
    arguments 22 lines
  • get_source_file reads unknown never probed

    Reads one source file from a Maven Central library's sources jar (the `-sources.jar` artifact). Pass the `link` value returned by list_source_files. Use this whenever you need the exact source text of a JVM library — tracing behavior into a dependency, confirming a public API's implementation, finding a definition, or comparing two library versions. Strongly preferred over locating the jar in a local build cache and unzipping it: it works for any Maven Central artifact, no local checkout or build needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groupId",
        "artifactId",
        "version",
        "link"
      ],
      "properties": {
        "link": {
          "type": "string",
          "description": "The relative path/link within the jar, as returned by list_javadoc_symbols or list_source_files."
        },
        "groupId": {
          "type": "string",
          "description": "The Maven groupId, e.g. \"dev.zio\"."
        },
        "version": {
          "type": "string",
          "description": "The artifact version, e.g. \"2.1.9\"."
        },
        "artifactId": {
          "type": "string",
          "description": "The Maven artifactId, e.g. \"zio_3\"."
        }
      },
      "description": "A pointer to one documented page or source file inside an artifact's jar."
    }
    arguments 28 lines
  • get_javadoc_symbol reads unknown 8h ago

    Reads one Javadoc/Scaladoc page from a Maven Central artifact, already converted to plain text/markdown so you don't have to parse HTML. Pass the `link` value returned by list_javadoc_symbols. Navigation and links to external sites are stripped; the links that remain point at other pages of the same jar and can be passed back as `link` to follow them. Use this when you need to know what a class, method, or field does and what its parameters mean for any library on Maven Central — without downloading or unzipping the javadoc jar yourself.

    mcp-tool

    {
      "type": "object",
      "required": [
        "groupId",
        "artifactId",
        "version",
        "link"
      ],
      "properties": {
        "link": {
          "type": "string",
          "description": "The relative path/link within the jar, as returned by list_javadoc_symbols or list_source_files."
        },
        "groupId": {
          "type": "string",
          "description": "The Maven groupId, e.g. \"dev.zio\"."
        },
        "version": {
          "type": "string",
          "description": "The artifact version, e.g. \"2.1.9\"."
        },
        "artifactId": {
          "type": "string",
          "description": "The Maven artifactId, e.g. \"zio_3\"."
        }
      },
      "description": "A pointer to one documented page or source file inside an artifact's jar."
    }
    arguments 28 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 f16e243435c0d226.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f16e243435c0d226/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/f16e243435c0d226/badge.svg)](https://brick.blue/agent/f16e243435c0d226?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
100%

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.