NC General Statutes MCP server
com.ncstatutes/ncgsncstatutes.comstreamable-httpv1.3.0Scanned
NC statutes, session laws, Constitution, court rules and agency rules: search, read, see changes.
15 tools: 6 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the NC General Statutes MCP server can do
The NC General Statutes MCP server is published by ncstatutes.com, a domain the MCP Registry verified. It has 15 tools. It can create or change data (6 tools: pending_changes, amendment_history, recent_law_changes, chapter_activity and 2 more), but cannot delete data. 9 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Changes things 6Claude Code: ask
amendment_historyWhen a North Carolina (NC) statute section was enacted and every time it was amended.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: When a North Carolina (NC) statute was enacted and amended
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
chapter_activityHow much legislative churn a North Carolina (NC) statute chapter has seen.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Legislative activity across a North Carolina (NC) statute chapter
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
cross_referencesWhich North Carolina (NC) statutes this section cites, which cite it, and which agency rules implement it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Which North Carolina (NC) statutes this section cites, which cite it, and which agency rules implement it. Use for "what does G.S. 14-72.1 depend on", "what else references it", or "what rules were adopted under G.S. 150B-21.2". OUTBOUND is what the section's own text cites; INBOUND is every section citing it — the direction you cannot get by reading one statute — plus `implementing_rules`: NC Administrative Code rules that cite it as their authority. 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.
Annotations the server declares
- title: What a North Carolina (NC) statute cites, what cites it, and its rules
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pending_changesNorth Carolina (NC) statute text already enacted but not yet effective.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: North Carolina (NC) statute changes enacted but not yet effective
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
recent_law_changesChanged North Carolina (NC) statutes, by effective date, observation or session year.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Recently changed North Carolina (NC) statutes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
rule_historyWhen a North Carolina Administrative Code (NCAC) rule was adopted, amended or repealed, and exactly what changed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it When a North Carolina Administrative Code (NCAC) rule was adopted, amended or repealed, and exactly what changed. Returns OAH's history events (dated: adopted, amended, temporary or emergency adoption, readopted, repealed, expired, transferred, recodified) and the versions of the text this server has stored, with a word-level diff between two of them — the latest two by default, or the versions in force on `from_date` and `to_date` (YYYY-MM-DD). `format` is "unified", "html" or "both". Stored versions begin with the first weekly crawl, so older changes have dates but no diff.
Annotations the server declares
- title: When a North Carolina (NC) Administrative Code rule changed, and how
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
diff_statuteWord-level diff of a North Carolina (NC) statute section between two versions.No findings
Why it is in this group
- The name "diff_statute" says "diff": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Diff two versions of a North Carolina (NC) statute
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_constitutionThe North Carolina (NC) Constitution — read a section by citation, list an article, or search it by topic.No findings
Why it is in this group
- The name "get_constitution" says "get": a word for reading.
Description, as the server wrote it The North Carolina (NC) Constitution — read a section by citation, list an article, or search it by topic. Use for "what does the NC Constitution say about ..." and for any "N.C. Const." citation. Give `citation` ("N.C. Const. art. I, § 20", "Article I, Section 20", "Art. IX, sec. 2", "Section 20 of Article I") or `article` + `section`; an article alone ("Article IV") lists its sections. Give `query` instead to search the text by topic. A section returns its heading, text, the statutes that cite it, and when ncleg's text last changed. Amendments awaiting a referendum are printed by ncleg as two versions — "(Effective until contingency met)" and "(Effective once contingency met)" — and come back as `variants`, the one in force first, with ncleg's note on the contingency. This is ncleg's online text, not an official certified copy, and it carries no amendment history: stored versions begin with the first crawl. For the U.S. Constitution this server has nothing; for statutes use get_statute.
Annotations the server declares
- title: Read or search the North Carolina (NC) Constitution
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_court_ruleNorth Carolina (NC) court rules that are NOT in the General Statutes: the Rules of Appellate Procedure, the General Rules of Practice for the Superior and District Courts, and the …No findings
Why it is in this group
- The name "get_court_rule" says "get": a word for reading.
Description, as the server wrote it North Carolina (NC) court rules that are NOT in the General Statutes: the Rules of Appellate Procedure, the General Rules of Practice for the Superior and District Courts, and the Business Court Rules. Give `citation` in any common form — "N.C. R. App. P. 30(e)", "App. R. 30", "Appellate Rule 28(b)(6)", "Rule 2 of the General Rules of Practice", "BCR 7.2", "Business Court Rule 7.2" — or `rule_set` + `rule`. A pinpoint returns that subdivision's text (`pinpoint`) alongside the whole rule. `rule_set` alone lists its rules; `query` searches by topic. The Rules of Civil Procedure and of Evidence are General Statutes (G.S. 1A-1, 8C-1): use get_statute("1A-1, Rule 12"). The Rules of Professional Conduct are NC Administrative Code (27 NCAC 02): use get_rule. Local rules are not covered. Versions are dated by codification, not by each amendment's effective date; the Appellate Rules go back to the January 2019 codification.
Annotations the server declares
- title: North Carolina (NC) appellate, practice and Business Court rules
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_definitionWhat a term means in the North Carolina (NC) General Statutes — the statutory definition, and where it applies.No findings
Why it is in this group
- The name "get_definition" says "get": a word for reading.
Description, as the server wrote it What a term means in the North Carolina (NC) General Statutes — the statutory definition, and where it applies. Use whenever a statute's outcome turns on a word that may be DEFINED rather than plain English ("motor vehicle", "impairing substance", "person", "dwelling"). With `section`, returns only the definitions whose scope covers that section, most specific first (section > listed sections > Subpart > Part > Subchapter > Article > Chapter > statewide rules of construction in G.S. 12-3), each with `why` it applies. Without `section`, returns every definition of the term grouped by scope — which differ: "board" means a different body in each chapter that defines it. Matching: the exact term first, then case and plural folded, then the term inside a longer defined phrase (flagged `fuzzy`). A definition that only says "has the meaning in G.S. X" is resolved one step to that section's definition. Definitions are extracted automatically from the statute text; some lead-ins ("As used in this act") cannot be tied to a scope and are reported as such, never guessed. Read the defining section before relying on a definition. get_statute(include_definitions= True) lists every defined term a section uses.
Annotations the server declares
- title: What a term means in North Carolina (NC) statutes, where it applies
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_ruleRead a North Carolina Administrative Code (NCAC) rule — a state agency regulation.No findings
Why it is in this group
- The name "get_rule" says "get": a word for reading.
Description, as the server wrote it Read a North Carolina Administrative Code (NCAC) rule — a state agency regulation. Returns the rule's text, heading, status (current, temporary, emergency, repealed, expired, transferred or reserved), its history (adopted, amended, …, by date), the G.S. sections it cites as AUTHORITY, and links to the rule on OAH. Give a chapter instead ("26 NCAC 03") to list that chapter's rules. Use for agency rules; use get_statute for the General Statutes the legislature passes. To find which rules implement a statute, use cross_references on the statute.
Annotations the server declares
- title: Read a North Carolina (NC) Administrative Code rule
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_session_lawThe text of North Carolina (NC) session laws — the enacted acts — by act-section.No findings
Why it is in this group
- The name "get_session_law" says "get": a word for reading.
Description, as the server wrote it The text of North Carolina (NC) session laws — the enacted acts — by act-section. Use when an answer turns on what an ACT says rather than the codified statute: "what does Sec. 5.14 of S.L. 2026-61 do", an uncodified "Notwithstanding G.S. 143-129 …" provision, an amendment to one subsection the codified text has not caught up with, or when an act takes effect. get_statute names acts touching a section; this reads them. - `session_law` alone: the act's title, effective date, the chapters it creates or repeals, and its table of contents (each act-section's number, caption and the G.S. sections it names), paged by `limit`/`offset`. - `session_law` + `section`: the full text of that act-section ("5.14" gives 5.14.(a), (b), …). - `citation` (a G.S. section), with or without `session_law`: every provision naming it, newest act first. - `query`: provisions containing all the words, in one act or across all of them. Amended text is marked as the act prints it: [-deleted-] {+inserted+}. Covers the acts of the current biennium (2025-) that ncleg has published; a bill not yet law is not here. This is the act's own text, not the codified statute — use get_statute for that.
Annotations the server declares
- title: Read a North Carolina (NC) session law, by act-section
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_statuteFull text of one North Carolina (NC) General Statutes section, by citation.No findings
Why it is in this group
- The name "get_statute" says "get": a word for reading.
Description, as the server wrote it 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"). `include_definitions=True` adds the defined terms the section uses, each with the definition that governs it here (most specific scope) — use it whenever the outcome turns on a word like "vehicle", "person" or "dwelling". get_definition looks up one term. 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.
Annotations the server declares
- title: Read a North Carolina (NC) General Statutes section
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_rulesSearch North Carolina Administrative Code (NCAC) rules — state agency regulations — by topic.No findings
Why it is in this group
- The name "search_rules" says "search": a word for reading.
Description, as the server wrote it Search North Carolina Administrative Code (NCAC) rules — state agency regulations — by topic. Use when you know the subject but not the rule: "how long to file a contested case", "child care staff ratios", "septic permit requirements". Narrow with `title` ("15A") or `chapter` ("15A NCAC 18A", or "18A" together with `title`). If you have a citation, use get_rule instead. Returns ranked rules with highlighted fragments; read one with get_rule. Results are ordered the same way as search_statutes: by how many search words a rule contains, then how much of its heading they make up, then rank. For the General Statutes the legislature passes, use search_statutes.
Annotations the server declares
- title: Search North Carolina (NC) Administrative Code rules by topic
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_statutesSearch North Carolina (NC) statutes by topic, keyword or phrase.1 finding
Why it is in this group
- The name "search_statutes" says "search": a word for reading.
Findings
- Info
The description is 2,188 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ome subjects, and saying so is a better answer than the nearest loose word match."
Description, as the server wrote it 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), "all_terms_with_synonyms" (every word, but the words as typed matched nothing or only weakly, so statutory synonyms were accepted — "car" for "motor vehicle", "leaving" for "confined"; listed in `synonyms_used`), "any_of" (the query used `or`), "any_terms" (nothing matched every word, so any word or synonym 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 `catchline_terms_matched`, how many are in the section's own heading, then by `catchline_coverage`, how much of that heading the search words make up (1.0 is an exact title, so "DWI" finds "Impaired driving" before longer sections that merely mention it), 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`. Shorthand that names one offense lists that offense's section first, marked `primary_for` (FTA → 15A-543, DWI → 20-138.1). 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.
Annotations the server declares
- title: Search North Carolina (NC) statutes by topic or keyword
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.ncstatutes.com/mcp: tools/list returned 15 tools to an anonymous client, including pending_changes (write), amendment_history (write), recent_law_changes (write), chapter_activity (write), cross_references (write) and 1 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 5 to 6
Findings
Matches of fixed checks, with the text they matched.
- Infosearch_statutes
The description is 2,188 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ome subjects, and saying so is a better answer than the nearest loose word match."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
- Tools that change things, listed without credentials: 5 to 6
Tools1 added, 12 changed.+1 added~12 changedView diff
- Added:get_session_lawOnly reads
- Changed:chapter_activityChanges thingsinputSchema
- Changed:cross_referencesChanges thingsinputSchema
- Changed:diff_statuteOnly readsinputSchema
- Changed:get_constitutionOnly readsinputSchema
- Changed:get_court_ruleOnly readsinputSchema
- Changed:get_ruleOnly readsinputSchema
- Changed:get_statuteOnly readsinputSchema
- Changed:pending_changesChanges thingsinputSchema
- Changed:recent_law_changesChanges thingsinputSchema
- Changed:rule_historyChanges thingsinputSchema
- Changed:search_rulesOnly readsinputSchema
- Changed:search_statutesOnly readsinputSchema
Tools6 added, 3 changed.+6 added~3 changedView diff
- Added:get_constitutionOnly reads
- Added:get_court_ruleOnly reads
- Added:get_definitionOnly reads
- Added:get_ruleOnly reads
- Added:rule_historyChanges things
- Added:search_rulesOnly reads
- Changed:cross_referencesChanges thingstitledescriptionannotations
- Changed:get_statuteOnly readsdescriptioninputSchema
- Changed:search_statutesOnly readsdescription
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ncgs https://mcp.ncstatutes.com/mcpclaude mcp add --transport http ncgs https://mcp.ncstatutes.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ncgs__search_statutes",
"mcp__ncgs__get_statute",
"mcp__ncgs__get_definition",
"mcp__ncgs__diff_statute",
"mcp__ncgs__search_rules",
"mcp__ncgs__get_rule",
"mcp__ncgs__get_constitution",
"mcp__ncgs__get_court_rule",
"mcp__ncgs__get_session_law"
],
"ask": [
"mcp__ncgs__pending_changes",
"mcp__ncgs__amendment_history",
"mcp__ncgs__recent_law_changes",
"mcp__ncgs__chapter_activity",
"mcp__ncgs__cross_references",
"mcp__ncgs__rule_history"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ncgs. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ncstatutes/ncgs/verify?hash=eca80c14134e0fff871bf204d759df3bfff105a2ad6d3f8f0c7a47d3b53d2aae" | jq -e '.changed == false'Pinned hash eca80c14134e, from Nov 11, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ncstatutes/ncgs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ncstatutes/ncgs)Source: MCP Registry. Synced Nov 11, 2026, 22:17 UTC.
NC General Statutes MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NC General Statutes MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NC General Statutes MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NC General Statutes MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the NC General Statutes MCP server have?
- 15 tools: 6 write, 9 read. pending_changes, amendment_history, recent_law_changes, chapter_activity, cross_references, rule_history, search_statutes, get_statute and 7 more.
Does the NC General Statutes MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NC General Statutes MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NC General Statutes MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.