Sec Form D
NPM · @PIPEWORX/MCP-SEC-FORM-D · 2 COMPONENTS
SEC Form D fundraising intelligence.
Available components
Last scanned (5 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sec-form-d). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1184 tokens (~148/item across 8 items; 8 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sec-form-d@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-sec-form-d |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sec-form-d/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3562860817 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:58c7558b2dbc7a104489cecd2ca0aa327363f55cb7c637e59e9051f3b269766053ef08409aefb72623407e0ff43abe64cd439c90f34f084bc3d58e7ce |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
form_d_amendment_chains ~84
Group one issuer’s recent Form D notices into original-plus-amendment chains using each filing’s previous accession number. This prevents amendments from being mistaken for separate raises; incomplete SEC recent history can leave a chain without its original.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
| limit | number | – | Filings to inspect (1-20, default 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | yes | – |
| cik | string | yes | – |
| interpretation | string | yes | – |
| issuer_name | string | – | – |
| returned_chains | number | yes | – |
No examples provided.
form_d_issuer_history ~90
List one private issuer’s Form D filing and amendment history from SEC submissions data, with each notice hydrated from official XML. Do not sum amendments: later notices may restate the same offering rather than represent new capital.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | Issuer CIK, with or without leading zeros. |
| limit | number | – | Filings to hydrate (1-20, default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| filings | array | yes | – |
| returned | number | yes | – |
No examples provided.
form_d_latest_offering_states ~66
Return only the latest filing state from each amendment-aware Form D chain for an issuer. This is a normalized regulatory snapshot, not proof that the amount sold closed or that separate chains are economically distinct rounds.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
| limit | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| offerings | array | yes | – |
| returned | number | yes | – |
No examples provided.
form_d_offering_detail ~78
Retrieve and normalize one official Form D XML filing by SEC accession number. Returns offering amounts, first sale, investors, exemptions, securities, issuer identity, executives/related persons, commissions, and exact SEC provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | yes | SEC accession number, e.g. 0002036057-26-000002. |
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | yes | – |
| cik | string | yes | – |
| filing_date | string | – | – |
| filing_url | string | yes | – |
| is_amendment | boolean | yes | – |
| issuer_name | string | – | – |
| total_amount_sold | number | – | – |
| total_offering_amount | number | – | – |
| total_remaining | number | – | – |
No examples provided.
form_d_recent_raises ~383
Recent SEC Form D exempt-offering notices, newest first, hydrated from official filing XML with offering amount, amount sold, investors, security types, industry, issuer and related persons. SAMPLE, NOT A CENSUS: this inspects only the newest few dozen notices counting back from `until`, no matter how wide a window you ask for — ask for a month and you get roughly its final day or two. `total_search_matches` is the SIZE OF THE WINDOW, not the number examined; `scanned` is the number examined and `scanned_window` is the date range those actually cover. To cover a period densely, step through it in short windows rather than widening `since`. A Form D is a self-reported offering notice—not proof that a financing round closed. Amendments are labeled and must not be double-counted.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look back this many days from `until` instead of supplying `since` (1-3650). An explicit `since` wins. |
| include_amendments | boolean | – | Include amended notices (default true). |
| industry | string | – | Optional case-insensitive industry substring, e.g. "Biotechnology". |
| limit | number | – | Results to hydrate and return (1-10, default 8). |
| min_amount | number | – | Alias for `minimum_sold`: minimum reported amount sold in USD. |
| minimum_sold | number | – | Only return offerings reporting at least this much sold, in USD. Also accepted as `min_amount`. |
| since | string | – | Start filing date YYYY-MM-DD. Default: 7 days before `until` (NOT 7 days before today — so an `until` in the past gives a sensible window instead of erroring). |
| until | string | – | End filing date YYYY-MM-DD. Default today. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | "complete" = every Form D in `window` was inspected. "sample" = only the newest `scanned` were and the rest of `window` was never looked at. |
| coverage_note | string | – | – |
| offerings | array | yes | – |
| returned | number | yes | – |
| scanned | number | – | How many notices were actually hydrated and examined. |
| scanned_window | object|null | – | The date range the inspected filings actually cover. Narrower than `window` whenever `coverage` is "sample". |
| total_search_matches | number | – | Form D notices filed in `window`. NOT the number examined — that is `scanned`. |
| window | object | – | The date range asked for. |
No examples provided.
form_d_related_person_network ~64
Summarize filer-reported related persons across one issuer’s recent Form D history, with filing and chain counts. Related persons are executives, directors, promoters, or similar roles—not disclosed investors.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
| limit | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
| interpretation | string | yes | – |
| people | array | yes | – |
No examples provided.
form_d_related_person_search ~123
Find Form D notices mentioning an executive, promoter, director, or other related person, then return only filings whose parsed related-person list matches the name. Useful for mapping repeat founders and fund managers; relationships are filer-supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Matching filings to return (1-10, default 5). |
| person | string | yes | Person name or distinctive substring. |
| since | string | – | Start filing date YYYY-MM-DD. Default 5 years ago. |
| until | string | – | End filing date YYYY-MM-DD. Default today. |
| Name | Type | Req | Description |
|---|---|---|---|
| offerings | array | yes | – |
| returned | number | yes | – |
No examples provided.
form_d_search_issuers ~242
Look up a named company's or fund's SEC Form D filing by the issuer's name — what it reported: total offering amount, amount sold, number of investors already invested, date of first sale, the federal exemption claimed (Rule 506(b), 506(c), Investment Company Act 3(c)(1)/3(c)(7)), securities offered and related persons. Pass the name, e.g. "YCA26, L.P." or "Chickadee Biomedicines"; SEC EDGAR full-text search covers every Form D on file (default the last 5 years), so the issuer's filing is found wherever it sits. Also finds filings naming an executive or fund. A Form D is a self-reported offering notice, not an independently verified closed round.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results to hydrate (1-10, default 5). |
| query | string | yes | Issuer, person, fund, or filing text to search. |
| since | string | – | Start filing date YYYY-MM-DD. Default 5 years ago. |
| until | string | – | End filing date YYYY-MM-DD. Default today. |
| Name | Type | Req | Description |
|---|---|---|---|
| offerings | array | yes | – |
| returned | number | yes | – |
No examples provided.
How do I install the Sec Form D MCP server?
Sec Form D runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-form-d. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-sec-form-d
claude mcp add pipeworx-io-sec-form-d -- npx -y @pipeworx/mcp-sec-form-d
What is the Sec Form D MCP server?
Sec Form D is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-form-d. SEC Form D fundraising intelligence. This page covers its npm package (@pipeworx/mcp-sec-form-d).
Is the Sec Form D MCP server safe to use?
Sec Form D scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Sec Form D MCP server expose?
Sec Form D exposes 8 tools: form_d_recent_raises, form_d_search_issuers, form_d_offering_detail, form_d_issuer_history, form_d_related_person_search, and 3 more. Their descriptions and schemas cost roughly 1,130 tokens of context every time the server is loaded.
Is the Sec Form D MCP server still maintained?
Sec Form D is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sec Form D MCP server under?
Sec Form D declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.