A remote MCP server that gives an assistant verbatim US federal and state law text, resolved by address, topic, or citation, with official source provenance.
What you can do
Resolve an address or coordinates to the full jurisdiction stack (federal, state, county, place) and its code sources, including unincorporated areas that fall back to county code only. Search original law by topic, question, or exact citation, scoped by jurisdiction, source ids, or an address. Fetch full verbatim section text by id or citation, in batches of up to 10, with provenance, parent path, and neighboring sections. Check per-source coverage: what is hosted, section counts, currency or vintage, last verification, and stale flags.
When to use it
Useful when an assistant needs to quote or check the actual text of US law rather than a summary, for example to answer a question about a specific statute, confirm a citation, or find which codes apply to a given address.
Requirements
A remote streamable HTTP endpoint; no package, account, API key, or environment variable is declared. Network access to the provider's endpoint is needed.
Before you install
The server returns law text, not legal advice or interpretation. Coverage is partial: some jurisdictions and roughly half of US municipalities publish no code, and absence from the coverage list means the text is not hosted. Some sources may be flagged stale, so check currency before relying on a section.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.agentlookups%2Fgroundrules/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Resolve an address or lat/lon to its full jurisdiction stack: federal, state, county, place, each with its code sources (name, publisher, official URL, current-through, whether we host its text). Unincorporated areas get the county code with no city code; about half of US municipalities publish no code online, and the answer says so and points at where the code lives if anywhere.
Parameterslatlonaddress
law_search
Search the text of the law
Search original law by topic, question, or citation. Exact citations resolve directly. Scoped by jurisdiction or source ids (e.g. us, us-tx; us-cfr scopes to the CFR alone, us covers both the US Code and the CFR) or by an address (the address is resolved first, then the search covers exactly its stack's hosted sources). Results are verbatim snippets with citation, official source URL, retrieval time, and a current-through or vintage label adjacent to every snippet; a hit whose source has fallen behind its upstream carries stale:true. Vintage-labeled text is a dated snapshot, not current law. Requested ids we do not host are named in the response note; law_coverage lists what is hosted.
Fetch full verbatim text by id or citation, or pass references for a batch of up to 10. Each batch item has its own result/error. Includes provenance (official source URL, current-through or vintage label, retrieval time), parent path, and prev/next siblings. The text is reproduced exactly as published by the official source; nothing is added or removed except publisher editorial matter, which we never carry.
Parametersidcitationreferences
law_coverage
List the law sources we host
Per-source coverage: what we host, section counts, current-through or vintage, last_verified, and a stale flag for any source the recurring verify has proven behind its upstream. Machine-generated from the build manifest; never hand-typed. Absence from this list means we do not host that jurisdiction's text, not that no law exists there.
Takes no parameters.
Version history
1
v1.0.0LatestOct 9, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.