South Dakota Code
NPM · @PIPEWORX/MCP-SOUTH-DAKOTA-CODE · 2 COMPONENTS
South Dakota Codified Laws — state statutes by citation and by topic. Fleet #2748.
Available components
Last scanned (10 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-south-dakota-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 498 tokens (~249/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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- 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.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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 →
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 +3
- Stability: unverified → 0.23 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 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-south-dakota-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-south-dakota-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-south-dakota-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692355966 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:65de6b1b5edc1b5aa00696ccab8eeef1716fedcab8cc9e4794283bb32a7aed107891210fd70c2a650d97b7eb607eeea51950fe4a4b5959f3bff44d916 |
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 →
sd_search ~170
Search the South Dakota Codified Laws BY TOPIC or keyword rather than citation — "landlord security deposit", "concealed pistol permit", "homicide". Matches against the Legislature's own official section and chapter CATCHLINES across the whole Code (not full statutory prose — South Dakota does not publish a full-text search of Code section text, verified live), e.g. "landlord" surfaces sections like "Modification of lease--Written notice by landlord" even in a chapter not named for landlords. Returns matching citations and catchlines; call sd_statute with a 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.
sd_statute ~269
Get the FULL TEXT of a section of the South Dakota Codified Laws — South Dakota state law — by citation. "22-16-4" is murder in the first degree; "43-32-13" covers a landlord's notice of lease modification. Accepts natural forms: "22-16-4", "SDCL 22-16-4", "§ 22-16-4". Returns the current statutory text, the official catchline, and — when present — the "Source:" line listing every session law that enacted or amended the section (split out into `history`). South Dakota publishes the CURRENT text only, no per-year historical archive, so a prior (pre-amendment) version of the text is not available; this tool says so rather than guessing. Keyless. Use for "what does SDCL 22-16-4 say" or to check a South Dakota statute a case or lease relies on.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | Section citation, title-chapter-section, e.g. "22-16-4" (murder in the first degree) or "43-32-13" (landlord notice of lease modification). Some sections carry a decimal suffix, e.g. "22-16-20.1". |
No output schema declared.
No examples provided.
How do I install the South Dakota Code MCP server?
South Dakota Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-south-dakota-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-south-dakota-code
claude mcp add pipeworx-io-south-dakota-code -- npx -y @pipeworx/mcp-south-dakota-code
What is the South Dakota Code MCP server?
South Dakota Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/south-dakota-code. South Dakota Codified Laws, state statutes by citation and by topic. Fleet #2748. This page covers its npm package (@pipeworx/mcp-south-dakota-code).
Is the South Dakota Code MCP server safe to use?
South Dakota Code 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 South Dakota Code MCP server expose?
South Dakota Code exposes 2 tools: sd_statute, sd_search. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.
Is the South Dakota Code MCP server still maintained?
South Dakota 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 South Dakota Code MCP server under?
South Dakota 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.
What did VerifyMCP test on the South Dakota Code MCP server?
VerifyMCP ran 15 checks on South Dakota Code, 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 South Dakota Code: Security disclosure. 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.