# Sec Ftd (npm · @pipeworx/mcp-sec-ftd)

SEC Fails-to-Deliver (CNS fails data).

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-sec-ftd/sec-ftd-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-ftd/sec-ftd-mcp)
- npm · `@pipeworx/mcp-sec-ftd`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sec-ftd`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sec-ftd).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - 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.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-sec-ftd -- npx -y @pipeworx/mcp-sec-ftd
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-sec-ftd": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-ftd"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-sec-ftd": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-ftd"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-sec-ftd -- npx -y @pipeworx/mcp-sec-ftd
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-sec-ftd": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-sec-ftd"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-sec-ftd --command npx --arg -y --arg @pipeworx/mcp-sec-ftd
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-sec-ftd:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-sec-ftd"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-sec-ftd": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-sec-ftd"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-sec-ftd -t stdio -c npx -a -y @pipeworx/mcp-sec-ftd
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-sec-ftd": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-ftd"
      ]
    }
  }
}
```

## 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-11-05 (score 84, +4)

- [security regression] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (3)

### `ftd_security` (~189 tokens)

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".

Input parameters:

- `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, required): Ticker symbol as SEC writes it, e.g. "GME", "TSLA".

### `ftd_largest` (~167 tokens)

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".

Input parameters:

- `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.

### `ftd_periods` (~72 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd#diagnostics

## Score history

- 2026-11-06: 84
- 2026-11-05: 84
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-sec-ftd
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-sec-ftd
- Repository: https://github.com/pipeworx-io/mcp-sec-ftd
- Website: https://pipeworx.io/packs/sec-ftd
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-sec-ftd/pipeworx-mcp-sec-ftd