Nubra MCP server for Codex and other MCP clients
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"nubra-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Nubra MCP Server A Python MCP server for Nubra built on `FastMCP`. This repo is designed to let MCP clients such as Codex connect to Nubra for: - authentication - instrument lookup and ref-id resolution - quotes and historical data - option-chain and derivatives analysis - holdings, funds, positions, and portfolio reporting - TA/indicator scans via `nubra-talib` - backtesting via `vectorbt` - local report and CSV export workflows - UAT-only trading actions with strict environment guardrails ## What This MCP Supports ### Read-only workflows - auth state and session checks - cash, futures, and options instrument discovery - quotes, current price, and previous-close change - historical OHLCV fetch and CSV export - options analytics and chain summaries - portfolio summary, holdings, positions, and funds - HTML and image-based portfolio reports - watchlist scanning and strategy helper tools - trade journal summaries - backtest reports and equity curve exports ### Trading workflows Trading is intentionally limited: - order placement is allowed only in `UAT` - order modification is allowed only in `UAT` - order cancellation is allowed only in `UAT` - square-off is allowed only in `UAT` - options strategy execution is allowed only in `UAT` - all trading actions are blocked in `PROD` The guardrail exists in both the MCP tool layer and the service layer. ## Safety Model This repo is meant to be public-safe if used correctly. What should be committed: - source code - `.env.example` - `.mcp.json` - docs - tests What should never be committed: - `.env` - `auth_state.json` - personal phone numbers - MPIN values - OTPs - generated reports and exports Each user of this MCP should create their own local `.env` and log in with their own Nubra account. ## Project Structure - [server.py](C:\Users\suboth sundar\Desktop\Nubra_API_Full_context\nubra-mcp-server\server.py): MCP entrypoint and tool reg…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.