MCP connector at mcp.tipranks.com · Production

TipRanks financial data - built for AI agents

Plug Claude, ChatGPT, Cursor, or any MCP client into live analyst ratings, Smart Score, technicals, earnings, and your TipRanks portfolios. One URL, OAuth or API key, ready in 60 seconds.

Free tier · no credit card required.

Same TipRanks data that powers research at 100+ banks, brokers, and exchanges - including Robinhood, E*TRADE, Interactive Brokers, Santander, and TMX - plus tipranks.com (10M+ monthly users).

curl -X POST https://mcp.tipranks.com/dev/api/signup \
  -H 'content-type: application/json' \
  -d '{"email":"agent@example.com","password":"<10+ chars, 3 of: lower/upper/digit/symbol>","accept_terms":true,"label":"my-agent"}'

What you can do

See it in action

Real screenshots of Claude.ai using this connector. Each one is a single prompt - the chart, dashboard, or table is rendered inline by Claude's Analysis tool from JSON returned by TipRanks MCP tools.

See the full playbook catalog ↓

Ready to plug it in? Connect any MCP client in about a minute.

Free tier · no credit card required.

Quickstart

Two ways to authenticate. Pick whichever fits the client.

Remote - OAuth (recommended for Claude.ai & Claude Desktop)

https://mcp.tipranks.com/mcp/

Sign in with your TipRanks account when the client prompts. Grants tipranks:portfolio if you opt in.

Remote - API key (recommended for ChatGPT, Cursor, Codex, agents)

https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY

Get a free key at /dev/signup or via the JSON API (see Run locally).

Claude.ai (web & desktop)

The full OAuth flow - sign in with TipRanks, approve scopes, done. Claude.ai handles token refresh automatically.

1. Open Claude.ai → Settings → Connectors (or the connector panel in Claude Desktop).
2. Click Add custom connector.
3. Enter the URL: https://mcp.tipranks.com/mcp/
4. Click Connect. A new tab opens to TipRanks for sign-in (skipped if you already have a TipRanks session).
5. On the consent screen, approve tipranks:read (market data) and optionally tipranks:portfolio (your TipRanks portfolios).

You'll need a TipRanks account. Free, Premium, and Ultimate plans all work; per-account monthly quotas differ - see Scopes & quotas.

Claude Desktop config file

If you prefer editing the config file directly (or you're on an older Claude Desktop build that only supports stdio), point at the hosted server through the mcp-remote proxy with your API key:

{
  "mcpServers": {
    "tipranks": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY"
      ]
    }
  }
}

Replace YOUR_API_KEY with the key shown after signup. Save the file at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Restart Claude Desktop and the tipranks tools appear in the 🎲 menu.

Claude Code CLI

One command - works against the hosted server. Replace YOUR_API_KEY with a real key.

claude mcp add -t http tipranks https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY

Or, if you'd rather use OAuth (and don't mind the consent screen popping up in your browser):

claude mcp add -t http tipranks https://mcp.tipranks.com/mcp/

List or remove later with claude mcp list / claude mcp remove tipranks.

ChatGPT

TipRanks is approved in the ChatGPT plugin directory, so the simplest path is to install it there — no developer-mode setup. You connect over OAuth: sign in with your TipRanks account and approve the requested scopes. (ChatGPT's connector framework uses OAuth 2.1 for authenticated apps; TipRanks supports it natively, with dynamic client registration and PKCE.)

1. Open ChatGPT → Settings → Plugins (or the Plugins entry in the sidebar).
2. Search for TipRanks in the plugin directory and open it.
3. Click Install. When prompted to connect, you'll be sent to TipRanks to sign in and approve tipranks:read (market data) and optionally tipranks:portfolio (your TipRanks portfolios).
4. Start a new chat, then call TipRanks by name or from the tools menu.

Advanced: add it manually (developer mode)

Only needed if TipRanks isn't in your plugin directory yet and you want to add the connector by hand. It still uses OAuth — ChatGPT authenticates connectors with your TipRanks sign-in, not an API key.

1. Open ChatGPT → Settings → Apps & Connectors.
2. Enable Developer mode under Advanced settings, then click Create.
3. MCP Server URL: https://mcp.tipranks.com/mcp/
4. Authentication: OAuth — you'll be sent to TipRanks to sign in and approve access.

Cursor

Edit ~/.cursor/mcp.json (user-wide) or .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "tipranks": {
      "url": "https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY"
    }
  }
}

