The AI-native interface to Fintel’s institutional financial intelligence. Access structured market data, ownership, and insider intelligence via the Model Context Protocol.
https://mcp.fintel.io/mcp
Query institutional financial datasets through the Model Context Protocol, designed specifically for AI-agent integrations.
Clean, structured JSON responses suitable for tools, research copilots, and automation workflows.
Clients automatically discover available tools, parameters, and descriptions via the standardized MCP interface.
MCP and REST share the same underlying data, auth, entitlements, and stability. One backend, two front doors.
Billing-grade usage metering and account-aware access control for production-ready agent deployments.
Rich provenance and freshness metadata where available, giving agents the context they need for financial analysis.
Security master and identifier lookup (ticker, CUSIP, ISIN, FIGI). Profile data and listing history.
Country and exchange discovery for covered active securities.
End-of-day price bars and historical market data trends.
Institutional ownership and 13F-derived data from SEC filings.
Reported insider transactions from SEC Form 3, 4, and 5-derived data.
Short interest, borrow-rate, short-volume, and fails-to-deliver datasets, with some datasets subject to account-level availability.
Access account-scoped watchlists and resources via the authenticated live catalog.
Access personal alerts and team collaboration tools via the authenticated live catalog.
The public catalog is unauthenticated and intended for capability discovery. Authenticating with your API key below will reveal the live catalog—the exact tools and entitlements available for your account.
Enter your API key to load the authoritative MCP tool list for your account.
X-API-KEY header and is not stored by this page.
Authenticated live discovery may count as authenticated usage.
The Fintel MCP server uses JSON-RPC 2.0 over HTTP POST. Connect your MCP-compatible client (like Claude Desktop or an MCP-aware IDE) using the following configuration. Most MCP clients handle JSON-RPC framing automatically.
Canonical MCP Endpoint: https://mcp.fintel.io/mcp
Secondary Compatible Endpoint: https://api.fintel.io/mcp
All tool calls require an API key passed via the X-API-KEY header. Tool calls are account-aware and subject to entitlements.
X-API-KEY: YOUR_API_KEY
POST /mcp
Content-Type: application/json
X-API-KEY: YOUR_API_KEY
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}