com.mcparmory/codacy vs hotpath-cloud
com.mcparmory/codacy is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). hotpath-cloud is an MCP server published by hotpath.rs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
| Marketplace |  com.mcparmory/codacy |  hotpath-cloud |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (PyPI): 824 Downloads/week (PyPI): 155 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.0.3 Forks (GitHub): 64 Stars (GitHub): 1 921 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
| Fact | com.mcparmory/codacy | hotpath-cloud |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 (worse) | 1 921 (better) |
| Forks (GitHub) (differs) | 4 (worse) | 64 (better) |
| Last release (differs) | Not published | 2026-11-08 |
| Where it runs (differs) | On your machine (mcparmory-codacy) | Remote server (hotpath.rs/api/v1/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/hotpath-rs/hotpath |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-11 | 2026-11-07 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 27 h ago |
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
com.mcparmory/codacy
Analyze code quality, security issues, and coverage across repositories
hotpath-cloud
Read-only access to Rust profiling reports from CI: benchmark history, diffs and policies
How to run each
com.mcparmory/codacy As a local MCP server: PyPI package
claude mcp add --transport stdio codacy -- uvx mcparmory-codacyhotpath-cloud As a remote MCP server
claude mcp add --transport http hotpath-cloud https://hotpath.rs/api/v1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only hotpath-cloud has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: com.mcparmory/codacy · What it can do: hotpath-cloud · Compare two other plugins
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.