Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
GroundRules - US Law Text is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
4
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
The original text of US federal and state law, with official sources; never a summary or advice.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http groundrules-us-law-text-mcp https://law.agentlookups.ai/mcp
# 2 — ask your agent for something these tools do
# law_for_location, law_search, law_get_section and 1 more
GroundRules - US Law Text costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AGAll 7 servers
agentlookups7 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http groundrules-us-law-text-mcp https://law.agentlookups.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | One-line street address |
| lat | number | no | — |
| lon | number | no | — |
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 ti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | One-line street address to auto-scope the search; pass this or jurisdictions, not both |
| include_text | integer | no | Include full text for up to this many top results (0 by default; sections over 64KB require get). |
| jurisdictions | string | no | Comma-separated jurisdiction or source ids from law_coverage, e.g. us,us-tx (us-cfr = CFR only) |
| limit | integer | no | — |
| mode | string | no | auto combines word and semantic retrieval when available; keyword avoids model inference. |
| offset | integer | no | — |
| q | string | yes | Topic, question, or citation |
| sources | string | no | Exact comma-separated source IDs; us = US Code only here. Use instead of jurisdictions/address. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | no | Full citation, e.g. California Civil Code 1950.5 |
| id | string | no | Section id returned by search |
| references | array | no | Batch of section ids or complete citations |
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GroundRules - US Law Text or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish GroundRules - US Law Text can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.