TickerInside
NPM · TICKERINSIDE-MCP · SCANNED SEP 25
Holdings, overlap, correlation and look-through risk for US ETFs, from issuer files, with no key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 836 tokens (~104/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TickerInside MCP server?
TickerInside runs locally as an npm package, launched with npx -y tickerinside-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tickerinside-mcp
claude mcp add com-tickerinside-tickerinside-mcp -- npx -y tickerinside-mcp
{
"mcpServers": {
"com-tickerinside-tickerinside-mcp": {
"command": "npx",
"args": [
"-y",
"tickerinside-mcp"
]
}
}
} {
"servers": {
"com-tickerinside-tickerinside-mcp": {
"command": "npx",
"args": [
"-y",
"tickerinside-mcp"
]
}
}
} codex mcp add com-tickerinside-tickerinside-mcp -- npx -y tickerinside-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tickerinside-tickerinside-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tickerinside-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-tickerinside-tickerinside-mcp --command npx --arg -y --arg tickerinside-mcp
mcp_servers:
com-tickerinside-tickerinside-mcp:
command: "npx"
args: ["-y", "tickerinside-mcp"] {
"McpServers": {
"com-tickerinside-tickerinside-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tickerinside-mcp"
]
}
}
} assistant mcp add com-tickerinside-tickerinside-mcp -t stdio -c npx -a -y tickerinside-mcp
{
"mcpServers": {
"com-tickerinside-tickerinside-mcp": {
"command": "npx",
"args": [
"-y",
"tickerinside-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 7 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 6 Sept 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/tickerinside-mcp@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_funds Compare two funds ~74
Any two covered funds, not only the pairs the website has written about. Returns holdings overlap measured three ways, correlation and covariance from weekly returns, and the cost, return and risk of each.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | A US ETF ticker, for example VOO. Case does not matter. |
| b | – | yes | – |
No output schema declared.
No examples provided.
compare_stocks Compare two stocks ~144
Any two US stocks with three years of price history, about 4,700 of them and any of the eleven million pairs. Market cap, valuation, returns, drawdown, volatility and beta side by side, the correlation of their weekly returns, and every covered fund that holds both with the weight of each. A fund ticker works on either side: a stock against a fund adds whether the fund holds it, at what weight and rank. For two funds use compare_funds, which also measures holdings overlap.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | A US stock ticker, for example NVDA. A fund ticker also works. |
| b | string | yes | The other ticker. |
No output schema declared.
No examples provided.
fund_profile Fund profile ~93
One fund: cost, assets, returns over one, three and five years, volatility, beta, worst fall, concentration, and its largest positions with weights. Every figure carries the date of the file it came from.
| Name | Type | Req | Description |
|---|---|---|---|
| holdings | integer | – | How many of the largest positions to return. 0 for none. |
| ticker | string | yes | A US ETF ticker, for example VOO. Case does not matter. |
No output schema declared.
No examples provided.
list_funds List covered funds ~35
Every fund this server can answer for, with the date of the data. Call this first when a ticker might not be covered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
look_through What a portfolio really holds ~124
Look through a list of funds to the companies underneath. Returns how much of each company the portfolio carries, in percent and, when amounts are given, in money, along with which funds it comes through. This is the question a holder actually has.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | The currency the amounts are in, for example USD or EUR. Echoed back so the answer is never a number without a unit. Amounts must all be in one currency; nothing is converted. |
| positions | array | yes | – |
| top | integer | – | How many companies to return. |
No output schema declared.
No examples provided.
overlap_matrix Overlap across a basket ~51
Every pair in a list of funds, ranked by how much of their combined weight sits in the same companies. Use it to find which lines in a portfolio duplicate each other.
| Name | Type | Req | Description |
|---|---|---|---|
| tickers | array | yes | – |
No output schema declared.
No examples provided.
risk_decomposition Where a portfolio's risk sits ~122
Portfolio volatility, and each position's share of the risk by Euler decomposition, which sums to 100. Also the squared diversification ratio, which counts positions that behave differently rather than positions held. A line whose share of risk exceeds its share of capital is doing more of the moving than its size suggests.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | The currency the amounts are in, for example USD or EUR. Echoed back so the answer is never a number without a unit. Amounts must all be in one currency; nothing is converted. |
| positions | array | yes | – |
No output schema declared.
No examples provided.
stock_exposure Which funds hold a company ~72
For one company, every covered fund that holds it and at what weight, heaviest first. The look-through in reverse, and the answer to how much of something a holder already owns without knowing it.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | A company ticker as it appears in issuer holdings files, for example NVDA. |
No output schema declared.
No examples provided.
What is the TickerInside MCP server?
TickerInside is an MCP server listed in the public MCP registry as com.tickerinside/tickerinside-mcp. Holdings, overlap, correlation and look-through risk for US ETFs, from issuer files, with no key. This page covers its npm package (tickerinside-mcp).
Is the TickerInside MCP server safe to use?
TickerInside scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TickerInside MCP server expose?
TickerInside exposes 8 tools: list_funds, fund_profile, compare_funds, overlap_matrix, look_through, and 3 more. Their descriptions and schemas cost roughly 715 tokens of context every time the server is loaded.
Is the TickerInside MCP server still maintained?
TickerInside is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TickerInside MCP server under?
TickerInside declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.