# NC General Statutes (remote · mcp.ncstatutes.com) Search North Carolina's General Statutes, read any section by citation, track how it changed. - Trust score: 71/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-23 ## Components - remote · `mcp.ncstatutes.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-ncstatutes-ncgs/mcp.md), [page](https://verifymcp.io/servers/com-ncstatutes-ncgs/mcp) ## Channel facts - Endpoint: `https://mcp.ncstatutes.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.2` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-23. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 60/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 2275 tokens (~284/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 33/100 - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 77/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 20% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the NC General Statutes MCP server? NC General Statutes is a hosted endpoint at https://mcp.ncstatutes.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http com-ncstatutes-ncgs 'https://mcp.ncstatutes.com/mcp' ``` ### Cursor ```json { "mcpServers": { "com-ncstatutes-ncgs": { "url": "https://mcp.ncstatutes.com/mcp" } } } ``` ### VS Code ```json { "servers": { "com-ncstatutes-ncgs": { "type": "http", "url": "https://mcp.ncstatutes.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-ncstatutes-ncgs] url = "https://mcp.ncstatutes.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-ncstatutes-ncgs": { "type": "remote", "url": "https://mcp.ncstatutes.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-ncstatutes-ncgs --url 'https://mcp.ncstatutes.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-ncstatutes-ncgs: url: "https://mcp.ncstatutes.com/mcp" ``` ### Netclaw ```json { "McpServers": { "com-ncstatutes-ncgs": { "Transport": "http", "Url": "https://mcp.ncstatutes.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-ncstatutes-ncgs -t streamable-http -u 'https://mcp.ncstatutes.com/mcp' ``` ### Other ```json { "mcpServers": { "com-ncstatutes-ncgs": { "type": "http", "url": "https://mcp.ncstatutes.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-22 (score 71, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-20 (score 70, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-18 (score 69, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-17 (score 68, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “get_statute” rewrote its description, which is the text the model reads - [security] Tool “search_statutes” rewrote its description, which is the text the model reads - [functional regression] Schema quality: 253 → 284 - [functional] Schema quality: good → excellent - [cosmetic] “get_statute” reworded the description of “citation” ### 2026-10-16 (score 68, 0) - [security] Tool “search_statutes” rewrote its description, which is the text the model reads - [functional] Schema quality: excellent → good ### 2026-10-15 (score 68, +1) - [security] Tool “amendment_history” rewrote its description, which is the text the model reads - [functional] Schema quality: good → excellent ### 2026-10-14 (score 67, 0) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-13 (score 67) First indexed and scored. ## MCP tools (8) ### `search_statutes` (~444 tokens) Search North Carolina (NC) statutes by topic or keyword 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. Input parameters: - `chapter` - `include_repealed` (boolean) - `limit` (integer) - `query` (string, required): Topic, keyword or phrase. Supports quoted "exact phrases", -excluded terms and `or`. Court shorthand (FTA, DWLR, PJC) is expanded for you. ### `get_statute` (~541 tokens) Read a North Carolina (NC) General Statutes section 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. Input parameters: - `as_of` - `citation` (string, required): 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(… - `max_chars` (integer) - `pending` (boolean) ### `pending_changes` (~145 tokens) North Carolina (NC) statute changes enacted but not yet effective 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 parameters: - `chapter` - `citation` - `include_diff` (boolean) - `limit` (integer) ### `amendment_history` (~178 tokens) When a North Carolina (NC) statute was enacted and amended 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. Input parameters: - `citation` (string, required): The section whose amendment record you want. ### `diff_statute` (~181 tokens) Diff two versions of a North Carolina (NC) 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. Input parameters: - `citation` (string, required): The section to diff. Add mode="pending" to compare today's text against an enacted-but-not-yet-effective version. - `format` (string) - `from_date` - `mode` (string) - `to_date` ### `recent_law_changes` (~225 tokens) Recently changed North Carolina (NC) statutes 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 parameters: - `chapter` - `include_baseline` (boolean) - `limit` (integer) - `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. - `source` (string) - `until` ### `chapter_activity` (~119 tokens) Legislative activity across a North Carolina (NC) statute chapter 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 parameters: - `chapter` - `since_year` - `top` (integer) ### `cross_references` (~156 tokens) What a North Carolina (NC) statute cites, and what cites it 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 parameters: - `citation` (string, required): The section whose references you want, in either direction. - `direction` (string) - `limit` (integer) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ncstatutes-ncgs/mcp#diagnostics ## Score history - 2026-10-23: 71 - 2026-10-22: 71 - 2026-10-21: 70 - 2026-10-20: 70 - 2026-10-19: 69 - 2026-10-18: 69 - 2026-10-17: 68 - 2026-10-16: 68 - 2026-10-15: 68 - 2026-10-14: 67 - 2026-10-13: 67 ## Common questions ### What is the NC General Statutes MCP server? NC General Statutes is an MCP server listed in the public MCP registry as com.ncstatutes/ncgs. Search North Carolina's General Statutes, read any section by citation, track how it changed. This page covers its hosted endpoint (https://mcp.ncstatutes.com/mcp). ### Is the NC General Statutes MCP server safe to use? NC General Statutes scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the NC General Statutes MCP server expose? NC General Statutes exposes 8 tools: search_statutes, get_statute, pending_changes, amendment_history, diff_statute, and 3 more. Their descriptions and schemas cost roughly 1,989 tokens of context every time the server is loaded. ### Does the NC General Statutes MCP server require authentication? No. We connected to NC General Statutes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the NC General Statutes MCP server still maintained? NC General Statutes is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://mcp.ncstatutes.com/mcp - Website: https://ncstatutes.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-ncstatutes-ncgs/mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/com-ncstatutes-ncgs/mcp.json - HTML version of this page: https://verifymcp.io/servers/com-ncstatutes-ncgs/mcp