PREVIEW · Proposed endpoints and dated plan snapshot · Not ready for public launch
navquote.
Menu
Financial data MCP

Give your AI tools
data to work with.

Connect compatible clients to quotes and historical data. Ask for a timestamped result, not a guess about the market.

Preview: the neutral MCP endpoint, tool names and client compatibility are awaiting end-to-end validation. The configuration below is proposed, not an active connection.
01 / A data-connected workflow

Connect. Authorize.
Ask a specific question.

  1. 01
    Add a remote HTTP MCP server

    Use a compatible client’s remote-server settings.

  2. 02
    Authorize in the shared console

    The planned OAuth flow keeps the existing account and subscription.

  3. 03
    Call a data tool and inspect its result

    Check the returned symbol, timestamp and availability.

PROPOSED HTTP CLIENT CONFIGURATION
{
  "mcpServers": {
    "navquote": {
      "type": "http",
      "url": "https://mcp.navquote.com/mcp"
    }
  }
}
Configuration syntax varies by client; this shape requires an OAuth-capable HTTP client.
02 / Make the task concrete

Ask for the context
alongside the number.

The first useful result is a successful data-tool call. A connected server or a list of tools is only an intermediate step.

EXAMPLE TASK
Get the latest available quote for AAPL.
Report the symbol, price and data timestamp.
If data is unavailable or delayed, say so.
This is a suggested prompt, not a recorded successful tool result.
03 / Intended data tools

Start with quotes and candles.

Neutral names below are planned aliases. Their compatibility and billing mapping must be verified.

Proposed toolTask
get_quoteGet a single market quote.
get_quote_batchRequest quotes for multiple symbols.
get_ohlcvRetrieve standard candles for an instrument.
get_ohlcv_batchRequest historical candle data for multiple instruments.
Review MCP plan access Understand candle data
A manual credential path

Mint an MCP token
on your server.

For a client that supports manual bearer authentication, call POST /api/mcp/generate with the account API key. Inspect success, token, expiresAt, mcpUrl and the returned client configuration.

The returned token goes in the MCP client’s Authorization header. Never substitute the account API key or a WebSocket token. Token lifetime follows the plan; do not hard-code the sample duration.

POST /api/mcp/generate
curl --fail-with-body "$NAVQUOTE_API_BASE/api/mcp/generate" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  --data '{}'
Uses the quickstart server environment. Neutral MCP authorization and client compatibility still require validation.
From a connection to an answer

Inspect the tool call, not just the text.

MCP session traffic is different from a market quote stream.

  1. Discover

    Read the client’s actual tool list.

    Implementation notes

    The aliases above are planned neutral names. Tool discovery must confirm which names the client actually exposes.

  2. Validate

    Check protocol errors and the data result’s success.

    Implementation notes

    The documented service uses JSON-RPC 2.0 over Streamable HTTP. Match response IDs and inspect the returned data result.

  3. Keep the evidence

    Return the symbol, currency and market time.

    Implementation notes

    Retain missing fields explicitly. A fluent explanation does not replace a successful data response.

The MCP session’s SSE channel is not /sse/stream market streaming. For continuously updating interfaces, use the streaming API.

04 / Before connecting

Know the boundaries.

Which clients have been tested with the new endpoint?

None have completed the neutral-endpoint acceptance test yet. Client support will be listed by name and version after authorization and actual data-tool calls succeed.

Is my REST API key also an MCP access token?

Follow the supported OAuth flow or generate an MCP JWT. Do not assume a long-lived REST API key can be sent as a bearer token to the hosted MCP endpoint.

Does generating a token mean the data connection works?

No. A token is a credential. Verify discovery, authorization, the tool list and a successful data-tool result before relying on the integration.

Financial context in your application

Give financial questions a data trail.

Explore assets & markets
Equity research

Identify the company

Ask your agent to resolve the listing before requesting price or company context. Check available tools and preserve reported periods.

Data & availability
Fund research

Separate price from holdings

Treat an ETF quote and its portfolio as different datasets. Confirm the client exposes the required tools before requesting holdings or NAV.

Data & availability
Market comparisons

Compare like with like

Preserve currency, timestamp and instrument type in the answer. Tool availability and account access must be checked for each workflow.

Data & availability
Build something your users can use

See where this API fits.

Choose the experience you want to deliver. Follow a concrete path from the first response to the access your application needs.

From the developer guides

Make the next step concrete.

Browse all guides

Start with a useful data task.

One account for API keys, usage and subscriptions.

Get API Key

Continue to our shared account console.