PredixLab
Sinais de ações dos EUA, screeners e análise de opções via MCP. Não é aconselhamento de investimento.
Servidor MCP hospedado
npx add-mcp 'https://api.predixlab.com/mcp/'Instala no Claude Code, Codex, Cursor e outros
Documentação
PredixLab's MCP server lets an AI agent query daily stock signals, market summaries, screeners and options analysis. MCP is a standard way for agents to use outside tools. The connection is read-only: it cannot place trades or change your account.
The endpoint is https://api.predixlab.com/mcp/, using Streamable HTTP MCP. Every request needs a bearer credential: either a dedicated PredixLab MCP API key (plmcp_) or an OAuth access token issued for MCP. Both use the read-only scope mcp:read.
The website dashboard JWT is not used for MCP. MCP uses a dedicated OAuth authorization server, separate from the website's authorization server. The browser flow shares your dashboard login, not your website tokens. Website login sessions and website access tokens are not accepted by MCP. OAuth clients obtain a separate MCP access token through the browser authorization flow; do not copy a dashboard token into an MCP client. MCP API keys cannot call the ordinary REST API.
Which agents can connect
Use Grok Bot, or any agent or client that can add a custom remote HTTP MCP server with a custom Bearer header.
API keys remain supported for Claude Desktop, Cursor and other compatible clients. Existing plmcp_ API keys still work.
ChatGPT custom MCP connectors and Codex can connect through OAuth, with sign-in and approval on dashboard.predixlab.com. Client features and setup screens depend on the client; follow the OpenAI documentation linked below for current details.
Set up with an API key
API keys remain the primary setup for Claude Desktop, Cursor and other clients that support custom authorization headers.
- Sign in to the PredixLab dashboard, open Profile, and find Agent connections.
- Choose Create key. In Create MCP API key, enter a Key name, choose Expires after, and select Create key.
- In Save your new key, copy the One-time API key into your client's secure secret storage. The secret is shown only once after creation or rotation; it cannot be retrieved later.
- Add a custom HTTP MCP server at
https://api.predixlab.com/mcp/. Set itsAuthorizationheader toBearerfollowed by a space and your full key. - Reconnect the client or start a new conversation. Ask it to call
list_signal_dates,list_option_activity_datesorlist_screener_presetsto discover available sessions or preset IDs.
This generic configuration uses mcpServers. Adapt the outer structure to your client's documented format and preserve unrelated entries. Replace YOUR_API_KEY with your key through the client's supported secure credential input; do not send the placeholder literally.
{
"mcpServers": {
"predixlab": {
"type": "http",
"url": "https://api.predixlab.com/mcp/",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
The dashboard also provides an Agent configuration example. Whatever format you use, confirm that the client sends the complete Bearer header with every request.
Connect ChatGPT custom MCP through OAuth
- In ChatGPT's custom MCP connector setup, add PredixLab with the server URL
https://api.predixlab.com/mcp/and choose OAuth authentication. - Follow the connection prompt to
dashboard.predixlab.com. Sign in with your usual dashboard login (Email, Google or Microsoft) if needed, then approve or deny the app's read-only access on the dashboard consent screen. - After approval, the browser returns to ChatGPT. Use the connector in a conversation and ask it to call
list_signal_datesorlist_screener_presetsto check the connection.
ChatGPT custom MCP connectors use CIMD automatically; you do not need to register a client or create an MCP API key for this OAuth connection. See OpenAI's guide to connecting custom MCP servers in ChatGPT for current client UI, availability and workspace requirements.
Connect Codex through OAuth
- Add a remote HTTP MCP server named
predixlabathttps://api.predixlab.com/mcp/in Codex. - Run
codex mcp login predixlab. The browser opensdashboard.predixlab.com. Sign in with your usual dashboard login (Email, Google or Microsoft) if needed, then approve or deny the app's read-only access on the dashboard consent screen. - After approval, the browser returns to Codex. Ask it to list PredixLab's available tools or call
list_signal_datesto check the connection.
For the CLI, the add-and-login sequence is:
codex mcp add predixlab --url https://api.predixlab.com/mcp/
codex mcp login predixlab
Codex uses CIMD automatically and manages the OAuth credentials; do not paste a website dashboard JWT into its MCP configuration. See OpenAI's Codex MCP documentation for current commands, configuration and client UI details.
OAuth discovery and scope
PredixLab supports OAuth 2.1 through its dedicated MCP authorization server. Clients use Protected Resource Metadata to discover the authorization server, then complete browser authorization. PKCE S256 is required, as is the resource parameter set to https://api.predixlab.com/mcp.
Browser sign-in and consent happen on dashboard.predixlab.com. If you are already signed in to the dashboard, login is skipped. The consent screen shows the app name and where the browser will return; for Codex and Claude Code, this is an app on this computer (127.0.0.1 or localhost). You can approve or deny the app's read-only access. After approval, the browser returns to the client.
Client registration uses Client ID Metadata Documents (CIMD) only. Dynamic Client Registration (DCR) is not supported; it is deprecated in the MCP 2026-07-28 specification.
| Setting | Value |
|---|---|
| MCP server URL | https://api.predixlab.com/mcp/ |
| OAuth issuer | https://api.predixlab.com/mcp-oauth |
| OAuth resource / audience | https://api.predixlab.com/mcp |
| Protected Resource Metadata | https://api.predixlab.com/.well-known/oauth-protected-resource/mcp |
| Authorization Server Metadata | https://api.predixlab.com/.well-known/oauth-authorization-server/mcp-oauth |
| Scope | mcp:read |
Keep the URL distinction: the MCP endpoint has a trailing slash; the OAuth resource identifier does not. OAuth gives the same read-only MCP access as an API key, not trading or account-management access.
Available tools
All 18 tools are read-only. Start with list_signal_dates, list_option_activity_dates or list_screener_presets rather than guessing dates or preset IDs. Optional date arguments use YYYY-MM-DD; omitting one selects the latest session visible to your account for that tool and symbol, where applicable.
| Tool | What it returns |
|---|---|
list_signal_dates | Published signal sessions visible to your account, newest first. |
get_signals | The combined Pivot and AlphaRank signal board for a session. |
get_pivot_signals | Pivot signals for a session, optionally filtered by direction and event. |
get_alpharank_signals | The AlphaRank top-15 rankings for a session. |
get_alpharank_history | Visible AlphaRank publications for one symbol, oldest first. |
get_market_snapshot | The complete latest daily market snapshot. |
get_market_overview | Daily market breadth, sentiment and leading movers in one overview. |
get_market_movers | Daily rankings for gainers, losers, activity, unusual volume, gaps or 52-week extremes. |
get_quotes | Latest-session quotes for up to 50 symbols. |
get_technical_analysis | A symbol's trend, momentum, key levels and technical interpretation. |
run_screener | Daily snapshot matches for custom filters, sorting and pagination supplied under request. |
list_screener_presets | Built-in screener preset IDs and their criteria. |
run_screener_preset | Matches for a built-in screener preset in a chosen index universe, without saving a strategy. |
list_option_activity_dates | Unusual-options activity sessions visible to your account. |
get_unusual_options | Unusual options activity grouped by symbol for a session, with up to 20 symbol groups. |
get_option_activity | Unusual options activity across visible sessions with symbol-level pagination. |
get_gamma_exposure | Gamma exposure analysis for a symbol and session. |
get_options_structure | The latest visible implied-volatility and positioning structure for a symbol. |
The client's tools/list response provides parameter and output schemas. Tools that need a symbol take the stock identifier you want to research; use SYMBOL as a placeholder when drafting a request.
Coverage and data dates
PredixLab tracks S&P 500 and Nasdaq-100 constituents. Some tools may cover a different set; check what each result includes. Daily end-of-day data is published once per trading day after the US close. Quotes and snapshots are daily observations, not live prices.
Market results are tied to a data date. Ask the agent to include that date in every answer based on those results, and check it before comparing figures. Different tools may return different sessions. Non-trading days do not produce a new session. See how PredixLab works for coverage, the update schedule and the methods behind the signals.
Free and Premium access
MCP uses the same account entitlements as the REST API. Neither an API key nor OAuth bypasses your plan.
- Free: the 10-day delay applies to signal sessions, Pivot signals, AlphaRank rankings and publication history, unusual options activity, gamma exposure, and options structure. Their date-discovery tools also respect this delay. Accessible sessions are dated on or before the date 10 calendar days ago, not 10 trading sessions ago. The corresponding REST API endpoints use the same delay.
- Other MCP market tools: market snapshots, overviews, movers, quotes, technical analysis and screening do not have this 10-day gate. They still use daily published data.
- Premium: access to the latest published data without the Free delay. This does not change model accuracy or remove data limitations.
See pricing for plan details and known limitations before interpreting results.
Keep your key safe
Treat the key like a password. Prefer client-managed secret storage. Never put it in URLs, shared files, source-controlled files or public chats. Do not include it in screenshots or logs.
If a key leaks, open Profile > Agent connections and choose Revoke key or Rotate key. Revocation stops access immediately. Rotation invalidates the old secret immediately and shows a new secret only once; replace the saved key in every client that used it, then reconnect.
Open-source scope
Only predixlab-signals is open source (Apache-2.0), covering signal research and backtests. The API, MCP server, dashboard and all other PredixLab repositories are private. Market data is not included. See Signal code to inspect and run the public code. The connection steps and tool reference above document the hosted MCP service.
Important information
For research and education only, not investment advice. Agents can make mistakes; check the data date and figures before relying on an answer.