Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Federal Rules

NPM · @PIPEWORX/MCP-FEDERAL-RULES · 2 COMPONENTS

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

69 Trust /100

Last scanned (22 hours ago)

Scores higher than 40% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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 & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

Changelog

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.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 54

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@pipeworx/mcp-federal-rules@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~699 tokens

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 →

Tool Tokens
get_federal_rule ~358

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.

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

No output schema declared.

No examples provided.

list_federal_rules ~140

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.

NameTypeReqDescription
setstringyesRule set: frcp (Civil Procedure), fre (Evidence), frap (Appellate), frcrp (Criminal Procedure), frbp (Bankruptcy). Aliases such as frcrmp and "civil" are accepted.

No output schema declared.

No examples provided.

search_federal_rules ~201

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.

NameTypeReqDescription
limitnumber–Max results (default 20, max 50).
querystringyesWords from the rule title, e.g. "seizing property", "business records".
setstring–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.

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-federal-rules

# add to Claude Code
claude mcp add pipeworx-io-federal-rules -- npx -y @pipeworx/mcp-federal-rules
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.