Other · Remote MCP server
TickerInside
Holdings, overlap, correlation and look-through risk for US ETFs, from issuer files, with no key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.tickerinside/tickerinside-mcp- Version
- 1.7.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.tickerinside
- Namespace
- Namespace verified by the MCP Registry via the domain tickerinside.com · how
- Website
- tickerinside.com/agent/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tickerinside.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- tickerinside 1.7.1 · protocol 2025-06-18
- Tools discovered
- 11:
list_funds,fund_profile,compare_funds,overlap_matrix,look_through,risk_decomposition,stock_exposure,compare_stocks,etf_ownership,fund_history,fund_changes - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | tickerinside-mcp | 1.7.1 | stdio |
How to connect TickerInside
TickerInside is a remote MCP server: there is nothing to install. Its endpoint is https://tickerinside.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: tickerinside-mcp version 1.7.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y tickerinside-mcp@1.7.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tickerinside-mcp": {
"command": "npx",
"args": [
"-y",
"tickerinside-mcp@1.7.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ThryxProtocol MCP ServerThryxProtocol v3.1 - gasless AI agent launchpad on Base. 21 tools wrap thryx.fun HTTP API. | Local · stdio |
| ThumbGatePre-action gates that block AI agents from repeating known mistakes. | Local · stdio |
| Tick MCPA time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies. | Remote · HTTPLive check: ✓ handshake |
| TickerFactsSEC EDGAR fundamentals as agent tools: look up or screen US public companies. Free, no key, CC0. | Remote · HTTPLive check: ✓ handshake |
| TickerrLive status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Tickwind US Market BoardsNo-API-key US market boards from SEC, Cboe, FINRA and CFTC: options flow, insiders, 13F, buybacks. | Remote · HTTPLive check: ✓ handshake |
| TidebaseInspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant. | Local · stdio |
| TidelightA shared island world for agents to explore, discover, craft and build together. | Remote · HTTPLive check: ✓ handshake |