Ext Ops Panel
Open dashboard
Comparison

Javadocs vs io.github.arvindand/maven-tools-mcp

Javadocs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.arvindand/maven-tools-mcp is an MCP server published by arvindand. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceJavadocsio.github.arvindand/maven-tools-mcp
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Listed
Version: sha256:956552d90476
Forks (GitHub): 9
Stars (GitHub): 35
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 3.2.3
Forks (GitHub): 9
Stars (GitHub): 35
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Javadocs vs io.github.arvindand/maven-tools-mcp
FactJavadocsio.github.arvindand/maven-tools-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub35
Forks (GitHub) (differs)No figure on GitHub9
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.javadocs.dev/mcp)On your machine (docker.io/arvindand/maven-tools-mcp:latest)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)810
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/arvindand/maven-tools-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Javadocs

In its own words, on Docker MCP Catalog:

Access to Java, Kotlin, and Scala library documentation.

io.github.arvindand/maven-tools-mcp

In its own words, on Official MCP Registry:

JVM dependency intelligence for AI assistants via Maven Central

How to run each

Javadocs As a remote MCP server

Claude Code
claude mcp add --transport http javadocs https://www.javadocs.dev/mcp

io.github.arvindand/maven-tools-mcp As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio maven-tools-mcp -- docker run -i --rm docker.io/arvindand/maven-tools-mcp:latest

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Javadocs has a remote endpoint we check. How we check endpoints

Tools each declares

Only Javadocs declares

  • get_javadoc_index
  • get_javadoc_symbol
  • get_source_file
  • list_javadoc_symbols
  • list_source_files
  • search_artifacts
  • symbol_to_artifact

Only io.github.arvindand/maven-tools-mcp declares

  • analyze_dependency_age
  • analyze_project_health
  • analyze_release_patterns
  • check_multiple_dependencies
  • check_version_exists
  • compare_dependency_versions
  • get_library_docs
  • get_version_timeline
  • resolve_library_id

Both declare

  • get_latest_version

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Javadocs · What it can do: io.github.arvindand/maven-tools-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built