Montana Code
NPM · @PIPEWORX/MCP-MONTANA-CODE · 2 COMPONENTS
Montana Code Annotated — state statutes by citation.
Available components
Last scanned (13 hours ago)
Scores higher than 81% 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-montana-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 338 tokens (~169/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
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-montana-code@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-montana-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-montana-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655542023 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7cf53ef22ff132ef9f93fbf6082e20e402ab074eaf0b7d845f0612f8cc0dff10765354cedc56fe573ca8babf507c31b0feb844e65bc138173070768cb |
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 →
mt_code_search ~163
Search the Montana Code Annotated BY TOPIC or keyword rather than citation -- "computing time deadline holiday", "landlord security deposit", "deliberate homicide". Covers all 54 MCA titles, including Title 25 chapter 20, the Montana Rules of Civil Procedure (Rule 6 computing time is MCA 25-20-206). Returns ranked sections with citation, heading and an opening excerpt; call mt_code_section with a result's citation for the full text. Full-text match, not semantic search. A query with no hits returns found:false. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, default 10, max 25. |
| query | string | yes | Topic or keywords, e.g. "computing time period days holiday". |
No output schema declared.
No examples provided.
mt_code_section ~120
Get the FULL TEXT of a section of the Montana Code Annotated — Montana state law — by citation. "MCA 45-5-102" is deliberate homicide. Returns the statutory text. Keyless. Use for "what does MCA 45-5-102 say" or to check a Montana statute a case relies on.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | Section as cited, e.g. "45-5-102" (deliberate homicide) or "61-8-401" (DUI). Title-chapter-section. |
No output schema declared.
No examples provided.
How do I install the Montana Code MCP server?
Montana Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-montana-code. 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-montana-code
claude mcp add pipeworx-io-montana-code -- npx -y @pipeworx/mcp-montana-code
What is the Montana Code MCP server?
Montana Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/montana-code. Montana Code Annotated, state statutes by citation. This page covers its npm package (@pipeworx/mcp-montana-code).
Is the Montana Code MCP server safe to use?
Montana Code scores 84 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 Montana Code MCP server expose?
Montana Code exposes 2 tools: mt_code_section, mt_code_search. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.
Is the Montana Code MCP server still maintained?
Montana Code 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 Montana Code MCP server under?
Montana Code declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.