# MCP server for SEC filings

SEC Blast runs a remote MCP server at `https://api.secblast.com/mcp`. Claude, ChatGPT, Cursor and any other MCP client connect to it over HTTP and use the API through its tools.

## Adding the server

The MCP server is hosted at `https://api.secblast.com/mcp`. To add to Claude Code:

```bash
claude mcp add --transport http secblast https://api.secblast.com/mcp
```

For other clients, use the same address as a remote MCP server (streamable HTTP).

## 

## Connecting

The client connects with OAuth 2.1. The first time, the client opens SEC Blast in the browser:

1. You sign in to SEC Blast, or create an account.
2. The consent page shows the app's name, the address it returns to, and the organization it connects to. With several organizations, you choose one.
3. **Allow** returns you to the app. From then on the app calls the API for that organization; **Deny** returns you with nothing granted.

Owners, admins and developers of an organization can connect an app to it, the same roles that manage SEC Blast API keys.

## What a connected AI can do

A connected AI has read access to the API. Every call it makes counts against the organization's plan, like a request made with a key.

The app holds an access token valid for 10 minutes and a refresh token valid for 60 days. Each refresh replaces the refresh token and double usage of a refresh token invalidates the session.

## Connected apps

[Connected apps](https://www.secblast.com/dashboard/apps) lists the apps connected to the organization: name, the address each returns to, who allowed it, when, and when it was last used. **Revoke** ends a connection: its refresh token stops at once, its access token within a minute. A revoked app can be allowed again after ten minutes.

## Tools

The server offers these tools. Each one calls the API with the app's token.

| Tool | What it does |
|---|---|
| `sec_find_company` | Find a company or fund by ticker, name or CIK; returns its CIK, current and former names, tickers, SIC industry, addresses and SPAC status. |
| `sec_latest_filing` | The latest filing of one form for a ticker or CIK in one call (for example the latest S-4 of NTWO), with the start of the document. |
| `sec_list_filings` | List filings by company, form, 8-K item, status and date, newest first. |
| `sec_get_filing` | One filing by accession number: dates, filers, status, amendments, documents and exhibits, sections or 8-K items. |
| `sec_search_filings` | Full-text search of every filing since 1993, with ticker, form, document type, SIC, state and date filters. |
| `sec_read_filing` | Read any document or exhibit, a named section (10-K, 10-Q and 20-F items; the summary, background of the merger, pro forma and target MD&A of S-4, F-4 and merger proxies; executive compensation in DEF 14A), or an 8-K item, page by page. |
| `sec_list_sections` | One section across many filings: 10-K, 10-Q and 20-F sections, and merger and proxy sections such as Background of the Merger or Pay Versus Performance, by company or date. |
| `sec_list_8k_events` | 8-K events across companies by item, with extracted fields: 1.01 merger and other material agreements and 2.01 completed acquisitions (deal price per share, cash per share, exchange ratio, closing date), 2.02 earnings and 4.01 auditor changes, with the accuracy of each field. |
| `sec_list_spacs` | Former SPACs by the date their business combination closed, or current blank-check SPACs, with the merger filing and the SPAC's original name. |
| `sec_get_financials` | XBRL financial statements, any concept over time, one concept across companies, standard fields and segments. |
| `sec_get_holdings` | Insider trades (Forms 3, 4 and 5), 13F holdings by security or manager, Form 144, N-PORT fund holdings and Form D. |
| `sec_get_tables` | The tables of a 10-K, 10-Q or 20-F primary document, with parsed numbers and scale. |
| `sec_get_filing_data` | The parsed content of one filing: Form D, N-PORT, 13F, Forms 3, 4 and 5, or Form 144. |
| `sec_watch_filings` | Create, list or delete a subscription to new filings (by company, form type or 8-K item) that sends them as signed webhooks to one of your endpoints. |
| `sec_send_feedback` | Send feedback to SEC Blast about the MCP server or the data: a bug, wrong or missing data, a missing tool or unclear docs. |

## For client developers

- Authorization code with PKCE, `S256` only. No implicit or password grant.
- Clients register dynamically (RFC 7591) or are named by a client ID metadata document: a `client_id` that is an `https` URL. Redirect URIs are `https`, or `http` on `127.0.0.1`, `[::1]` or `localhost` with any port.
- The `resource` parameter (RFC 8707) is `https://api.secblast.com/mcp` for the MCP server or `https://api.secblast.com/v3` for the API, and the access token is valid for that one only. Without it, the token is for the API.
- Access tokens are ES256 JWTs. The one scope is `api`.
- `POST /oauth/revoke` (RFC 7009) with either token ends the connection.
