Skip to content
TickerInside logo

TickerInside

Serves dated holdings of every US ETF, sourced from issuer files and SEC filings, through a keyless JSON API and MCP server.

Actively maintained

At a glanceswept Oct 15, 2026

≈ 85visits/mo

Established · estimate, read Oct 15, 2026

For
Investors checking what their ETFs hold, and developers or AI assistants needing US ETF holdings data
Activity
Actively maintainedrelease 3 days ago · site updated 2 days ago
Runs as
API
Used for
  • check how much of a portfolio overlaps across ETFs
  • compare what two ETFs hold in common
  • look through an ETF to its underlying stocks
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP servercom.tickerinside/tickerinside-mcpverified in the MCP registry
  • Stateanswers, 13 toolschecked 2026-10-15
  • Address to connecttickerinside.com/mcp
  • API docstickerinside.com/apithe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use TickerInside for?

Sign in to leave a note
Questions this page answers
  • What is TickerInside?

    Serves dated holdings of every US ETF, sourced from issuer files and SEC filings, through a keyless JSON API and MCP server.

  • Who is TickerInside for?

    Investors checking what their ETFs hold, and developers or AI assistants needing US ETF holdings data

  • Do people use TickerInside?

    Established: ≈ 85 visits/mo · estimate, 2026-10 · 2.4k installs/mo (npm).

  • Is TickerInside still maintained?

    Actively maintained: release 3 days ago · site updated 2 days ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.