Ext Ops Panel
Open dashboard
Comparison

CodeTrendy vs com.mcparmory/codacy

CodeTrendy is an MCP server published by codetrendy.com. Marketplaces we read that list it: 1 (Official MCP Registry). com.mcparmory/codacy is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-28. 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
MarketplaceCodeTrendycom.mcparmory/codacy
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 1.0.3
Downloads/month (PyPI): 824
Downloads/week (PyPI): 160
Forks (GitHub): 4
Stars (GitHub): 32
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.0.3
Downloads/month (PyPI): 824
Downloads/week (PyPI): 160
Forks (GitHub): 4
Stars (GitHub): 32
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

CodeTrendy vs com.mcparmory/codacy
FactCodeTrendycom.mcparmory/codacy
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub32
Forks (GitHub) (differs)No figure on GitHub4
Last releaseNot publishedNot published
Where it runs (differs)Remote server (codetrendy.com/api/mcp)On your machine (mcparmory-codacy)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/mcparmory/registry
Changes in the last 7 days00
First seen (differs)2026-10-202026-10-11
Endpoint at the last check (differs)Responded 39 h 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

CodeTrendy

In its own words, on Official MCP Registry:

Search the CodeTrendy directory of websites and tools. Read-only, no API key.

com.mcparmory/codacy

In its own words, on Official MCP Registry:

Analyze code quality, security issues, and coverage across repositories

How to run each

CodeTrendy As a remote MCP server

Claude Code
claude mcp add --transport http directory https://codetrendy.com/api/mcp

com.mcparmory/codacy As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio codacy -- uvx mcparmory-codacy

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

Only CodeTrendy 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: CodeTrendy · What it can do: com.mcparmory/codacy · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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