Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
NC General Statutes is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search North Carolina's General Statutes, read any section by citation, track how it changed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nc-general-statutes-mcp https://mcp.ncstatutes.com/mcp
# 2 — ask your agent for something these tools do
# search_statutes, get_statute, pending_changes and 5 more
NC General Statutes costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NCAll 1 server
ncstatutes1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nc-general-statutes-mcp https://mcp.ncstatutes.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search North Carolina (NC) statutes by topic, keyword or phrase. Use this when you know the SUBJECT but not the citation — "what's the NC law about leaving a dog in a hot car", "failure to appear penalty", "when can I expunge a misdemeanor". If you already have a citation, use get_statute instead. Returns ranked sections with highlighted fragments showing why each matched, not full text: pick th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Topic, keyword or phrase. Supports quoted "exact phrases", -excluded terms and or. Court shorthand (FTA, DWLR, PJC) is expanded for you. |
| chapter | no | — | |
| limit | integer | no | — |
| include_repealed | boolean | no | — |
Full text of one North Carolina (NC) General Statutes section, by citation. Use for "what does G.S. 14-72.1 say". Accepts any spelling — "14-72.1", "G.S. 14-72.1", "§ 14-72.1". Returns catchline, body, history note, and when it was first enacted and last amended. as_of gives the text observed on a past date; pending lists variants enacted but not yet effective. Carries codified_through, `s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | One NC General Statutes SECTION. Any spelling works; subsections do not — ask for 20-141, not 20-141(j1). |
| as_of | no | — | |
| pending | boolean | no | — |
| max_chars | integer | no | — |
North Carolina (NC) statute text already enacted but not yet effective. Use for "what changes to Chapter 14 are coming". Returns each section's current text alongside the future variant, its effective date, and by default a diff of the two. Distinguishes an AMENDMENT (current text exists) from a NEW SECTION (nothing in force yet, so no diff). Only counts variants dated in the future. For text in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chapter | no | — | |
| citation | no | — | |
| include_diff | boolean | no | — |
| limit | integer | no | — |
When a North Carolina (NC) statute section was enacted and every time it was amended. Use for "how often has G.S. 14-33 changed" or "when was this last amended". Returns one entry per session law mined from the section's own history note, grouped by year, plus first-enacted year and total amendment count. Each amendment is listed once even when the section has several versions; an entry marked `n
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | The section whose amendment record you want. |
Word-level diff of a North Carolina (NC) statute section between two versions. mode="pending" compares the text in force against an enacted-but-not-yet-effective variant — use this for "what will change on 1 October". mode="observed" compares versions this database has actually recorded, optionally between two dates. CANNOT show text from before the ingest's first observation: observed histo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | The section to diff. Add mode="pending" to compare today's text against an enacted-but-not-yet-effective version. |
| from_date | no | — | |
| to_date | no | — | |
| mode | string | no | — |
| format | string | no | — |
Changed North Carolina (NC) statutes, by effective date, observation or session year. source="effective" answers "what took effect on 1 October" from ncleg's own effective dates — use it for that, and bound a single day with since=until. It looks FORWARD too, so it also answers "what takes effect next quarter". source="statutory" is the legislature's record from history notes, back to the 1800s,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | yes | Start of the window: a session year or an ISO date. Pair with until and source="effective" to ask about a single day. | |
| until | no | — | |
| chapter | no | — | |
| source | string | no | — |
| include_baseline | boolean | no | — |
| limit | integer | no | — |
How much legislative churn a North Carolina (NC) statute chapter has seen. Use for "which parts of Chapter 14 keep changing". Returns amendment counts by year, the most-amended sections with their totals, and counts of pending and repealed sections. Omit chapter for a corpus-wide view. Counts are STATUTORY, from history notes — not observations. For one section use amendment_history; for upcom
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chapter | no | — | |
| since_year | no | — | |
| top | integer | no | — |
Which North Carolina (NC) statutes this section cites, and which cite it. Use for "what does G.S. 14-72.1 depend on" or "what else references it". OUTBOUND is what the section's own text cites; INBOUND is every section citing it — the direction you cannot get by reading one statute. Section-level only: a reference to 20-141(j1) is an edge to 20-141. Chapter-wide and "this Article" references are
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | The section whose references you want, in either direction. |
| direction | string | no | — |
| limit | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NC General Statutes or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish NC General Statutes can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.