NORTHSTAR

NORTHSTAR MCP / HOSTED INTERFACE PREVIEW

Bring market context to the AI client you already use.

Discover a focused catalog for market data, options, portfolio state, reviewed actions, and profile context through one remote MCP shape.

Interface preview

No live service is available. The reserved .example endpoint cannot authorize an account or place a trade.

Review client setup
REMOTE / OAUTH
RESERVED ENDPOINT https://mcp.northstar.example
FASTEST START / CODEX CLI codex mcp add northstar --url https://mcp.northstar.example
17 TOOLS5 DOMAINSPAPER FIRST

/ CAPABILITIES

Seventeen tools.
Five clear domains.

The catalog keeps read context separate from reviewed actions, so a client can expose only the scope a workflow needs.

01 / 04

Market data

  • search_ticker
  • get_latest_tick
  • get_quote
  • get_chart
02 / 04

Options

  • get_option_expiry_dates
  • get_option_chain
  • get_option_quote
  • get_better_buys
03 / 06

Account and portfolio

  • get_positions
  • get_assets
  • get_orders
  • get_order
  • get_watchlist
  • get_tradable_quantity
04 / 02

Trading

  • create_order
  • cancel_order
05 / 01

User

  • get_profile

Catalog names describe the intended interface only. Availability and scopes require a separately implemented service.

/ CLIENT SETUP

Choose the surface.
Keep one connection model.

Two CLI examples are verified locally. The remaining cards describe a neutral remote-HTTP setup path until a production service and client-specific UI are confirmed.

01 / CLI

Claude Code

Add a remote HTTP MCP server from the command line.

claude mcp add --transport http northstar https://mcp.northstar.example
Verified command shape / reserved endpoint
02 / CLI

Codex CLI

Register the server URL, then authenticate when a live service exists.

codex mcp add northstar --url https://mcp.northstar.example
Verified command shape / reserved endpoint
03 / DESKTOP

ChatGPT / Codex Desktop

Open the client's integrations surface, choose a remote HTTP MCP connection, enter the endpoint, and complete OAuth only after a real service is supplied.

04 / EDITOR

Cursor

Add a remote MCP server from client settings, use the reserved endpoint for layout review, and wait for a real authorization service before connecting.

05 / ASSISTANT

Grok

Use the client's supported remote MCP connection flow when available; do not treat this preview as a compatibility promise.

06 / OPEN

Other OAuth-capable clients

Provide the remote HTTP endpoint and follow the client's browser handoff. Confirm protocol and scope support before use.

/ OAUTH FLOW

Authorization that
keeps a person in view.

This is the intended protocol sequence for a future hosted service, not a working NORTHSTAR sign-in flow.

  1. 01

    Configure client

    Add the remote endpoint to an OAuth-capable MCP client.

  2. 02

    Browser handoff

    The client opens a browser authorization request owned by the future service.

  3. 03

    Sign in and consent

    Review the requested scopes and explicitly approve only what the workflow needs.

  4. 04

    Session established

    The client receives a scoped session without placing credentials in prompts.

  5. 05

    Credential refresh

    The client refreshes or reauthorizes according to the service policy and expiry.

/ PAPER FIRST

Start with context.
Earn every action.

Treat every external client, authorization request, and action tool as a deliberate boundary.

01

Read before write

Begin with quotes, charts, positions, and watchlists in a paper environment.

02

Confirm every trade

Require explicit human confirmation, clear sizing, and a reviewable summary before any order action.

03

Protect credentials

Keep tokens out of prompts, notes, screenshots, logs, and shared configuration.

04

Review authorization

Grant minimum scopes, inspect expiry, and revoke access when a client is no longer needed.

/ FAQ

Connection questions,
answered plainly.

Why did sign-in fail?

This preview has no authorization server. With a future service, also check the endpoint, browser session, approved account, and requested scopes.

What happens when authorization expires?

An OAuth-capable client should refresh the credential when permitted or ask you to authorize again. Exact behavior depends on the implemented service and client.

Why is a tool unavailable?

A tool can depend on the service version, account mode, granted scope, data coverage, and the client's protocol support.

Is the NORTHSTAR endpoint available now?

No. The `.example` address is reserved and non-operational. It exists only to make this interface preview concrete and safe to share.

Which clients are compatible?

The two CLI command shapes above are verified. Other cards describe the intended setup category, not a confirmed compatibility guarantee.

/ READY TO REVIEW

Map the connection
before you build it.

Use the catalog and safety model to align scopes, clients, and human confirmation points.

https://mcp.northstar.exampleReview client setup