# GroundRules - US Law Text (remote · law.agentlookups.ai)

The original text of US federal and state law, with official sources; never a summary or advice.

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `law.agentlookups.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-agentlookups-groundrules/law.md), [page](https://verifymcp.io/servers/ai-agentlookups-groundrules/law)

## Channel facts

- Endpoint: `https://law.agentlookups.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-05.

- **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**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 762 tokens (~190/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the GroundRules - US Law Text MCP server?

GroundRules - US Law Text is a hosted endpoint at https://law.agentlookups.ai/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 ai-agentlookups-groundrules 'https://law.agentlookups.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-agentlookups-groundrules": {
      "url": "https://law.agentlookups.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-agentlookups-groundrules": {
      "type": "http",
      "url": "https://law.agentlookups.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-agentlookups-groundrules]
url = "https://law.agentlookups.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-agentlookups-groundrules": {
      "type": "remote",
      "url": "https://law.agentlookups.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-agentlookups-groundrules --url 'https://law.agentlookups.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-agentlookups-groundrules:
    url: "https://law.agentlookups.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-agentlookups-groundrules": {
      "Transport": "http",
      "Url": "https://law.agentlookups.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-agentlookups-groundrules -t streamable-http -u 'https://law.agentlookups.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-agentlookups-groundrules": {
      "type": "http",
      "url": "https://law.agentlookups.ai/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-11-05 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 74, +1)

- [security] Tool “law_search” rewrote its description, which is the text the model reads

### 2026-10-26 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (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.

## MCP tools (4)

### `law_for_location` (~116 tokens)

Find the law that applies at a location

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.

Input parameters:

- `address` (string): One-line street address
- `lat` (number)
- `lon` (number)

### `law_search` (~343 tokens)

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. meaning_only:true means no section matched a word of the query, so every hit is only the nearest in meaning and may be unrelated. Requested ids we do not host are named in the response note; law_coverage lists what is hosted.

Input parameters:

- `address` (string): One-line street address to auto-scope the search; pass this or jurisdictions, not both
- `include_text` (integer): Include full text for up to this many top results (0 by default; sections over 64KB require get).
- `jurisdictions` (string): Comma-separated jurisdiction or source ids from law_coverage, e.g. us,us-tx (us-cfr = CFR only)
- `limit` (integer)
- `mode` (string): auto combines word and semantic retrieval when available; keyword avoids model inference.
- `offset` (integer)
- `q` (string, required): Topic, question, or citation
- `sources` (string): Exact comma-separated source IDs; us = US Code only here. Use instead of jurisdictions/address.

### `law_get_section` (~139 tokens)

Get the full text of a law section

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.

Input parameters:

- `citation` (string): Full citation, e.g. California Civil Code 1950.5
- `id` (string): Section id returned by search
- `references` (array): Batch of section ids or complete citations

### `law_coverage` (~78 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-agentlookups-groundrules/law#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 66
- 2026-10-10: 0

## Common questions

### What is the GroundRules - US Law Text MCP server?

GroundRules - US Law Text is an MCP server listed in the public MCP registry as ai.agentlookups/groundrules. The original text of US federal and state law, with official sources; never a summary or advice. This page covers its hosted endpoint (https://law.agentlookups.ai/mcp).

### Is the GroundRules - US Law Text MCP server safe to use?

GroundRules - US Law Text scores 78 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 GroundRules - US Law Text MCP server expose?

GroundRules - US Law Text exposes 4 tools: law_for_location, law_search, law_get_section, law_coverage. Their descriptions and schemas cost roughly 676 tokens of context every time the server is loaded.

### Does the GroundRules - US Law Text MCP server require authentication?

No. We connected to GroundRules - US Law Text without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GroundRules - US Law Text MCP server still maintained?

GroundRules - US Law Text is still listed as active in the MCP registry. We last reached this channel on 5 November 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://law.agentlookups.ai/mcp
- Website: https://law.agentlookups.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-agentlookups-groundrules/law.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-agentlookups-groundrules/law.json
- HTML version of this page: https://verifymcp.io/servers/ai-agentlookups-groundrules/law