Log inSubmit server

Package Registry MCP vs Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch

A side-by-side look at the Package Registry MCP and Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Package Registry MCP logoPackage Registry MCPDatabases · Local subprocess (stdio)MCP server for searching and getting up-to-date information about NPM, Cargo, PyPi, and NuGet packages.64GoodAuth: no auth required
E
Elasticsearch Redis Stack Generator Elasticsearch ElasticsearchDatabasesElasticsearch + Redis Stack Generator (Official Image)36FairAuth: not declared

Verdict: choose Package Registry MCP for databases work as a local process; choose Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch for databases. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Package Registry MCP logoChoose Package Registry MCP when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like get-cargo-package-details, search-cargo-packages, list-cargo-package-versions.
Explore Package Registry MCP

E
Choose Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch when

  • You need dedicated capabilities in the Databases domain.
Explore Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPackage Registry MCP logoPackage Registry MCP
E
Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch
CategoryDatabasesDatabases
Quality signal64/100 · Good36/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars39—
Directory activity 4 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools16Not listed
Full listingView Package Registry MCP View Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch

Tools & capabilities

Package Registry MCP tools 16

  • get-cargo-package-detailsGet detailed information about a specific Cargo package
  • search-cargo-packagesSearch the Cargo registry for packages
  • list-cargo-package-versionsList all versions of a specific Cargo package
  • get-github-advisoryGet detailed information about a specific GitHub Security Advisory by its GHSA ID (e.g., GHSA-grv7-fg5c-xmjg).
  • search-github-advisoriesSearch the GitHub Security Advisory Database for vulnerabilities. Filter by ecosystem (npm, pip, maven, etc.), severity, type, or CVE ID.
  • get-package-advisoriesGet all security advisories affecting a specific package. Use this to check if a package like "braces" or "lodash" has known vulnerabilities.
  • get-golang-package-detailsGet detailed information about a specific Go module/package
  • list-golang-package-versionsList all versions of a specific Go module/package
  • get-npm-package-detailsGet detailed information about a specific NPM package
  • search-npm-packagesSearch the NPM registry for packages
  • list-npm-package-versionsList all versions of a specific NPM package
  • get-nuget-package-detailsGet detailed information about a specific NuGet package
  • +4 more on the listing page

Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Package Registry MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "artmann-package-registry-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "package-registry-mcp"
      ]
    }
  }
}

Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch

No confirmed install command for Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Package Registry MCP is categorized under Databases and uses a local stdio subprocess. Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch belongs to Databases and uses an install path we have not confirmed yet. Pick Package Registry MCP for databases work and Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch for databases.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch has no confirmed install command yet — follow its own setup instructions.

Package Registry MCP is listed as free. Auth: no auth required. Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add artmann-package-registry-mcp and elasticsearch-redis-stack-generator-elasticsearch-elasticsearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Package Registry MCP has a quality signal of 64/100 (Good) with 4 views, 0 installs and 39 GitHub stars. Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch has 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.

Popular comparisons with Package Registry MCP

Popular comparisons with Elasticsearch Redis Stack Generator Elasticsearch Elasticsearch