Ext Ops Panel
Open dashboard
Comparison

io.github.FinzData/finzdata-mcp vs io.github.axionquant/axionquant

io.github.FinzData/finzdata-mcp is an MCP server published by FinzData. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.axionquant/axionquant is an MCP server published by axionquant. 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

Where each is published
Marketplaceio.github.FinzData/finzdata-mcpio.github.axionquant/axionquant
Official MCP Registry Listed
Version: 0.2.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 125
Not marked · First seen
Listed
Version: 1.1.2
Downloads/month (npm): 567
Downloads/week (npm): 288
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.FinzData/finzdata-mcp vs io.github.axionquant/axionquant
Factio.github.FinzData/finzdata-mcpio.github.axionquant/axionquant
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (api.finzdata.com/mcp)On your machine (@axionquant/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/axionquant/mcp-server
Changes in the last 7 days (differs)70
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)not checked yetno 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

io.github.FinzData/finzdata-mcp

In its own words, on Official MCP Registry:

US market data, point-in-time fundamentals, macro vintages, COT, 13F and backtests for AI agents.

io.github.axionquant/axionquant

In its own words, on Official MCP Registry:

MCP server for AxionQuant financial data, including market, economic, SEC filing, and company data.

How to run each

io.github.FinzData/finzdata-mcp As a remote MCP server

Claude Code
claude mcp add --transport http finzdata-mcp https://api.finzdata.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: FINZDATA_API_KEY (secret), Authorization header

io.github.axionquant/axionquant As a local MCP server: npm package

Claude Code
claude mcp add --env "YOUR_API_KEY=<YOUR_YOUR_API_KEY>" --transport stdio axionquant -- npx -y @axionquant/mcp

Requires: YOUR_API_KEY (secret)

Commands 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

Only io.github.FinzData/finzdata-mcp asks for

  • FINZDATA_API_KEY (secret)

Only io.github.axionquant/axionquant asks for

  • YOUR_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.FinzData/finzdata-mcp · What it can do: io.github.axionquant/axionquant · 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.

Where the data comes from: how the catalog is built