About Intrinio
Intrinio is an MCP server for accessing options data and analyst estimates from Intrinio. It is intended for financial-data workflows and offers a local stdio option as well as a Pipeworx gateway endpoint.
Key features
- 01Options chains with Greeks and implied volatility
- 02Unusual options activity and sentiment
- 03Analyst EPS estimate consensus
- 04Analyst target-price consensus
Use cases
- 01Reviewing option contracts for a symbol and expiry
- 02Tracking unusual options trades and premiums
- 03Checking analyst earnings estimates
- 04Comparing analyst price targets
MCP support
Exposes four Intrinio data tools to MCP clients through a Pipeworx remote endpoint or a standalone stdio server. Calls require the user's own API key.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/intrinio/mcpclaude mcp add --transport http pipeworx-io-intrinio https://gateway.pipeworx.io/intrinio/mcp{"mcpServers":{"pipeworx-io-intrinio":{"type":"http","url":"https://gateway.pipeworx.io/intrinio/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-intrinio":{"type":"http","url":"https://gateway.pipeworx.io/intrinio/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-intrinio":{"type":"http","url":"https://gateway.pipeworx.io/intrinio/mcp"}}}{"mcpServers":{"pipeworx-io-intrinio":{"serverUrl":"https://gateway.pipeworx.io/intrinio/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
45| Parameter | Type | Required | Description |
|---|---|---|---|
| q | string | No | Alias for question. |
| ask | string | No | Alias for question. |
| text | string | No | Alias for question. |
| input | string | No | Alias for question. |
| packs | array | No | OPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer). |
| query | string | No | Alias for question. |
| prompt | string | No | Alias for question. |
| message | string | No | Alias for question. |
| question | string | Yes | Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
Details
From the project READMEmcp-intrinio
Intrinio MCP — premium financial data (intrinio.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1881+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
intrinio_options_chain | Options chain with greeks and implied volatility for a symbol at a given expiration — returns strike, type, bid/ask/last, volume, open interest, delta, and IV per contract. Example: intrinio_options_chain({ symbol: "AAPL", expiration: "2026-01-16", _apiKey: "your-key" }) |
intrinio_unusual_options | Unusual options activity for a symbol — large/block/sweep trades flagged by Intrinio with bullish/bearish sentiment, total premium value, and the contract traded. Intrinio's signature feed for options flow. Example: intrinio_unusual_options({ symbol: "AAPL", source: "delayed", _apiKey: "your-key" }) |
intrinio_analyst_estimates | Zacks analyst EPS estimates for a company — consensus mean/high/low EPS estimate, number of analysts, and fiscal period. Example: intrinio_analyst_estimates({ symbol: "AAPL", _apiKey: "your-key" }) |
intrinio_target_price | Zacks target-price consensus for a company — mean/high/low/median analyst price targets and the number of estimates. Example: intrinio_target_price({ symbol: "AAPL", _apiKey: "your-key" }) |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"intrinio": {
"url": "https://gateway.pipeworx.io/intrinio/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/intrinio/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1881+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/intrinio_options_chain. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"intrinio": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-intrinio"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-intrinio
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Intrinio data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.