Server Details
US federal and state cybersecurity/privacy law MCP server with cross-state comparison
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Ansvar-Systems/US-law-mcp
- GitHub Stars
- 0
See and control every tool call
Available Tools
8 toolsbuild_legal_stanceTry in Inspector
Build a comprehensive legal research summary for a US cybersecurity/privacy question. Searches statutes and state requirements simultaneously to aggregate relevant citations. Use this for broad legal research questions like "What are the breach notification requirements for companies operating in multiple states?" Returns statute matches, classified requirements, and metadata. For targeted single-tool queries, use the specific tools instead. To drill into a specific result, pass its short_name and jurisdiction to get_provision for full text, or use compare_requirements for cross-state analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results per category (default 5, max 20). | |
| query | Yes | Legal question or topic to research (e.g. "breach notification requirements for financial institutions", "encryption requirements across states"). | |
| jurisdictions | No | Optional. Jurisdictions to include (e.g. ["US-CA", "US-NY"]). Omit to search all. |
check_currencyTry in Inspector
Check whether a US statute is currently in force, repealed, or superseded. Returns status (in_force, amended, repealed, superseded, not_found), effective date, and last amendment date. is_current is true for both "in_force" and "amended" statuses (an amended law is still current). Use this to verify that a law is still valid before relying on it. Provide either law_identifier or short_name (required, not both).
| Name | Required | Description | Default |
|---|---|---|---|
| short_name | No | Common short name (e.g. "CFAA", "HIPAA", "CCPA/CPRA"). Use either this or law_identifier. | |
| jurisdiction | Yes | Required. Jurisdiction code (e.g. "US-FED", "US-CA"). | |
| law_identifier | No | Formal statute identifier (e.g. "18 USC 1030"). Use either this or short_name. |
compare_requirementsTry in Inspector
Compare cybersecurity/privacy legal requirements across multiple US states side by side. This is the key cross-state analysis tool — use it when comparing how different states handle the same requirement. Returns structured data including notification timelines, penalty maximums, scope, and applicability for each state. Example: compare breach notification timelines across CA, NY, TX to see that TX requires 60-day notification. Do NOT use this for single-state lookup — use get_state_requirements instead.
| Name | Required | Description | Default |
|---|---|---|---|
| category | Yes | Requirement category to compare. | |
| subcategory | No | Optional subcategory filter. For breach_notification: timeline, definition, scope, notification_target, exemptions, penalties. For privacy_rights: right_to_know, right_to_delete, right_to_opt_out, right_to_correct, right_to_portability. For cybersecurity: security_requirements, risk_assessment, incident_response, encryption, vendor_management. For sector_specific: financial, healthcare, education, insurance. | |
| jurisdictions | Yes | Array of jurisdiction codes to compare (e.g. ["US-CA", "US-NY", "US-TX"]). Use ["all"] for all states with data for this category. |
get_provisionTry in Inspector
Retrieve the full text of a specific US statute provision. Use this when you know which law you want — by short name (e.g. "CFAA", "CCPA/CPRA", "SHIELD Act") or identifier (e.g. "18 USC 1030"). Returns all provisions for the law, or a specific section if section_number is provided. Supports partial short_name matching (e.g. "CCPA" matches "CCPA/CPRA"). If no results are found, returns hints listing available laws in the jurisdiction. Do NOT use this for keyword search — use search_legislation instead.
| Name | Required | Description | Default |
|---|---|---|---|
| short_name | No | Common short name of the law (e.g. "CFAA", "CCPA/CPRA", "SHIELD Act", "HIPAA", "GLBA", "COPPA", "TX Breach"). Supports partial matching. Use either this or law_identifier. | |
| jurisdiction | Yes | Required. Jurisdiction code: "US-FED" for federal, "US-XX" for states (e.g. "US-CA", "US-NY"). Use list_sources to see available jurisdictions. | |
| law_identifier | No | Formal statute identifier (e.g. "18 USC 1030", "Cal. Civ. Code § 1798.100"). Use either this or short_name, not both. | |
| section_number | No | Specific section to retrieve (e.g. "§ 1030", "§ 1798.100", "§ 899-aa"). Omit to get all provisions of the law. Supports parent/child matching. |
get_state_requirementsTry in Inspector
Get all classified cybersecurity/privacy requirements for a single US state. Returns structured data: breach notification timelines, privacy rights, cybersecurity obligations, and sector-specific rules. Each requirement includes summary, notification days, penalty maximum, private right of action, and linked law. Use this for single-state deep dive. For multi-state comparison, use compare_requirements instead.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Filter to a specific category. Omit for all categories. | |
| jurisdiction | Yes | Required. State jurisdiction code (e.g. "US-CA", "US-NY", "US-TX"). Must be a state code, not "US-FED". |
list_sourcesTry in Inspector
List all jurisdictions available in the US Law database with document and provision counts per jurisdiction. Use this tool first when you need to discover available data or verify which states are covered. Returns jurisdiction codes (e.g. "US-FED", "US-CA"), human-readable names, and counts. Currently covers 55 jurisdictions: Federal + 50 states + DC + Guam + Puerto Rico + US Virgin Islands.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
search_legislationTry in Inspector
Full-text search across US federal and state cybersecurity/privacy statutes. Returns BM25-ranked results with highlighted snippets from 55 jurisdictions (federal + 50 states + DC + territories). Covers breach notification, data privacy, cybersecurity, and sector-specific laws. Use this tool when you need to find provisions by keyword or topic. Do NOT use this when you already know the exact law and section — use get_provision instead. Multi-word queries use AND by default with OR fallback if no results found. To get full text of a result, pass its short_name and jurisdiction to get_provision.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results to return (1-50, default 10). Lower values are faster and use fewer tokens. | |
| query | Yes | Search terms (e.g. "breach notification", "encryption personal information", "right to delete"). Supports FTS5 syntax: AND, OR, NOT, "exact phrase", prefix*. | |
| jurisdiction | No | Filter to a single jurisdiction. Format: "US-FED" for federal, "US-XX" for states (e.g. "US-CA", "US-NY", "US-TX"). Omit to search all jurisdictions. Use list_sources to see available jurisdictions. |
validate_citationTry in Inspector
Validate whether a US legal citation exists in the database. Checks short names (e.g. "CFAA", "HIPAA"), identifiers (e.g. "18 USC 1030"), and provision section numbers. Returns the matched document and provision if found. Use this as a zero-hallucination check before citing a law. Returns valid=false with match_quality="none" if the citation is not found. match_quality indicates confidence: "section_exact" (section matched directly), "section_fuzzy" (section matched via number extraction), or "document_only" (law found but specific section not confirmed — matched_provision is a representative first section).
| Name | Required | Description | Default |
|---|---|---|---|
| citation | Yes | Citation to validate. Accepts short names ("CFAA", "HIPAA"), identifiers ("18 USC 1030"), section references ("§ 1798.100"), or partial matches. | |
| jurisdiction | No | Optional jurisdiction code to narrow the search (e.g. "US-FED", "US-CA"). |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.