Sec Ftd
NPM · @PIPEWORX/MCP-SEC-FTD · 2 COMPONENTS
SEC Fails-to-Deliver (CNS fails data).
Available components
Last scanned (37 minutes ago)
Scores higher than 81% 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-ftd). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 482 tokens (~160/item across 3 items; 3 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +4
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-sec-ftd@0.2.1
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-ftd |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sec-ftd/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692341748 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:896a4643bbf61640ab0a2bd3ecfc3a46bdd31546141a879cb4c80f6d469bfc3848b7236e03f3cae5d94ed08cea81130f273999771d6d4ff440901f6b0 |
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 →
ftd_largest ~167
The largest fails-to-deliver in one SEC reporting period, ranked by share count, from the CNS fails-to-deliver file. Returns ticker, security description, settlement date, shares failed and price. A fail-to-deliver is a settlement failure and is NOT evidence of naked short selling — the SEC says so explicitly; ordinary causes include processing delays and illiquidity. Answers "which stocks had the most failed deliveries this period".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many securities to return, 1-100 (default 25). |
| period | string | – | Reporting period as YYYYMM plus a or b — "202607b" is the second half of July 2026. Omit for the most recent published period. Call ftd_periods to see what exists. |
No output schema declared.
No examples provided.
ftd_periods ~72
Which SEC fails-to-deliver reporting periods are currently published, newest first. SEC posts one file per half month ("a" = 1st-15th, "b" = 16th to month end). Use this to pick a valid period argument, or to see how current the data is.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ftd_security ~189
Fails-to-deliver history for one US-listed security from the SEC's CNS fails-to-deliver file, by ticker symbol. Returns each settlement date with the number of shares that failed to deliver, the closing price, the security description and its CUSIP. A fail-to-deliver is a settlement failure — shares not delivered on time — and the SEC states it is NOT evidence of naked short selling; ordinary causes include processing delays, order-entry errors and illiquidity. Answers "what were the fails-to-deliver for GME", "has this stock had settlement failures recently".
| Name | Type | Req | Description |
|---|---|---|---|
| periods | number | – | How many recent half-month files to search, 1-6 (default 2, roughly the last month). SEC publishes one file per half month. |
| symbol | string | yes | Ticker symbol as SEC writes it, e.g. "GME", "TSLA". |
No output schema declared.
No examples provided.
How do I install the Sec Ftd MCP server?
Sec Ftd runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-ftd. 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-ftd
claude mcp add pipeworx-io-sec-ftd -- npx -y @pipeworx/mcp-sec-ftd
What is the Sec Ftd MCP server?
Sec Ftd is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-ftd. SEC Fails-to-Deliver (CNS fails data). This page covers its npm package (@pipeworx/mcp-sec-ftd).
Is the Sec Ftd MCP server safe to use?
Sec Ftd scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 Ftd MCP server expose?
Sec Ftd exposes 3 tools: ftd_security, ftd_largest, ftd_periods. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Is the Sec Ftd MCP server still maintained?
Sec Ftd is still listed as active in the MCP registry. We last reached this channel on 6 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 Ftd MCP server under?
Sec Ftd declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Sec Ftd MCP server?
VerifyMCP ran 16 checks on Sec Ftd, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.