Indiana Court Rules
NPM · @PIPEWORX/MCP-INDIANA-COURT-RULES · 2 COMPONENTS
Indiana court rules.
Available components
Last scanned (9 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
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-indiana-court-rules). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 744 tokens (~248/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 Management23
- Stability observed for 7 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
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 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-indiana-court-rules@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-indiana-court-rules |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-indiana-court-rules/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637434184 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f53618c1f6fdcddcaf10cfc492995ca7c8aeb12d6c8b0bf36f58aed76d74922bafcd17dfe74cea8580b231dff2875bb2d57db03be151209064fc1955e |
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 →
in_court_rule ~234
Full text of one Indiana statewide court rule by citation, e.g. Trial Rule 60 (set "trial", rule "60"), Appellate Rule 9, Evidence Rule 401, Criminal Rule 2.1, Professional Conduct 1.6. Returns the rule heading, effective date, text, and the published version history where one exists. Add a subdivision like "60(B)" to also get just that part. Source: Indiana Supreme Court, Indiana Rules of Court. Not the Indiana Code (use indiana-code) and not county local rules (use in_local_rules).
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | Rule number as cited: "60", "60(B)", "4.1", "401", "1.6". Decimals use a dot. |
| set | string | yes | Rule set: trial, appellate, evidence, criminal, admission-discipline, prof-conduct, small-claims, judicial-conduct, admin, adr, jury, tax, records, and others. Common names like "trial rules" or "pro… |
No output schema declared.
No examples provided.
in_court_rules_list ~108
List the Indiana Rules of Court. With a set (e.g. "trial"), returns every rule in it with its number and title, so you can find the right citation. With no set, returns every rule set with its name and rule count. Source: Indiana Supreme Court, Indiana Rules of Court.
| Name | Type | Req | Description |
|---|---|---|---|
| set | string | – | Rule set id or common name, e.g. "trial", "appellate", "evidence". Omit to list all sets. |
No output schema declared.
No examples provided.
in_local_rules ~342
Text of an Indiana county's local court rules (circuit/superior court rules, district governance plan, city-court rules). Given a county (e.g. "Johnson"), returns the county's documents and the rule text: pass query for a keyword search across the county's rules ("motion practice", "bond", "court reporter"), rule for one citation as the county numbers it ("LR41-TR-102"), or neither to read the document from the start (paginate with offset). Covers 91 of 92 counties; a document with no machine-readable text, or a county with no published rules, says so and returns the document link rather than an empty answer. With no county, returns every county with its coverage. Every response carries data_as_of. Source: Indiana Supreme Court, Indiana Judicial Branch, local court rules by county.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Indiana county name, with or without "County", e.g. "Johnson", "St. Joseph". Omit to list counties and coverage. |
| document | number | – | 1-based document number from the documents list, to restrict to one document. |
| max_chars | number | – | Maximum characters of rule text to return (500-20000, default 6000). |
| offset | number | – | Character offset when reading a document from the start. |
| query | string | – | Keywords to find in the county's local rules, e.g. "motion for continuance". Returns the best-matching passages. |
| rule | string | – | A rule citation as the county numbers it, e.g. "LR41-TR-102". Returns that rule's text. |
No output schema declared.
No examples provided.
How do I install the Indiana Court Rules MCP server?
Indiana Court Rules runs locally as an npm package, launched with npx -y @pipeworx/mcp-indiana-court-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-indiana-court-rules
claude mcp add pipeworx-io-indiana-court-rules -- npx -y @pipeworx/mcp-indiana-court-rules
What is the Indiana Court Rules MCP server?
Indiana Court Rules is an MCP server listed in the public MCP registry as io.github.pipeworx-io/indiana-court-rules. Indiana court rules. This page covers its npm package (@pipeworx/mcp-indiana-court-rules).
Is the Indiana Court Rules MCP server safe to use?
Indiana Court Rules scores 82 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 Indiana Court Rules MCP server expose?
Indiana Court Rules exposes 3 tools: in_court_rule, in_court_rules_list, in_local_rules. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.
Is the Indiana Court Rules MCP server still maintained?
Indiana Court Rules 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 Indiana Court Rules MCP server under?
Indiana Court 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.