NC General Statutes
Search North Carolina's General Statutes, read any section by citation, track how it changed.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"ncgs": {
"url": "https://mcp.ncstatutes.com/mcp"
}
}
}Remote endpoints
https://mcp.ncstatutes.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (8)
🟢search_statutes(query, chapter, limit, include_repealed)
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 the one you want and call get_statute for it. Supports quoted "exact phrases", -excluded terms and `or`. Court shorthand is expanded automatically and case-insensitively — FTA, DWLR, PJC, AWDW and similar become the statutory wording, because the statute book spells the phrase out and never uses the abbreviation. The expansion is reported back as `expanded_query`. Searches the law in force today, at section level. A low top rank means the corpus probably has no section on point — NC simply has no statute on some subjects, and saying so is a better answer than the nearest loose word match.
Input Schema
{
"type": "object",
"properties": {
"query": {
"description": "Topic, keyword or phrase. Supports quoted \"exact phrases\", -excluded terms and `or`. Court shorthand (FTA, DWLR, PJC) is expanded for you.",
"examples": [
"dog fighting",
"failure to appear penalty",
"\"breaking or entering\""
],
"type": "string"
},
"chapter": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"limit": {
"default": 10,
"type": "integer"
},
"include_repealed": {
"default": false,
"type": "boolean"
}
},
"required": [
"query"
],
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢get_statute(citation, as_of, pending, max_chars)
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`, `session_laws_through` and a `legislation_note` naming any enacted act that touches this section outside the codified text. An uncodified override ("Notwithstanding G.S. ...") is never codified, so it is reported regardless of the watermark. PENDING BILLS ARE NOT COVERED — a ratified bill is not law and appears in neither source, so an empty note is not evidence nothing passed. `as_of` RESOLVES AGAINST OBSERVED VERSIONS, NOT EFFECTIVE DATES — it answers "what did this database hold on that date", so it cannot reach text from before the first ingest run. For "what took effect on 1 October" use recent_law_changes(source="effective"). Section-level only — ask for "20-141", not "20-141(j1)". For WHEN it changed use amendment_history; for WHAT changed use diff_statute.
Input Schema
{
"type": "object",
"properties": {
"citation": {
"description": "One NC General Statutes SECTION. Any spelling works; subsections do not — ask for 20-141, not 20-141(j1).",
"examples": [
"14-72.1",
"G.S. 14-72.1",
"§ 14-72.1",
"15A-145.5"
],
"type": "string"
},
"as_of": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"pending": {
"default": false,
"type": "boolean"
},
"max_chars": {
"default": 12000,
"type": "integer"
}
},
"required": [
"citation"
],
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢pending_changes(chapter, citation, include_diff, limit)
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 force now use get_statute; for already-enacted history use amendment_history or recent_law_changes.
Input Schema
{
"type": "object",
"properties": {
"chapter": {
"anyOf": [
{
"type": "string"
},
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null
},
"citation": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"include_diff": {
"default": true,
"type": "boolean"
},
"limit": {
"default": 50,
"type": "integer"
}
},
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢amendment_history(citation)
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. These are STATUTORY dates from the legislature's record — not when this database saw the text change. For that use recent_law_changes; for the wording itself use get_statute or diff_statute.
Input Schema
{
"type": "object",
"properties": {
"citation": {
"description": "The section whose amendment record you want.",
"examples": [
"14-33",
"G.S. 20-141"
],
"type": "string"
}
},
"required": [
"citation"
],
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢diff_statute(citation, from_date, to_date, mode, format)
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 history begins then, so most sections have only one version and return diff: null. For earlier change dates use amendment_history; for pending text use pending_changes.
Input Schema
{
"type": "object",
"properties": {
"citation": {
"description": "The section to diff. Add mode=\"pending\" to compare today's text against an enacted-but-not-yet-effective version.",
"examples": [
"14-78",
"G.S. 14-33"
],
"type": "string"
},
"from_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"to_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"mode": {
"default": "observed",
"type": "string"
},
"format": {
"default": "unified",
"type": "string"
}
},
"required": [
"citation"
],
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢recent_law_changes(since, until, chapter, source, include_baseline, ...)
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, dated by year. source="observed" is only when this database saw text change — ncleg's publishing schedule, not the law's, and no substitute for effective dates. "both" returns statutory + observed. For one section use amendment_history.
Input Schema
{
"type": "object",
"properties": {
"since": {
"anyOf": [
{
"type": "string"
},
{
"type": "integer"
}
],
"description": "Start of the window: a session year or an ISO date. Pair with `until` and source=\"effective\" to ask about a single day.",
"examples": [
2025,
"2026-10-01"
]
},
"until": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"chapter": {
"anyOf": [
{
"type": "string"
},
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null
},
"source": {
"default": "both",
"type": "string"
},
"include_baseline": {
"default": false,
"type": "boolean"
},
"limit": {
"default": 100,
"type": "integer"
}
},
"required": [
"since"
],
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢chapter_activity(chapter, since_year, top)
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 upcoming text use pending_changes.
Input Schema
{
"type": "object",
"properties": {
"chapter": {
"anyOf": [
{
"type": "string"
},
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null
},
"since_year": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null
},
"top": {
"default": 20,
"type": "integer"
}
},
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}🟢cross_references(citation, direction, limit)
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 not edges. For the text itself use get_statute.
Input Schema
{
"type": "object",
"properties": {
"citation": {
"description": "The section whose references you want, in either direction.",
"examples": [
"15A-145.5",
"G.S. 1A-1"
],
"type": "string"
},
"direction": {
"default": "both",
"type": "string"
},
"limit": {
"default": 100,
"type": "integer"
}
},
"required": [
"citation"
],
"additionalProperties": false
}Output Schema
{
"type": "object",
"additionalProperties": true
}Community
Evidence