NC General Statutes

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "NC General Statutes": {
      "url": "https://mcp.ncstatutes.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• search_statutes read-only

  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.

  Parameters:

  • query (required) — string — Topic, keyword or phrase. Supports quoted "exact phrases", -excluded terms and `or`. Court shorthand (FTA, DWLR, PJC) is expanded for you.
  • limit — integer
  • chapter
  • include_repealed — boolean

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_statute read-only

  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.

  Parameters:

  • citation (required) — string — One NC General Statutes SECTION, or one rule of the Rules of Evidence or Civil Procedure ("8C-1, Rule 104", "N.C. R. Civ. P. 12"). Any spelling works; subsections do not — ask for 20-141, not 20-141(j1), and 1A-1, Rule 12, not Rule 12(b)(6).
  • as_of
  • pending — boolean
  • max_chars — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• pending_changes read-only

  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.

  Parameters:

  • limit — integer
  • chapter
  • citation
  • include_diff — boolean

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• amendment_history read-only

  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.

  Parameters:

  • citation (required) — string — The section whose amendment record you want.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• diff_statute read-only

  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.

  Parameters:

  • citation (required) — string — The section to diff. Add mode="pending" to compare today's text against an enacted-but-not-yet-effective version.
  • mode — string
  • format — string
  • to_date
  • from_date

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• recent_law_changes read-only

  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.

  Parameters:

  • since (required) — Start of the window: a session year or an ISO date. Pair with `until` and source="effective" to ask about a single day.
  • limit — integer
  • until
  • source — string
  • chapter
  • include_baseline — boolean

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• chapter_activity read-only

  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.

  Parameters:

  • top — integer
  • chapter
  • since_year

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• cross_references read-only

  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.

  Parameters:

  • citation (required) — string — The section whose references you want, in either direction.
  • limit — integer
  • direction — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.