New Mexico Code
NPM · @PIPEWORX/MCP-NEW-MEXICO-CODE · 2 COMPONENTS
New Mexico Statutes Annotated 1978 (NMSA 1978) — section lookup, chapter list, and catchline…
Available components
Last scanned (12 hours ago)
Scores higher than 76% 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-new-mexico-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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 542 tokens (~180/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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-new-mexico-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-new-mexico-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-new-mexico-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655712103 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:68c4394d896e320d03474727210f14b7cd7c142bb5667d467114fbfb3a0762906d798eae175c7c447faa77bb8c54a2a0f8bdf2aa8f497df083991298c |
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 →
nm_chapters ~73
List all chapters of the New Mexico Statutes Annotated 1978 with their official names, e.g. Chapter 30 is Criminal Offenses, Chapter 40 is Domestic Affairs. Routing help for when you know the subject but not the chapter number — call this or nm_search before guessing a citation. Keyless.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nm_search ~130
Search the New Mexico Statutes Annotated 1978 BY TOPIC or keyword rather than citation, e.g. "landlord security deposit", "concealed handgun", "grounds for divorce". Matches official section CATCHLINES (and chapter names), not full statutory body text. Returns matching citations, catchlines, and chapter names; call nm_statute with a result's citation for the full text. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return, default 10, max 25. |
| query | string | yes | Topic or keywords, e.g. "landlord security deposit". |
No output schema declared.
No examples provided.
nm_statute ~281
Get the FULL TEXT of a section of the New Mexico Statutes Annotated 1978 (NMSA 1978) by citation, e.g. "30-2-1" (Murder) or "40-4-1" (grounds for divorce). Accepts "30-2-1", "NMSA 1978, § 30-2-1", or "§ 30-2-1". Returns the current statutory text, its official catchline, chapter name, and legislative "History:" line. New Mexico publishes each CHAPTER as one PDF rather than per-section, so a bare citation (no chapter name) resolves via a baked chapter index — most chapters are covered; an uncovered one reports chapter_not_baked rather than a false no-match. Keyless. Use for "what does NMSA 30-2-1 say" or to check a New Mexico statute a case or contract relies on.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | Section citation as chapter-article-section, e.g. "30-2-1" (murder) or "40-4-1" (divorce). A lettered chapter keeps its letter, e.g. "59A-1-1" (Insurance Code) or "32A-4-1" (Children's Code). |
No output schema declared.
No examples provided.
How do I install the New Mexico Code MCP server?
New Mexico Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-new-mexico-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-new-mexico-code
claude mcp add pipeworx-io-new-mexico-code -- npx -y @pipeworx/mcp-new-mexico-code
What is the New Mexico Code MCP server?
New Mexico Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/new-mexico-code. New Mexico Statutes Annotated 1978 (NMSA 1978), section lookup, chapter list, and catchline… This page covers its npm package (@pipeworx/mcp-new-mexico-code).
Is the New Mexico Code MCP server safe to use?
New Mexico Code scores 83 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 New Mexico Code MCP server expose?
New Mexico Code exposes 3 tools: nm_statute, nm_search, nm_chapters. Their descriptions and schemas cost roughly 484 tokens of context every time the server is loaded.
Is the New Mexico Code MCP server still maintained?
New Mexico 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 New Mexico Code MCP server under?
New Mexico 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.