# Federal Rules (npm · @pipeworx/mcp-federal-rules)

Federal Rules pack -- the text of the federal court rules, read live per request from the Legal…

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-federal-rules/federal-rules-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-federal-rules/federal-rules-mcp)
- npm · `@pipeworx/mcp-federal-rules`: 69/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-federal-rules/pipeworx-mcp-federal-rules.md), [page](https://verifymcp.io/servers/pipeworx-io-federal-rules/pipeworx-mcp-federal-rules)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-federal-rules`
- Version: `0.1.0`
- 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-21.

- **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**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 754 tokens (~251/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Federal Rules MCP server?

Federal Rules runs locally as an npm package, launched with npx -y @pipeworx/mcp-federal-rules. 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-federal-rules -- npx -y @pipeworx/mcp-federal-rules
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-federal-rules -- npx -y @pipeworx/mcp-federal-rules
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-federal-rules --command npx --arg -y --arg @pipeworx/mcp-federal-rules
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-16 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 54)

First indexed and scored.

## MCP tools (3)

### `get_federal_rule` (~358 tokens)

Get the full text of a federal court rule, optionally one subdivision. Covers the Federal Rules of Civil Procedure (FRCP, e.g. "Rule 64 seizing a person or property", "Rule 12(b)(6)", "Rule 56"), Evidence (FRE, e.g. "803(6) business records hearsay exception"), Appellate Procedure (FRAP, e.g. "Rule 4 time to appeal"), Criminal Procedure (FRCrP) and Bankruptcy Procedure (FRBP). Pass the citation pieces: set="frcp", rule="64", subdivision="(b)" -- or rule="64(b)" / "4(a)(1)(B)". Returns the requested subdivision text (when given), the whole rule text, the amendment/effective credit line, whether Advisory Committee notes exist (include_notes=true returns them), and a source link. An unknown rule number or subdivision returns an explicit not-found.

Input parameters:

- `include_notes` (boolean): Include Advisory Committee notes / committee notes text (truncated at 12,000 characters). Default false.
- `rule` (string, required): Rule number, optionally with subdivisions: "64", "4.1", "803(6)", "12(b)(6)". A leading "Rule" is ignored.
- `set` (string, required): Rule set: frcp (Civil Procedure), fre (Evidence), frap (Appellate), frcrp (Criminal Procedure), frbp (Bankruptcy). Aliases such as frcrmp and "civil" are accepted.
- `subdivision` (string): Optional subdivision path, e.g. "(b)" or "(a)(1)(B)". Appended to any subdivision already in rule.

### `list_federal_rules` (~140 tokens)

List every rule in a federal court rules set with its number and title: FRCP (civil procedure), FRE (evidence), FRAP (appellate), FRCrP (criminal procedure) or FRBP (bankruptcy). Also returns the "as amended to" date the publisher states for the set. Use to find the rule number before get_federal_rule.

Input parameters:

- `set` (string, required): Rule set: frcp (Civil Procedure), fre (Evidence), frap (Appellate), frcrp (Criminal Procedure), frbp (Bankruptcy). Aliases such as frcrmp and "civil" are accepted.

### `search_federal_rules` (~201 tokens)

Find federal court rules by words in their title, e.g. "summary judgment" (FRCP 56), "hearsay" (FRE 801-807), "notice of appeal" (FRAP), "discovery". Matches rule titles and numbers only, not the full rule text. Searches one set, or all five when set is omitted. Returns rule numbers and titles; call get_federal_rule for the text.

Input parameters:

- `limit` (number): Max results (default 20, max 50).
- `query` (string, required): Words from the rule title, e.g. "seizing property", "business records".
- `set` (string): Rule set: frcp (Civil Procedure), fre (Evidence), frap (Appellate), frcrp (Criminal Procedure), frbp (Bankruptcy). Aliases such as frcrmp and "civil" are accepted. Omit to search all sets.

## Diagnostics

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

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 54

## Common questions

### What is the Federal Rules MCP server?

Federal Rules is an MCP server listed in the public MCP registry as io.github.pipeworx-io/federal-rules. Federal Rules pack -- the text of the federal court rules, read live per request from the Legal… This page covers its npm package (@pipeworx/mcp-federal-rules).

### Is the Federal Rules MCP server safe to use?

Federal Rules scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Federal Rules MCP server expose?

Federal Rules exposes 3 tools: get_federal_rule, list_federal_rules, search_federal_rules. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

### Is the Federal Rules MCP server still maintained?

Federal Rules is still listed as active in the MCP registry. We last reached this channel on 21 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 Federal Rules MCP server under?

Federal Rules 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 Federal Rules MCP server?

VerifyMCP ran 15 checks on Federal Rules, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Federal Rules: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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-federal-rules
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-federal-rules
- Repository: https://github.com/pipeworx-io/mcp-federal-rules
- Website: https://pipeworx.io/packs/federal-rules
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-federal-rules/pipeworx-mcp-federal-rules.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-federal-rules/pipeworx-mcp-federal-rules/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-federal-rules/pipeworx-mcp-federal-rules.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-federal-rules/pipeworx-mcp-federal-rules
