# Sec Regulations (npm · @pipeworx/mcp-sec-regulations)

SEC Regulations MCP — US securities regulations (17 CFR).

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sec-regulations`
- 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-05.

- **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-regulations).
  - 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**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 917 tokens (~458/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Regulations MCP server?

Sec Regulations runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-regulations. 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-regulations -- npx -y @pipeworx/mcp-sec-regulations
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 81, +3)

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

### 2026-11-01 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `sec_regulation` (~580 tokens)

Get the full text of one SEC regulation — a US securities regulation codified in 17 CFR (SEC and CFTC) — by its citation or common rule name. Returns the exact regulatory wording currently in force. Answers "what does SEC Rule 10b-5 require", "what is the SEC regulation for X", "read 17 CFR 240.10b-5", "what does Regulation S-K item 303 say", "the SEC disclosure requirement for X". Forgiving input: "240.10b-5", "17 CFR 240.10b-5", "§ 229.303", "230.506(b)" (paragraph stripped to the section), "240.15l-1", "part 240". Common rule names resolve automatically: "Rule 10b-5" -> 240.10b-5, "Rule 10b5-1", "Rule 144", "Rule 506", "Rule 15c3-1" (net capital), "Regulation S-K" -> part 229, "Regulation S-X" -> part 210, "Reg FD" -> 243.100, "Reg NMS" -> part 242, "Reg SHO", "Reg D", "Reg A", "Reg S", "Regulation BI" -> 240.15l-1, "Form ADV" / Investment Advisers Act rules -> part 275, "Rule 206(4)-7". Covers securities regulation across all of Title 17: registration and offerings, disclosure requirements, insider trading, proxy rules, broker-dealer obligations, investment advisers, market structure, and CFTC commodity and derivatives regulation. Pass a whole part (e.g. "229" or "part 240") to get that part's section list. Example: sec_regulation({ citation: "240.10b-5" }) -> employment of manipulative and deceptive devices; sec_regulation({ citation: "Rule 10b-5" }) -> same section via the rule name. Keyless. This pack is the SEC RULES text; the separate `edgar` and `sec-xbrl` packs serve SEC filings data (company filings, XBRL financials).

Input parameters:

- `citation` (string, required): Securities-regulation citation or rule name. A section: "240.10b-5", "17 CFR 240.10b-5", "§ 229.303", "230.506(b)", "275.206(4)-7". A rule name: "Rule 10b-5", "Rule 144", "Regulation S-K", "Reg FD",…

### `sec_regulations_search` (~283 tokens)

Keyword search across the SEC regulations — US securities regulation in 17 CFR (SEC and CFTC). Answers "what SEC regulations cover X", "the SEC rule about X", "find the securities regulation for X", "which disclosure requirement applies to X", "the CFTC regulation on X". Great for topics: insider trading and material nonpublic information, disclosure requirements and MD&A, registration statements and exempt offerings, private placements and accredited investors, proxy solicitations and shareholder proposals, broker-dealer net capital and customer protection, investment adviser fiduciary duty and custody, market structure and short sales, tender offers, beneficial ownership reporting, swaps and commodity futures. Returns matching securities rules with citation (17 CFR), heading, excerpt, and source URL. Example: sec_regulations_search({ query: "insider trading" }); sec_regulations_search({ query: "accredited investor definition", limit: 15 }). Keyless. Searches the SEC RULES text; the separate `edgar` and `sec-xbrl` packs search SEC filings data.

Input parameters:

- `limit` (number): Max results to return, 1-20 (default 10).
- `query` (string, required): Securities-regulation topic or phrase, e.g. "insider trading", "accredited investor definition", "management discussion and analysis", "net capital requirements", "short sale".

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Sec Regulations MCP server?

Sec Regulations is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-regulations. SEC Regulations MCP, US securities regulations (17 CFR). This page covers its npm package (@pipeworx/mcp-sec-regulations).

### Is the Sec Regulations MCP server safe to use?

Sec Regulations scores 81 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 Regulations MCP server expose?

Sec Regulations exposes 2 tools: sec_regulation, sec_regulations_search. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

### Is the Sec Regulations MCP server still maintained?

Sec Regulations 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 Regulations MCP server under?

Sec Regulations 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 Regulations MCP server?

VerifyMCP ran 16 checks on Sec Regulations, 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-regulations
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-sec-regulations
- Repository: https://github.com/pipeworx-io/mcp-sec-regulations
- Website: https://pipeworx.io/packs/sec-regulations
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-sec-regulations/pipeworx-mcp-sec-regulations.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-sec-regulations/pipeworx-mcp-sec-regulations/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-sec-regulations/pipeworx-mcp-sec-regulations.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-sec-regulations/pipeworx-mcp-sec-regulations