All servers · Research & knowledge · Government & law
NC General Statutes
com.ncstatutes/ncgs · v1.0.2
Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | experimental, extensions, logging, prompts, resources, tools |
| Tool definitions | 8 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Search North Carolina's General Statutes, read any section by citation, track how it changed.
Connect
streamable-http · https://mcp.ncstatutes.com/mcp
claude mcp add --transport http ncgs https://mcp.ncstatutes.com/mcp{
"mcpServers": {
"ncgs": {
"url": "https://mcp.ncstatutes.com/mcp"
}
}
}Tools as reported by the server
search_statutesSearch 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. Rget_statuteFull 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 apending_changesNorth 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 NEWamendment_historyWhen 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 amendmentdiff_statuteWord-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, optionarecent_law_changesChanged 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 nechapter_activityHow 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 arecross_referencesWhich 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 on
Tool changes
- 2026-10-17: search_statutes, get_statute, pending_changes, amendment_history, diff_statute, recent_law_changes, chapter_activity, cross_references
- 2026-10-16: search_statutes, get_statute, pending_changes, amendment_history, diff_statute, recent_law_changes, chapter_activity, cross_references
Website · JSON · Text for agents · Registry updated 2026-10-13