Docs › Core Systems › MCP

MCP

TRUE's Model Context Protocol server. One endpoint, one auth flow, every tool TRUE uses internally.

What this is

Everything in TRUE that can be queried from the outside is exposed as a Model Context Protocol (MCP) server. One endpoint, one auth flow, every tool. The MCP surface is the same surface our internal agents use — there’s no second-class API on the outside.

Endpoint

POST https://app.truefinance.ai/api/v1/mcp

Connect from Claude Desktop, Cursor, Continue, or any MCP-compatible client. The server speaks standard MCP over HTTP and authenticates with the same bearer token used by the TRUE app.

Available tools

The MCP surface mirrors what TRUE itself uses internally — agents on our side and agents on your side hit the same tools.

Pricing

get_price

Latest price, 24h change, market data for one or many assets.

Search

search_assets

Resolve symbols across crypto, stocks, and tokenized equities.

Memecoins

getMemecoinOverview

Canonical overview of any Solana long-tail token.

Memecoins

getMemecoinSecurity

Mint authority, freeze authority, holder concentration.

Memecoins

getMemecoinHolders

Top holders ranked, with concentration warnings.

Memecoins

getMemecoinTrades

Most recent on-chain trades for a token.

Charts

getMemecoinChart

OHLCV candles at the requested timeframe.

News

get_news

Latest headlines with sentiment analysis.

User

get_watchlist

The current TRUE user’s saved assets.

User

get_points_balance

Points, streak, referral stats for the authenticated user.

Example call

{
  "method": "tools/call",
  "params": {
    "name": "get_price",
    "arguments": { "assets": ["BTC", "SOL", "NVDA"] }
  }
}

Connecting from Claude Desktop

// ~/.config/Claude/mcp.json
{
  "mcpServers": {
    "true": {
      "url": "https://app.truefinance.ai/api/v1/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer tp_live_..." }
    }
  }
}

Restart Claude Desktop. The TRUE tools appear under the MCP tools menu and are callable from any conversation.

Connecting from Cursor / Continue

Both editors accept the same mcp.json shape. Drop the snippet above into the editor’s MCP config, restart, and the tools become available to the in-editor assistant. For Continue, add the entry under experimental.modelContextProtocolServers in ~/.continue/config.json.

OAuth for multi-user MCP

When you’re embedding TRUE inside a multi-user product (a research workspace, a trading desk), use the OAuth flow rather than a static bearer. The OAuth grant binds an MCP session to a specific TRUE user wallet and inherits that user’s scope, watchlist, and points balance. Authorization endpoints, redirect flow, and PKCE requirements are on Authentication.

Scoped API keys

Static keys come in two flavors:

  • tp_live_… — production-tier keys with the scopes you grant at issuance time. Use the smallest scope set that still works.
  • tp_test_… — sandbox keys against a non-production fixture. No real funds, no real points.

Rotation cadence is described on Authentication. Compromised keys can be revoked instantly from the dashboard; revocation propagates within seconds across the MCP edge.

Rate limits

100 requests / minute per token on the public tier. Higher quotas available for partners — contact [email protected]. Per-tool rate limits and the full table are on Rate Limits.

Safety

Never expose user bearer tokens in client-side code. All MCP calls go over TLS, but TLS does not protect a token from being lifted out of a JS bundle. Proxy through your backend; mint short-lived tokens; revoke on incident. Apply the principle of least privilege when scoping keys — a tool a key cannot call cannot be abused with that key.

For Partners

White-label MCP setup is available on the partner tier. You provision keys for end users from your dashboard, brand the OAuth screen with your logo and copy, and inherit the same tool surface. Revenue share, SLA, and onboarding flow on Partner Integration.

Safety, limits, failure modes

  • Token leak. Treat keys like passwords. Revoke on suspicion; rotate on schedule.
  • Per-tool rate limits. A single tool can be limited tighter than the bucket suggests — see Rate Limits.
  • Tool unavailability. When an upstream (TRUE Quotes, Solana RPC) is unhealthy, the relevant tool returns a structured error rather than a hallucinated payload.
  • Versioning. Tool schemas are versioned; breaking changes ship as new tool names rather than mutating an existing one.

See also

Last updated: