MCP

Server details

The OAuth authorization server (issuer) is https://www.chickstockfi.com/openapi/pro/v1. Use the www.chickstockfi.com host for MCP connections.

Connect with a Data API key

Data API customers connect with their Data API key (ck_live_…) in the Authorization header. No PRO API plan is needed. The server URL is the same; the key decides which tools you get.

• Each tool maps to one Data API endpoint. One tool call is one Data API request, counted toward the same daily quota and per-minute limit as REST.
• tools/list shows only the tools your key can use. Tools for markets outside your contract are left out (a KR-only account has no get_earnings_calendar). Legacy Free keys get get_news, search_news, grounded_answer and get_api_usage only.
• A result is the REST response body plus usage: quota (daily), rate_limit (per minute) and, for accounts with an AI call limit (PoC, Launch, Business, Scale), ai_quota.
• Error codes and messages are the same as REST, for example MARKET_NOT_ENTITLED, PLAN_REQUIRED, POC_ENDED, QUOTA_EXCEEDED, RATE_LIMITED and AI_QUOTA_EXCEEDED. When a PoC ends, the connection itself returns 403 POC_ENDED.
• OAuth sign-in is for PRO accounts; connect a Data API key with the header. API docs session keys (ck_docs_…) cannot connect (401 WRONG_KEY_SCOPE), and PRO tools such as ask_phoenix return WRONG_KEY_SCOPE.

Claude Code

claude mcp add --transport http phoenix-data https://www.chickstockfi.com/openapi/pro/v1/mcp \
  --header "Authorization: Bearer $PHOENIX_DATA_KEY"

Claude Desktop

{
  "mcpServers": {
    "phoenix-data": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.chickstockfi.com/openapi/pro/v1/mcp", "--header", "Authorization:${PHOENIX_AUTH}"],
      "env": { "PHOENIX_AUTH": "Bearer ck_live_xxxxxxxx" }
    }
  }
}

Cursor

{
  "mcpServers": {
    "phoenix-data": {
      "url": "https://www.chickstockfi.com/openapi/pro/v1/mcp",
      "headers": { "Authorization": "Bearer ck_live_xxxxxxxx" }
    }
  }
}

AI calls

grounded_answer uses one AI call each time the answer model is called. get_disclosure_summary and get_stock_briefing use one only when a new summary or briefing is generated. run_data_query runs without a model and does not count. The limit is your tier's daily AI call limit, shared with REST (Rate limits).

Data API tools

Endpoint paths are under https://api.chickstockfi.com/openapi/v1.

Connecting each client

Claude Code

# Connect with a PRO API key
claude mcp add --transport http phoenix https://www.chickstockfi.com/openapi/pro/v1/mcp \
  --header "Authorization: Bearer $PHOENIX_PRO_KEY"

# Connect with OAuth: add it without a header, then in Claude Code run /mcp → phoenix → Authenticate
claude mcp add --transport http phoenix https://www.chickstockfi.com/openapi/pro/v1/mcp

Claude Desktop

To connect without a key, go to Settings → Connectors → Add custom connector, enter the server URL and connect. Log in and approve in the browser, and you are done. To connect with a key, use mcp-remote in claude_desktop_config.json.

{
  "mcpServers": {
    "phoenix": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.chickstockfi.com/openapi/pro/v1/mcp", "--header", "Authorization:${PHOENIX_AUTH}"],
      "env": { "PHOENIX_AUTH": "Bearer ck_pers_xxxxxxxx" }
    }
  }
}

claude.ai web and apps

Settings → Connectors → Add custom connector → enter the server URL → Connect → log in → approve. OAuth only.

ChatGPT

In developer mode, create an app or connector, enter the same address as the MCP server URL, and choose OAuth for authentication.

Cursor

{
  "mcpServers": {
    "phoenix": {
      "url": "https://www.chickstockfi.com/openapi/pro/v1/mcp",
      "headers": { "Authorization": "Bearer ck_pers_xxxxxxxx" }
    }
  }
}

Other MCP clients

Any client that supports Streamable HTTP needs only the server URL and an Authorization header. You can also check the connection with curl.

curl -s https://www.chickstockfi.com/openapi/pro/v1/mcp \
  -H "Authorization: Bearer $PHOENIX_PRO_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

OAuth flow

1. When a client calls the server without a key, it gets 401 and the protected resource metadata URL.
2. The client finds the authorization server in the metadata and performs dynamic client registration (/oauth/register).
3. The browser goes to /oauth/authorize, then login, then the consent screen. The consent screen shows the app name, the redirect URL, the account and the features its plan allows.
4. After approval, the client exchanges the code for tokens (PKCE S256 required). The access token (ck_mcp_at_…) lasts 1 hour; the refresh token lasts 30 days and is replaced each time it is used.
5. Approval requires a valid PRO plan. Even after tokens are issued, the plan is checked again on every request.

HTTP/2 401
WWW-Authenticate: Bearer resource_metadata="https://www.chickstockfi.com/openapi/pro/v1/.well-known/oauth-protected-resource/mcp", scope="mcp"

All paths are under https://www.chickstockfi.com/openapi/pro/v1. Each account can have 20 live connections; beyond that, the oldest connections are dropped first.

PRO tools (PRO API key · OAuth)

PRO limits

• One tool call counts as one daily call, combined with REST calls. get_ask_result and get_account_usage do not count.
• Connections made with a key share the same per-second bucket as REST. Each OAuth connection has its own bucket.
• The connection handshake (initialize · tools/list) does not count toward daily calls.
• When you hit a limit, the tool result comes back as an error (isError) containing a code such as RATE_LIMITED or DAILY_QUOTA_EXCEEDED. See Errors for what each code means.