mcpbeat Sign in

NC General Statutes MCP Server

by ncstatutes Your server? Claim it
answering

NC General Statutes is answering right now. Last checked 1 min ago. It exposes 8 tools.

Search North Carolina's General Statutes, read any section by citation, track how it changed.

Uptime history 70 hours of history
70 hours agonow
100.0%
Uptime 24h
92 of 92 checks
8
Tools
read from the server
392 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

16 Oct 4 tools changed the parameters they ask for amendment_history, cross_references, diff_statute and 1 more
16 Oct 2 tool descriptions were rewritten get_statute, search_statutes
15 Oct a tool description was rewritten search_statutes
14 Oct a tool description was rewritten amendment_history

Nothing serious here today

Today is the operative word: we check NC General Statutes every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add ncgs --transport http https://mcp.ncstatutes.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ncgs": {
      "url": "https://mcp.ncstatutes.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ncgs]
url = "https://mcp.ncstatutes.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ncgs": {
      "url": "https://mcp.ncstatutes.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ncgs": {
      "url": "https://mcp.ncstatutes.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

amendment
amendment_history
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 `not_yet_in_force` is an enacted law whose version of the text has not taken effect yet. 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.
chapter
chapter_activity
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.
cross
cross_references
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.
diff
diff_statute
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.
pending
pending_changes
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.
recent
recent_law_changes
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.
statute
get_statute
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)". The Rules of Evidence and of Civil Procedure are each one statute (G.S. 8C-1, G.S. 1A-1) holding many rules; ask for a rule as "8C-1, Rule 104" or "1A-1, Rule 12" (N.C. R. Evid. / N.C. R. Civ. P. forms work). Asking for 8C-1 or 1A-1 itself lists the rules. For WHEN it changed use amendment_history; for WHAT changed use diff_statute.
statutes
search_statutes
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`. `match_mode` says how the query was read: "all_terms" (every word), "any_of" (the query used `or`), "any_terms" (nothing matched every word, so any word was accepted) or "citation" (the query was a bare citation, so it was looked up directly; when the section doesn't exist, the nearest real sections by number come back as `suggestions`). The loose modes only return sections that contain at least one of your words. Results are ordered by `terms_matched` — how many of the search words a section contains, a quoted phrase counting only when it appears as a phrase — then by rank. 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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.ncstatutes.com/mcp streamable-http answering 199 ms 1 min ago

Alternatives to NC General Statutes

same job, measured the same way
North Carolina Code
by pipeworx-io

North Carolina General Statutes — state statutes by citation, plus topic search.

42 tools answering
Connecticut Code
by pipeworx-io

Connecticut General Statutes — state statutes by citation.

42 tools answering
Uk Legislation MCP Server
by cyanheads

Search and read UK legislation at any date, resolve citations, list amendments, track changes.

269 installs/wk 6 tools answering
Alaska Code
by pipeworx-io

Alaska Statutes — statute text by citation and chapter-catchline search.

42 tools answering
Rhode Island Code
by pipeworx-io

Rhode Island General Laws — state statutes by citation.

42 tools answering
Texas Ag Opinions
by pipeworx-io

Texas Attorney General opinions — statute-citation search over recorded

44 tools answering
South Carolina Code
by pipeworx-io

South Carolina Code of Laws — state statutes by citation.

37 tools answering
US Code Federal Statutes
by ecfr

Search and read U.S. Code statutes with legal and inline citations linking to uscode.ecfr.io.

answering

NC General Statutes — questions

Answers built from our own checks of this server.

What can NC General Statutes do?
It exposes 8 tools, read directly from the server on our last check. Among them: amendment_history, chapter_activity, cross_references, diff_statute, get_statute, pending_changes and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is NC General Statutes working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 392 ms. The bar chart above shows every period we have measured.
How do I connect NC General Statutes?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does NC General Statutes need an API key?
No. NC General Statutes completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is NC General Statutes?
It answers our handshake in 392 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.