# Tennessee Code (npm · @pipeworx/mcp-tennessee-code)

Tennessee Code Annotated (T.C.A.) — Tennessee state statutes by citation and by topic. Fleet #2885.

- Trust score: 78/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-tennessee-code/tennessee-code-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-tennessee-code/tennessee-code-mcp)
- npm · `@pipeworx/mcp-tennessee-code`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code.md), [page](https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-tennessee-code`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-tennessee-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-tennessee-code -- npx -y @pipeworx/mcp-tennessee-code
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-tennessee-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-tennessee-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-tennessee-code -- npx -y @pipeworx/mcp-tennessee-code
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-tennessee-code": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-tennessee-code --command npx --arg -y --arg @pipeworx/mcp-tennessee-code
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-tennessee-code:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-tennessee-code"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-tennessee-code": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-tennessee-code -t stdio -c npx -a -y @pipeworx/mcp-tennessee-code
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-tennessee-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 78, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `tn_statute` (~418 tokens)

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.

Input parameters:

- `citation` (string, required): 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.

### `tn_search` (~183 tokens)

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.

Input parameters:

- `limit` (number): Max results, default 10, max 50.
- `query` (string, required): Topic or keywords, e.g. "security deposit".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Tennessee Code MCP server?

VerifyMCP ran 15 checks on Tennessee 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 Tennessee Code: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-tennessee-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-tennessee-code
- Repository: https://github.com/pipeworx-io/mcp-tennessee-code
- Website: https://pipeworx.io/packs/tennessee-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-tennessee-code/pipeworx-mcp-tennessee-code