AlphaCreek SEC Filings MCP
REMOTE · MCP.ALPHACREEK.AI · SCANNED SEP 25
Access SEC filings efficiently (10-K, 10-Q, etc), save time and tokens, and get cited answers.
Available components
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. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 521, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3017 tokens (~603/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the AlphaCreek SEC Filings MCP server?
AlphaCreek SEC Filings MCP is a hosted endpoint at https://mcp.alphacreek.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.alphacreek.ai
claude mcp add --transport http ai-alphacreek-alphacreek-mcp 'https://mcp.alphacreek.ai/mcp'
{
"mcpServers": {
"ai-alphacreek-alphacreek-mcp": {
"url": "https://mcp.alphacreek.ai/mcp"
}
}
} {
"servers": {
"ai-alphacreek-alphacreek-mcp": {
"type": "http",
"url": "https://mcp.alphacreek.ai/mcp"
}
}
} [mcp_servers.ai-alphacreek-alphacreek-mcp] url = "https://mcp.alphacreek.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-alphacreek-alphacreek-mcp": {
"type": "remote",
"url": "https://mcp.alphacreek.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-alphacreek-alphacreek-mcp --url 'https://mcp.alphacreek.ai/mcp' --transport streamable-http
mcp_servers:
ai-alphacreek-alphacreek-mcp:
url: "https://mcp.alphacreek.ai/mcp" {
"McpServers": {
"ai-alphacreek-alphacreek-mcp": {
"Transport": "http",
"Url": "https://mcp.alphacreek.ai/mcp"
}
}
} assistant mcp add ai-alphacreek-alphacreek-mcp -t streamable-http -u 'https://mcp.alphacreek.ai/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Sept 26 −2
- Stability: pass → fail ▼ security
- 3 Sept 26 0
- A breaking change shipped without a version bump: still 1.1.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_sec_event_filings” rewrote its description, which is the text the model reads security
- “search_sec_event_filings” made “concept_groups” required, so existing callers break ▼ functional
- “search_sec_event_filings” reworded the description of “concept_groups” cosmetic
- “search_sec_event_filings” reworded the description of “query” cosmetic
- “search_sec_event_filings” made “query” optional cosmetic
- 30 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_sec_event_filings” rewrote its description, which is the text the model reads security
- Schema quality: 405 → 596 ▼ functional
- Tool coverage: 59% → 64% ▲ functional
- Server version: 1.0.1 → 1.1.0 functional
- “search_sec_event_filings” added an optional parameter “concept_groups” cosmetic
- “search_sec_event_filings” added an optional parameter “ne_tickers” cosmetic
- “search_sec_event_filings” added an optional parameter “tickers” cosmetic
- “search_sec_event_filings” reworded the description of “limit” cosmetic
- “search_sec_event_filings” reworded the description of “query” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 19 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_latest_filing” rewrote its description, which is the text the model reads security
- “get_latest_filing” added an optional parameter “limit” cosmetic
- “get_latest_filing” reworded the description of “filing_registry” cosmetic
- 13 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1606 → 1922 ▼ functional
- Tool coverage: 47% → 57% ▲ functional
- New tool “search_sec_event_filings” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.alphacreek.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alphacreek.ai | CN=YE1,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6b4755daed30d6f8a570a1f9356fb1988d6 |
| SANs: *.alphacreek.ai, alphacreek.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.alphacreek.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| alphacreek.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="alphacreek-mcp", error="invalid_token", scope="filings.search"
Bearer realm="alphacreek-mcp", error="invalid_token", scope="filings.search"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.alphacreek.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.alphacreek.ai/mcp | Inconclusive | 521 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_filing_toc ~208
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) for annual ESEF reports or sec-parser ids (e.g. sp-0000001) for half-year RNS HTML reports.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_document_id | string | – | – |
| company | string | – | – |
| document_type | – | – | Optional document type filter (canonical values only). See Field reference for allowed values per registry. |
| filing_registry | string | – | Filing source registry. sec_edgar — US SEC EDGAR filings. fca_nsm — UK FCA National Storage Mechanism. Omit to search both registries. |
| ticker | string | – | – |
No output schema declared.
No examples provided.
get_latest_filing ~283
Return latest filing metadata for a company or ticker. If ticker and company are omitted, return newly ingested filings newest-first. Omit filing_registry in that mode to include both SEC and FCA. Company results include one metadata object; newly ingested results include a filings list. Each row includes Filing metadata object. Includes `document_type` (Canonical document type. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: annual, half-year, press.) and, for FCA press rows, `announcement_type` (FCA press subtype when document_type is press; null for annual and half-year. Values: 1st Quarter Results, 2nd Quarter Results, 3rd Quarter Results, 4th Quarter Results, Final Results, Preliminary Results, Share Buyback, Trading Update.).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| document_type | – | – | Optional document type filter (canonical values only). See Field reference for allowed values per registry. |
| filing_registry | string | – | Filing source registry. sec_edgar — US SEC EDGAR. fca_nsm — UK FCA NSM. Omit with no ticker/company to list newly ingested filings from both registries. |
| limit | integer | – | Max newly ingested filings when ticker and company are omitted |
| ticker | string | – | – |
No output schema declared.
No examples provided.
list_filings ~253
List available filings for a ticker (newest first) with artifact_document_id and dates. Use filing_registry=fca_nsm for UK FCA NSM reports. Use this first when you need a specific reporting period. Each row includes Filing metadata object. Includes `document_type` (Canonical document type. SEC: 10-K, 10-Q, 20-F, 6-K, 8-K. FCA: annual, half-year, press.) and, for FCA press rows, `announcement_type` (FCA press subtype when document_type is press; null for annual and half-year. Values: 1st Quarter Results, 2nd Quarter Results, 3rd Quarter Results, 4th Quarter Results, Final Results, Preliminary Results, Share Buyback, Trading Update.).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| document_type | – | – | Optional document type filter (canonical values only). See Field reference for allowed values per registry. |
| filing_registry | string | – | Filing source registry. sec_edgar — US SEC EDGAR filings. fca_nsm — UK FCA National Storage Mechanism. Omit to search both registries. |
| limit | integer | – | – |
| ticker | string | – | – |
No output schema declared.
No examples provided.
read_node_content ~253
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 (the same values shown as NODE_ID lines in this tool's output). Returns plain MCP text: an ARTIFACT_DOCUMENT_ID header, then per-node blocks with NODE_ID, TITLE, CITATION_URL, CITATION_MARKDOWN, CONTENT_START … CONTENT_END. Each block's CITATION_URL links to the reader location for that node; CITATION_MARKDOWN is the same link as ready-to-paste markdown [TITLE](CITATION_URL). A requested TOC node may expand into more granular child NODE_ID blocks, each with its own TITLE, CITATION_URL, and CITATION_MARKDOWN. Responses that include citations end with a CITATIONS_IN_THIS_RESPONSE list.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_document_id | string | yes | – |
| 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). |
No output schema declared.
No examples provided.
search_sec_event_filings ~880
Search US SEC 8-K and 6-K current-report nodes for company events and disclosures. Use this to discover issuers across a date range. Do not use this for 10-K or 10-Q filings. How to search: 1. Always pass concept_groups. Every group is required (AND). Within each group's any_of list, one alternative must match (OR). All groups match inside one filing node. Use separate groups for the main context, action or direction, business object or metric, and a causal or limiting relation when that relation is essential. 2. Optionally pass query with likely verbatim disclosure phrases. Each item is an exact adjacent-token phrase. Put alternate full phrasings in the same list. Query plus concept_groups is hybrid search: exact phrase matches receive a score boost, and concept groups recover different wording. Do not put broad topic words such as "China", "AI", "customer", or "restructuring" alone in query. 3. Add real synonyms and alternate filing language to any_of. The concept path uses English stemming, so one base form usually covers inflections (decline/declined/declining and volume/volumes). Stemming does not add synonyms (sales does not mean revenue; reduce does not mean weaken). 4. Do not search with query only. Omit query for concept-only search. If query is omitted, the search is concept-only. 5. Use date filters for time and tickers to search only selected issuers. Pass ne_tickers (or prefix a symbol with !) to omit issuers. 6. Results are candidates, not final conclusions. Call read_node_content with each promising document_id and node_id(s). Verify negation, causal claims, comparisons across periods, and numeric thresholds such as a percentage or dollar amount in the source text. Cite CITATION_MARKDOWN. When you finish an issuer, search again with the same inputs and add its ticker to ne_tickers so later hits come from other issuers. Examples of useful group dimensions include geography + weakening signal + demand metric; CapEx + reduction + guidance; AI/automation…
| Name | Type | Req | Description |
|---|---|---|---|
| concept_groups | array | yes | Required stemmed concept groups. Every group must match in the same node (AND). Any one alternative inside any_of can satisfy its group (OR). Use 2-5 focused groups in most searches. Supply synonyms… |
| end_date | string | yes | Inclusive end date on filing_date (YYYY-MM-DD) |
| limit | integer | – | Maximum unique matches to return across all query phrases. At most 3 matches come from one filing. |
| ne_tickers | – | – | Optional. Omit these issuers (example: ["HOOD"] or ["!HOOD"]). After you finish read_node_content for a ticker, search again with that ticker here. Exclude wins if a ticker is in both lists. Max 50. |
| query | – | – | Optional exact disclosure phrases for hybrid search (max 8). Each phrase requires adjacent tokens in order and does not use stemming. Send complete event phrasings, not standalone topics. Omit this f… |
| start_date | string | yes | Inclusive start date on filing_date (YYYY-MM-DD) |
| tickers | – | – | Optional. Search only these issuers (example: ["NVDA", "MSFT"]). Prefix a symbol with ! to omit it (same as ne_tickers). Max 50. Omit to search all issuers. |
No output schema declared.
No examples provided.
What is the AlphaCreek SEC Filings MCP server?
AlphaCreek SEC Filings MCP is listed in the public MCP registry as ai.alphacreek/alphacreek-mcp. Access SEC filings efficiently (10-K, 10-Q, etc), save time and tokens, and get cited answers. This page covers its hosted endpoint (https://mcp.alphacreek.ai/mcp).
Is the AlphaCreek SEC Filings MCP server safe to use?
AlphaCreek SEC Filings MCP scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AlphaCreek SEC Filings MCP server expose?
AlphaCreek SEC Filings MCP exposes 5 tools: get_latest_filing, list_filings, get_filing_toc, read_node_content, search_sec_event_filings. Their descriptions and schemas cost roughly 1,877 tokens of context every time the server is loaded.
Does the AlphaCreek SEC Filings MCP server require authentication?
Yes. AlphaCreek SEC Filings MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AlphaCreek SEC Filings MCP server still maintained?
AlphaCreek SEC Filings MCP is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.