# TickerInside (npm · tickerinside-mcp)

Holdings, overlap, correlation and look-through risk for US ETFs, from issuer files, with no key.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `tickerinside-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-tickerinside-tickerinside-mcp/tickerinside-mcp.md), [page](https://verifymcp.io/servers/com-tickerinside-tickerinside-mcp/tickerinside-mcp)

## Channel facts

- Registry: `npm`
- Package: `tickerinside-mcp`
- Version: `1.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 18 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 836 tokens (~104/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-tickerinside-tickerinside-mcp -- npx -y tickerinside-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-tickerinside-tickerinside-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tickerinside-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tickerinside-tickerinside-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tickerinside-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-tickerinside-tickerinside-mcp -- npx -y tickerinside-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tickerinside-tickerinside-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tickerinside-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tickerinside-tickerinside-mcp --command npx --arg -y --arg tickerinside-mcp
```

### Hermes

```yaml
mcp_servers:
  com-tickerinside-tickerinside-mcp:
    command: "npx"
    args: ["-y", "tickerinside-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-tickerinside-tickerinside-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tickerinside-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tickerinside-tickerinside-mcp -t stdio -c npx -a -y tickerinside-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-tickerinside-tickerinside-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tickerinside-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 72, +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.

### 2026-09-21 (score 71, +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.

### 2026-09-18 (score 70, +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.

### 2026-09-16 (score 69, +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.

### 2026-09-14 (score 68, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 64, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-06 (score 49)

First indexed and scored.

## MCP tools (8)

### `list_funds` (~35 tokens)

List covered funds

Every fund this server can answer for, with the date of the data. Call this first when a ticker might not be covered.

### `fund_profile` (~93 tokens)

Fund profile

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.

Input parameters:

- `holdings` (integer): How many of the largest positions to return. 0 for none.
- `ticker` (string, required): A US ETF ticker, for example VOO. Case does not matter.

### `compare_funds` (~74 tokens)

Compare two funds

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.

Input parameters:

- `a` (string, required): A US ETF ticker, for example VOO. Case does not matter.
- `b` (required)

### `overlap_matrix` (~51 tokens)

Overlap across a basket

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.

Input parameters:

- `tickers` (array, required)

### `look_through` (~124 tokens)

What a portfolio really holds

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.

Input parameters:

- `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, required)
- `top` (integer): How many companies to return.

### `risk_decomposition` (~122 tokens)

Where a portfolio's risk sits

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.

Input parameters:

- `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, required)

### `stock_exposure` (~72 tokens)

Which funds hold a company

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.

Input parameters:

- `ticker` (string, required): A company ticker as it appears in issuer holdings files, for example NVDA.

### `compare_stocks` (~144 tokens)

Compare two stocks

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.

Input parameters:

- `a` (string, required): A US stock ticker, for example NVDA. A fund ticker also works.
- `b` (string, required): The other ticker.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-tickerinside-tickerinside-mcp/tickerinside-mcp#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 71
- 2026-09-21: 71
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 64
- 2026-09-12: 64
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 49

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/tickerinside-mcp
- Socket report: https://socket.dev/npm/package/tickerinside-mcp
- Website: https://tickerinside.com/agent/
- Changelog RSS feed: https://verifymcp.io/servers/com-tickerinside-tickerinside-mcp/tickerinside-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tickerinside-tickerinside-mcp/tickerinside-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-tickerinside-tickerinside-mcp/tickerinside-mcp