resmed-data-mcp vs jDataMunch MCP
resmed-data-mcp is an MCP server published by sfls1397. Marketplaces we read that list it: 1 (npm registry (MCP servers)). jDataMunch MCP is an MCP server published by jgravelle. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-08. 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 |  resmed-data-mcp |  jDataMunch MCP |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 1.1.5 Downloads/month (npm): 1 094 Downloads/week (npm): 520 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.33.0 Downloads/month (PyPI): 730 Downloads/week (PyPI): 510 Forks (GitHub): 20 Stars (GitHub): 83 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.33.0 Downloads/month (PyPI): 730 Downloads/week (PyPI): 510 Forks (GitHub): 20 Stars (GitHub): 83 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 | resmed-data-mcp | jDataMunch MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 83 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 20 (better) |
| Last release (differs) | 2026-10-29 (worse) | 2026-11-05 (better) |
| Where it runs (differs) | On your machine (resmed-data-mcp) | On your machine (jdatamunch-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | MIT | LicenseRef-jDataMunch-Dual-Use |
| Repository (differs) | github.com/sfls1397/resmed-data-mcp | github.com/jgravelle/jdatamunch-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
resmed-data-mcp
Indexer and read-only MCP server for ResMed AirSense CPAP data: reads the SD card over Wi-Fi through a Toshiba FlashAir card, archives every EDF signal in a local SQLite database, and serves it to any MCP client over bearer-token HTTP.
jDataMunch MCP
Tabular data retrieval. Index CSV/Excel, query rows, aggregate. 99%+ savings vs raw file reads.
How to run each
resmed-data-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
jDataMunch MCP As a local MCP server: PyPI package
claude mcp add --transport stdio jdatamunch-mcp -- uvx jdatamunch-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: resmed-data-mcp · What it can do: jDataMunch MCP · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.