# AlphaCreek SEC Filings MCP (remote · mcp.alphacreek.ai)

Access SEC filings efficiently (10-K, 10-Q, etc), save time and tokens, and get cited answers.

- Trust score: 65/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.alphacreek.ai`: 65/100 (this document), [markdown](https://verifymcp.io/servers/ai-alphacreek-alphacreek-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-alphacreek-alphacreek-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.alphacreek.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1194 tokens (~298/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-alphacreek-alphacreek-mcp https://mcp.alphacreek.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-alphacreek-alphacreek-mcp]
url = "https://mcp.alphacreek.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-alphacreek-alphacreek-mcp": {
      "type": "remote",
      "url": "https://mcp.alphacreek.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-alphacreek-alphacreek-mcp --url https://mcp.alphacreek.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-alphacreek-alphacreek-mcp:
    url: "https://mcp.alphacreek.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-alphacreek-alphacreek-mcp": {
      "type": "http",
      "url": "https://mcp.alphacreek.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, 0)

- [security regression] HTTPS: fail → unverified

### 2026-07-29 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (4)

### `get_latest_filing` (~106 tokens)

Return latest filing metadata for a company or ticker.

Input parameters:

- `company` (string)
- `document_type`: Optional filing type filter. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: Annual Report.
- `filing_registry` (string): Filing source registry. Use sec_edgar (default) for US SEC filings or fca_nsm for UK FCA NSM annual reports.
- `ticker` (string)

### `list_filings` (~144 tokens)

List available filings for a ticker (newest first) with artifact_document_id and dates. Use filing_registry=fca_nsm for UK FCA annual reports. Use this first when you need a specific reporting period.

Input parameters:

- `company` (string)
- `document_type`: Optional filing type filter. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: Annual Report.
- `filing_registry` (string): Filing source registry. Use sec_edgar (default) for US SEC filings or fca_nsm for UK FCA NSM annual reports.
- `limit` (integer)
- `ticker` (string)

### `get_filing_toc` (~188 tokens)

Return the full filing table of contents for one filing. If artifact_document_id is omitted, resolves the single latest filing for ticker/company (and optional document_type) only. Use list_filings first to discover a specific reporting period. For FCA filings, pass filing_registry=fca_nsm; TOC node ids are HTML page element ids (e.g. pf2a, page12, pageView1).

Input parameters:

- `artifact_document_id` (string)
- `company` (string)
- `document_type`: Optional filing type filter. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: Annual Report.
- `filing_registry` (string): Filing source registry. Use sec_edgar (default) for US SEC filings or fca_nsm for UK FCA NSM annual reports.
- `ticker` (string)

### `read_node_content` (~241 tokens)

Return content for one or more navigation nodes in a filing. Pass one node via node_id or several via node_ids, using the node ids from TOC lines. These are the same values shown as NODE_ID lines in read_node_content output. The authoritative node content is returned as plain MCP text only: an ARTIFACT_DOCUMENT_ID header, then per-node blocks with NODE_ID, TITLE, CITATION_URL, CONTENT_START … CONTENT_END. A TOC node may expand into more granular child NODE_ID blocks; cite those granular NODE_ID/CITATION_URL pairs when they support the claim. For every material claim or logical paragraph in your answer, place one or more relevant CITATION_URL links immediately next to the claim, using the URL paired with each supporting NODE_ID.

Input parameters:

- `artifact_document_id` (string, required)
- `node_id` (string): Single node id from TOC / NODE_ID lines. For FCA filings this is the HTML page id (e.g. pf2a, page12, pageView1).
- `node_ids` (array): Batch read: multiple node ids for one filing (same identifiers as NODE_ID / TOC).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-alphacreek-alphacreek-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 63
- 2026-07-30: 60
- 2026-07-29: 60
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 58

## Links

- Remote endpoint: https://mcp.alphacreek.ai/mcp
- Authorisation metadata: https://mcp.alphacreek.ai/.well-known/oauth-protected-resource/mcp
- Website: https://www.alphacreek.ai/mcp-docs
- Changelog RSS feed: https://verifymcp.io/servers/ai-alphacreek-alphacreek-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-alphacreek-alphacreek-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-alphacreek-alphacreek-mcp/mcp