Tennessee Code
NPM · @PIPEWORX/MCP-TENNESSEE-CODE · 2 COMPONENTS
Tennessee Code Annotated (T.C.A.) — Tennessee state statutes by citation and by topic. Fleet #2885.
Available components
Last scanned (2 hours ago)
Scores higher than 58% 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-tennessee-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 656 tokens (~328/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 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 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
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.
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: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-tennessee-code@0.2.0
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-tennessee-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-tennessee-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560408629 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2b4b38d326fa0316c5fa0ee29ab98aaec8bc6c1731da5da58e5799dc80c79327d690d650cb63c492ad654328dd8732dfee37195e18ce572a397b2a166 |
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 →
tn_search ~183
Search the Tennessee Code Annotated (T.C.A.) BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". This matches OFFICIAL CATCHLINES/HEADINGS (e.g. "39-13-202. First degree murder." matches "murder"), not the full statutory body text — a word that appears only inside a section's text and not its heading will not be found this way. Returns matching citations, catchlines and chapter context; call tn_statute with a citation for the full text. Same 2021-05-21 point-in-time snapshot as tn_statute. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, default 10, max 50. |
| query | string | yes | Topic or keywords, e.g. "security deposit". |
No output schema declared.
No examples provided.
tn_statute ~418
Get a section of the Tennessee Code Annotated (T.C.A.) — Tennessee state law — by citation. "39-13-202" is first degree murder; "66-28-301" is the security-deposit statute. Accepts natural forms: "39-13-202", "T.C.A. 39-13-202", "Tenn. Code Ann. § 39-13-202". Returns the statutory text, catchline, chapter context, and the "Acts ..." legislative history when the text carries one — but NOT case-law digest ("Notes to Decisions"), which this pack excludes. IMPORTANT: this is a POINT-IN-TIME snapshot frozen at 2021-05-21 (release 76 of Public.Resource.Org's scan), not the current code — Tennessee's only current electronic TCA is behind a LexisNexis login/session wall this pack cannot reach (confirmed by Tennessee Court of Appeals litigation; see this pack's README). Every response states current_through explicitly. Also returns later_acts: a dated, linked overlay of every Public Chapter this pack's own home-built index (built from Tennessee General Assembly Effective Reports and bill text, since Tennessee publishes no citation-to-act index) shows touching this exact citation since the 2021-05-21 snapshot (Public Chapter number, General Assembly, bill id, link to the bill text) — NOT merged into the text, explicitly labelled so, with sessions_checked naming every Effective Report the index covers even when later_acts is empty. Use for "what does T.C.A. 39-13-202 say" or to check a Tennessee statute AND whether it has been amended since 2021-05-21. All 68 published titles are covered. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | Section citation, e.g. "39-13-202" (murder) or "66-28-301" (security deposits). Title-chapter-section; the title is the part before the first dash. |
No output schema declared.
No examples provided.
How do I install the Tennessee Code MCP server?
Tennessee Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-tennessee-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-tennessee-code
claude mcp add pipeworx-io-tennessee-code -- npx -y @pipeworx/mcp-tennessee-code
What is the Tennessee Code MCP server?
Tennessee Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tennessee-code. Tennessee Code Annotated (T.C.A.), Tennessee state statutes by citation and by topic. Fleet #2885. This page covers its npm package (@pipeworx/mcp-tennessee-code).
Is the Tennessee Code MCP server safe to use?
Tennessee Code scores 78 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 Tennessee Code MCP server expose?
Tennessee Code exposes 2 tools: tn_statute, tn_search. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.
Is the Tennessee Code MCP server still maintained?
Tennessee 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 Tennessee Code MCP server under?
Tennessee 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.