Reload Cursor and the tools appear under the MCP indicator.

VS Code

Add an HTTP MCP server in .vscode/mcp.json (workspace) or the user-level equivalent:

{
  "servers": {
    "tipranks": {
      "type": "http",
      "url": "https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY"
    }
  }
}

OpenAI Codex

Codex CLI reads ~/.codex/config.toml. Use the mcp-remote proxy because Codex's MCP transport is stdio-only:

[mcp_servers.tipranks]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY"]

Gemini CLI

One-shot command:

gemini mcp add -t http tipranks https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY

Or edit ~/.gemini/settings.json directly:

{
  "mcpServers": {
    "tipranks": {
      "httpUrl": "https://mcp.tipranks.com/mcp/?apikey=YOUR_API_KEY"
    }
  }
}

Run locally / programmatic signup

Programmatic signup (one HTTP call, no email verification)

Agents and CI jobs can mint a free-tier key in one round-trip. Password must be at least 10 characters and include at least three of: lowercase, uppercase, digit, symbol. Pass "accept_terms": true to accept the MCP Terms of Service — it's required, exactly like ticking the box on the web signup form.

The free tier is rate-limited (10 rpm / 50 per month) so abuse is bounded without an email-verification gate. Email here is an account identifier. The web signup form does require email verification before you can sign in to manage keys via /dev/keys; the API endpoint trades that for one-call usability.

POST https://mcp.tipranks.com/dev/api/signup
Content-Type: application/json

{ "email": "you@example.com", "password": "Aa1!aaaaaaaa", "accept_terms": true, "label": "my-agent" }

Returns 201 with a usable key:

{
  "account_id": "dev_...",
  "api_key": "tr_live_...",
  "tier": "free",
  "rpm_limit": 10,
  "monthly_limit": 50,
  "manage_url": "https://mcp.tipranks.com/dev/login",
  "mcp_url": "https://mcp.tipranks.com/mcp"
}

Scopes & quotas

OAuth users (connector)

Tool calls are counted per calendar month per TipRanks user. Quota resets on the 1st of every month (UTC).

Have a paid MCP subscription? A Smart, Advanced, or Professional API-key plan on the same email as your TipRanks login also lifts this connector quota — to 1,000, 2,500, or 6,000 calls/month respectively — so you don't have to switch to an API key to spend your paid allowance.

Changed your TipRanks access after connecting? Your tier is captured when you authorize, so an updated plan applies once we re-read it: just open the developer dashboard while signed in to TipRanks, or reconnect the connector in your client. Either picks up the updated quota — no need to wait for the monthly reset.

API key users

Per-key rate limits. The monthly cap is the value meter that separates tiers; a per-minute burst guard keeps a runaway agent from hammering the API in a tight loop.

Hitting any cap returns HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Window, and Retry-After headers so clients can back off intelligently. Manage your plan from the developer portal; updated limits cascade onto every active API key on your account.

To check where you stand at any point, just ask - the get_my_usage tool reports calls used this month, your limit, how many remain, your plan tier, and when the quota resets (UTC). It's free: calling it never counts against the quota.

Example prompts

Once connected, ask the model questions like these. The tool calls happen automatically.

Playbooks

The examples above are single questions. The connector really shines on multi-step research workflows - Claude calls one tool, looks at the result, calls another, then synthesizes. These are copy-pasteable starting points; tweak tickers / sectors / time windows to match what you're after.

Charts & visualizations

You don't need anything special on the connector side to get charts - that part comes from the client.

