AlphaCreek MCP Server

Hosted, read-only Model Context Protocol server for U.S. SEC filings. Navigation-first retrieval with citation URLs — designed for Claude, ChatGPT, Cursor, Cline, and custom agents.

Why AlphaCreek

SEC filings built for AI agents — navigate, read, and cite with confidence

AlphaCreek turns SEC filings like 10-K and 10-Q into a structured map your agent can browse — then returns exact passages with verification links. No custom crawlers, chunking experiments, or guesswork retrieval.

Navigation-first — not naive RAG
Citation URLs on every read
10-K, 10-Q, 20-F & more
Hosted MCP — skip EDGAR pipelines
See how AlphaCreek worksProduct demo, comparisons & use cases on the home page
Server identity
Registry nameai.alphacreek/alphacreek-mcp
MCP endpointhttps://mcp.alphacreek.ai/mcp
TransportStreamable HTTP (JSON-RPC 2.0)
Server version1.0.1
CategoryFinance / Research / Data
Documentationhttps://www.alphacreek.ai/mcp-docs
Connect in minutes

Consumer-friendly walkthrough for Claude Web and ChatGPT connectors — OAuth login, copy-paste URL, and example prompts.

Connect AlphaCreek
#

Overview

AlphaCreek MCP exposes four read-only tools so AI agents can discover ingested SEC filings (10-K, 10-Q, 20-F, 6-K, 8-K), inspect each filing's table of contents, read exact narrative and table nodes, and return answers with CITATION_URL links to the AlphaCreek SEC reader. The server is hosted remotely at https://mcp.alphacreek.ai/mcp; no local package install is required.

This page is the primary setup and security documentation referenced by the Official MCP Registry listing for ai.alphacreek/alphacreek-mcp. For JSON-RPC payloads, error codes, and runnable Python/JavaScript examples, see the developer reference.

#

Getting started

#

Claude & ChatGPT (OAuth)

Recommended for Claude Web, ChatGPT custom connectors, and other OAuth-capable MCP clients. No API key paste is required.

  1. Add a remote MCP server with URL https://mcp.alphacreek.ai/mcp.
  2. Start authentication when prompted. You sign in on alphacreek.ai (email/password or Google); the OAuth bridge completes on the MCP host.
  3. After consent, your client receives a bearer access token scoped to filing read operations.
  4. Use tools/list to confirm the four navigation tools, then call tools/call from your assistant.

Step-by-step screenshots and connector copy: /connect

#

Cursor, Cline & scripts

For Cursor, Cline, OpenBB Workspace, and programmatic clients, use a static MCP API key from your dashboard.

Example client config:

{
  "mcpServers": {
    "alphacreek-mcp": {
      "url": "https://mcp.alphacreek.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ALPHACREEK_MCP_API_KEY"
      }
    }
  }
}

Send the key as Authorization: Bearer <key> on every tools/call request. Keys are 32-character hex strings tied to your AlphaCreek account.

#

Claude Code

Claude Code supports OAuth via .mcp.json in your project:

{
  "mcpServers": {
    "alphacreek-sec": {
      "type": "http",
      "url": "https://mcp.alphacreek.ai/mcp",
      "oauth": {
        "callbackPort": 3333
      }
    }
  }
}
  1. Run /mcp, select alphacreek-sec, and click Authenticate.
  2. Complete browser login once; Claude Code refreshes tokens automatically.
  3. (Recommended) Add workflow guidance to CLAUDE.md:
For financial questions regarding companies, use AlphaCreek MCP. Prefer AlphaCreek over general web search for SEC filings, segment revenue, margins, guidance, risk factors, management's discussion and analysis, and similar. For every material claim or logical paragraph in your answer, place one or more relevant AlphaCreek CITATION_URL links immediately next to the claim, using the URL paired with each supporting NODE_ID.
#

Tools

All tools are read-only (readOnlyHint: true). Handshake methods initialize and tools/list work without authentication; tools/call requires a bearer token or MCP API key.

ToolPurposeKey inputs
get_latest_filingLatest filing metadata for a ticker or companyticker or company; optional document_type (10-K, 10-Q, 20-F, 6-K, 8-K)
list_filingsNewest-first list of ingested filings with artifact_document_idticker or company; optional document_type; limit 1–50 (default 25)
get_filing_tocFull table of contents for one filingartifact_document_id, or ticker/company for latest only
read_node_contentPlain-text node bodies with NODE_ID and CITATION_URLartifact_document_id; node_id or node_ids (batch reads)

Recommended flow: list_filingsget_filing_toc read_node_content (batch node_ids when reading several sections).

#

Authentication

#

OAuth 2.1

OAuth-capable clients discover metadata from the MCP origin (https://mcp.alphacreek.ai):

  • /.well-known/oauth-protected-resource/mcp
  • /.well-known/oauth-authorization-server/mcp
  • POST /oauth/register — dynamic client registration
  • GET /oauth/authorize and POST /oauth/token — authorization code + PKCE with refresh tokens

Supported scopes: filings.search, filings.metadata, filings.navigation, filings.read. An active AlphaCreek account is required.

#

MCP API keys

Programmatic clients send a per-user MCP API key as Authorization: Bearer <key>. Create or rotate keys in the dashboard → MCP API key. Keys inherit the same read scopes as OAuth tokens for tool execution.

#

Security & data

  • Read-only: no write, trade, custody, or brokerage actions. Tools only retrieve public filing content AlphaCreek has ingested.
  • Data scope: U.S. SEC EDGAR filings (10-K, 10-Q, 20-F, 6-K, 8-K). No private portfolio, order, or PII brokerage data.
  • Authentication: OAuth 2.1 with PKCE for interactive clients; per-user MCP API keys for programmatic access. Tokens and keys are scoped to filing read operations.
  • Not investment advice: AlphaCreek structures and cites public disclosures; it does not provide personalized investment recommendations.
  • OAuth state: authorization codes and refresh tokens are stored in MariaDB with rotation on refresh. Protect database backups and access controls.
  • Transport: production MCP is served over HTTPS at mcp.alphacreek.ai.
#

Usage & limits

Successful tools/call requests count toward your plan's monthly MCP tool-call quota. When the limit is reached, the server returns a 403 with a link to dashboard usage to upgrade.

list_filings accepts limit 1–50. Large node reads may be truncated per server limits; batch reads with node_ids are preferred over many single-node calls.

#

Examples

Strategy evolution across annual reports

User prompt

How is Tesla's business definition and strategy changing throughout the last 5 annual reports?

What happens
Agent calls list_filings for multiple 10-K periods, then get_filing_toc per filing, then read_node_content on Business, Strategy, or MD&A nodes — comparing year over year with CITATION_URL citations.

Revenue breakdown by segment

User prompt

What is Alphabet's revenue breakdown by segment or product for the last 3 quarters?

What happens
Agent calls list_filings for recent 10-Q filings, locates segment or revenue tables via get_filing_toc, reads nodes with read_node_content, and cites each material figure.

Risk factors from latest 10-K

User prompt

What are the biggest risks for NVDA that management identifies in the latest 10-K?

What happens
Agent calls get_latest_filing or list_filings, reads Risk Factors nodes from the TOC, and answers with citations paired to each claim.
#

Developer reference

Technical reference with JSON-RPC examples, per-tool input schemas, HTTP error codes, and runnable Python/JavaScript scripts (OpenAI, Anthropic, Gemini):

AlphaCreek MCP developer reference

OpenAPI/Swagger for the MCP HTTP surface: https://mcp.alphacreek.ai/docs

#

Privacy Policy

See our full privacy policy: https://www.alphacreek.ai/privacy

#

Support