Ext Ops Panel
Open dashboard
Comparison

EODHD Claude Skills vs com.mcparmory/polygon

EODHD Claude Skills is a plugin bundle for AI coding tools published by EOD Historical Data. Marketplaces we read that list it: 1 (Community GitHub marketplaces). com.mcparmory/polygon 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
MarketplaceEODHD Claude Skillscom.mcparmory/polygon
Community marketplace eodhistoricaldata/eodhd-claude-skills Listed
Version: 0.8.0
Forks (GitHub): 12
Stars (GitHub): 47
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (PyPI): 828
Downloads/week (PyPI): 151
Forks (GitHub): 4
Stars (GitHub): 32
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.0.2
Downloads/month (PyPI): 828
Downloads/week (PyPI): 151
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

EODHD Claude Skills vs com.mcparmory/polygon
FactEODHD Claude Skillscom.mcparmory/polygon
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)47 (better)32 (worse)
Forks (GitHub) (differs)12 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.eodhd.com/v2/mcp)On your machine (mcparmory-polygon)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)15Not a bundle
LicenceMITMIT
Repository (differs)github.com/eodhistoricaldata/eodhd-claude-skillsgithub.com/mcparmory/registry
Changes in the last 7 days00
First seen (differs)2026-10-172026-10-11
Endpoint at the last check (differs)Responded 5 days ago, requires a keyno 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

EODHD Claude Skills

In its own words, on Community GitHub marketplaces:

Core EODHD financial data skill — historical prices, fundamentals, options, technicals, news, sentiment, macro indicators, ESG, risk analytics, Treasury rates, and more

com.mcparmory/polygon

In its own words, on Official MCP Registry:

Access stock, crypto, and ETF market data, analyst ratings, earnings, and financial news

How to run each

EODHD Claude Skills As a Claude Code plugin

Claude Code
/plugin marketplace add eodhistoricaldata/eodhd-claude-skills
/plugin install eodhd-api@eodhd-claude-skills

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

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

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

Only EODHD Claude Skills 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: EODHD Claude Skills · What it can do: com.mcparmory/polygon · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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