com.mcparmory/datadog vs Netdata
com.mcparmory/datadog is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). Netdata is an MCP server published by netdata. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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/datadog |  Netdata |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (PyPI): 812 Downloads/week (PyPI): 180 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 2.12.1 Forks (GitHub): 6 673 Stars (GitHub): 80 971 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/datadog | Netdata |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 (worse) | 80 971 (better) |
| Forks (GitHub) (differs) | 4 (worse) | 6 673 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-datadog) | Remote server (app.netdata.cloud/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/netdata/netdata |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (1 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/datadog
Monitor infrastructure, manage agents and deployments, track metrics, logs, and events
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
How to run each
com.mcparmory/datadog As a local MCP server: PyPI package
claude mcp add --transport stdio datadog -- uvx mcparmory-datadogNetdata As a remote MCP server
claude mcp add --transport http netdata https://app.netdata.cloud/api/v1/mcp --header "Authorization: Bearer <YOUR_NETDATA_CLOUD_API_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Netdata 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/datadog · What it can do: Netdata · 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.