tickerinside-mcp

MCPcommunitylive
v1.9.0com.tickerinsideMITUpdated todaynpm

Holdings, overlap, correlation and look-through risk for US ETFs. Free data, no key.

Endpoint healthlive
checked 11 days ago · 169ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1kDownloads/wk
todayLast update
Package
Authorcom.tickerinside
LicenseMIT
Version1.9.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface21 tools · none privileged
Security scan✓ Cleanv1.10.0 · todayHow well does this scan work?
EvalsNone
IndexedSep 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

21 tools · none privileged
Statically extracted from the published packagev1.10.0 · 11h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_etf_flowsNo description published

This tool published no description. Forge does not invent one.

get_etf_holdings_historyNo description published

This tool published no description. Forge does not invent one.

get_etf_holdings_changesNo description published

This tool published no description. Forge does not invent one.

tickerinsideNo description published

This tool published no description. Forge does not invent one.

list_etfsNo description published

This tool published no description. Forge does not invent one.

get_etf_holdingsNo description published

This tool published no description. Forge does not invent one.

compare_etfsNo description published

This tool published no description. Forge does not invent one.

get_etf_overlap_matrixNo description published

This tool published no description. Forge does not invent one.

get_etf_portfolio_lookthroughNo description published

This tool published no description. Forge does not invent one.

get_etf_portfolio_riskNo description published

This tool published no description. Forge does not invent one.

find_etfs_holding_stockNo description published

This tool published no description. Forge does not invent one.

compare_stocksNo description published

This tool published no description. Forge does not invent one.

get_etf_ownershipNo description published

This tool published no description. Forge does not invent one.

what_does_this_etf_holdAsks what one US ETF holds, with the weight of each holding, its cost and size, and the date of its holdings file.

Asks what one US ETF holds, with the weight of each holding, its cost and size, and the date of its holdings file.

No input schema was published for this tool.

tickerA US ETF ticker, for example VOO or SCHD. Case does not matter.

A US ETF ticker, for example VOO or SCHD. Case does not matter.

No input schema was published for this tool.

which_etfs_hold_this_stockAsks which US ETFs hold one stock and at what weight, heaviest first, each with the date of its holdings file.

Asks which US ETFs hold one stock and at what weight, heaviest first, each with the date of its holdings file.

No input schema was published for this tool.

do_my_etfs_overlapAsks how much two to thirty US ETFs hold in common, by weight, and which of them duplicate each other.

Asks how much two to thirty US ETFs hold in common, by weight, and which of them duplicate each other.

No input schema was published for this tool.

tickersTwo to thirty US ETF tickers separated by commas, for example VOO,QQQ,SCHD. In Claude Code, type the list without spaces.

Two to thirty US ETF tickers separated by commas, for example VOO,QQQ,SCHD. In Claude Code, type the list without spaces.

No input schema was published for this tool.

what_is_inside_my_etf_portfolioAsks which companies a portfolio of US ETFs holds underneath, how much of each, and which funds each one comes through.

Asks which companies a portfolio of US ETFs holds underneath, how much of each, and which funds each one comes through.

No input schema was published for this tool.

holdingsThe ETFs of the portfolio, 1 to 60, separated by commas, each with the amount held after a colon, for example VOO:60,QQQ:40 or VOO:40000,QQQ:25000. Give an amount for every fund or for none; with none, every fund counts equally. In Claude Code, type the list without spaces.

The ETFs of the portfolio, 1 to 60, separated by commas, each with the amount held after a colon, for example VOO:60,QQQ:40 or VOO:40000,QQQ:25000. Give an amount for every fund or for none; with none, every fund counts equally. In Claude Code, type the list without spaces.

No input schema was published for this tool.

are_etfs_buying_this_stockAsks whether the US ETFs read daily from their issuers' files bought or sold one stock on the latest market close, and the value of that change.

Asks whether the US ETFs read daily from their issuers' files bought or sold one stock on the latest market close, and the value of that change.

No input schema was published for this tool.

8 of 21 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Holdings, overlap, correlation and look-through risk for US ETFs. Free data, no key.

Keywords
mcpmodelcontextprotocoletfholdingsoverlapportfoliocorrelationfinance
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-09 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in finance & trading