On Claude.ai and Claude Desktop, the built-in Analysis tool (a sandboxed JS/Python runtime) can take any time-series data an MCP tool returns and render it as a chart in the conversation. Just ask - e.g. “chart NVDA's daily close for the past year with 50- and 200-day moving averages” - and Claude will call the relevant tool (here get_assets_data or one of the historical tools), pipe the JSON through the Analysis tool, and produce a plot inline. The same works for technical indicators, multi-asset comparisons, and portfolio performance breakdowns.

Tools that produce chart-friendly output include the historical OHLCV endpoints (get_commodity_historical, get_forex_historical, get_crypto_historical, get_index_historical), the per-ticker financial statements time series (get_financials), the per-ticker earnings and dividend time series (get_earnings_history, get_dividend_history), the per-ticker buyback series (get_buybacks with a ticker argument), and the portfolio performance tools (get_portfolio_performance, get_portfolio_overview).

Build your own agent

The connector works in any MCP client, but you can also drive it straight from code. Point the Anthropic Messages API at mcp.tipranks.com as a remote MCP server, hand it your API key, and Claude calls the TipRanks tools on its own - no per-tool wiring on your side.

Here's the whole integration - give it a ticker, and Claude pulls analyst ratings, financials, technicals, and smart-money data to write a research memo:

import anthropic

client = anthropic.Anthropic()  # reads ANTHROPIC_API_KEY

resp = client.beta.messages.create(
    model="claude-opus-4-8",
    max_tokens=8000,
    betas=["mcp-client-2025-11-20"],
    system="You are an equity research analyst. Use the tools to gather "
           "analyst ratings, financials, technicals, and smart-money flows, "
           "then write a due-diligence memo. Informational only.",
    mcp_servers=[{
        "type": "url",
        "url": "https://mcp.tipranks.com/mcp/",
        "name": "tipranks",
        "authorization_token": "tr_live_...",   # your API key
    }],
    tools=[{"type": "mcp_toolset", "mcp_server_name": "tipranks"}],
    messages=[{"role": "user", "content": "Produce a due-diligence memo on NVDA."}],
)
print("".join(b.text for b in resp.content if b.type == "text"))

The full runnable example - it prints the TipRanks tools Claude calls, then the memo, and handles the pause_turn resume loop - is on GitHub: TipRanks/mcp → examples/due-diligence-agent.

More reference agents live in the same repo under examples/: an earnings-season companion (ticker → earnings brief) and a smart-money screener (a ranked shortlist of ideas hedge funds and insiders are buying). Fork one and make it yours.

Tools reference

Every tool is read-only, idempotent, and returns JSON. Categories follow the structure of server.py.

Asset data

Discovery & screening

Alternative data & signals

Signals beyond price and ratings - what political / insider / hedge-fund money is doing, where the biotech catalysts are, who's buying back stock.

Macro & calendars

Technical analysis

ETFs

Commodities

Forex

Indices

Crypto

Options

Quotes are typically delayed ~15 minutes. Greeks and implied volatility are not exposed by this data source.

Portfolios requires tipranks:portfolio

Privacy & support

The full connector-specific privacy policy is at /privacy. It supplements the broader TipRanks privacy policy which governs your TipRanks account itself. Your use of this connector is governed by the MCP Terms of Service.

In short: we store hashed OAuth tokens, your TipRanks user ID / email / tier, the portfolio IDs you authorized, and a per-user monthly request counter. We do not store tool-call payloads, the financial data we return, or your TipRanks credentials - sign-in happens on tipranks.com, never here.

Authentication: standard OAuth 2.1 with Dynamic Client Registration (RFC 7591) and PKCE-S256. Public clients only (token_endpoint_auth_method=none). Discovery at:

GET https://mcp.tipranks.com/.well-known/oauth-authorization-server

Tokens are SHA-256 hashed at rest; refresh tokens rotate on use, with chain-revocation on replay.

• Connection or auth issues: open a ticket in your TipRanks account.
• API behavior bugs or feature requests: support@tipranks.com.
• Privacy / data subject requests: see the privacy policy.

Last updated: 2026-05-19 · Hosted at https://mcp.tipranks.com/docs