mcp-server-pacman
Related Servers
Alternatives to mcp-server-pacman
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceModel Context Protocol server for npm registry. Enables searching packages, checking security, comparing versions, and validating compatibility.1246 npm3MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for querying package registries (npm, PyPI, crates.io) to retrieve metadata, release timelines, and maintenance signals.1-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for querying PyPI package information, dependencies, and compatibility checking. Supports advanced dependency analysis, download statistics, and trending analysis.34 PyPI18MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server for checking package versions and metadata across multiple package managers including npm, PyPI, Maven, NuGet, RubyGems, Crates.io, and Go modules.642 npm1MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server for the JSR (JavaScript Registry)4MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that allows interaction with the RubyGems.org API to fetch metadata about Ruby packages, search gems, and explore dependencies and ownership information.61-
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: Docker images have separate search and info tools, packages similarly, and Terraform modules have a dedicated version lookup. No overlap between resources.
Names use snake_case but the ordering of resource and action varies: e.g., 'docker_image_info' (resource_action) vs 'search_docker_image' (action_resource). 'terraform_module_latest_version' uses a different pattern with an adjective. This inconsistency could cause confusion.
With 5 tools, the server is focused and well-scoped for an informational package manager. It covers Docker, general packages, and Terraform modules without being too sparse.
The server provides search and info for Docker and packages, which is reasonable for an informational tool. However, only one Terraform module operation exists, and missing CRUD operations like install or delete are on the boundary of the domain.