# guide.capitol/capitolguide (remote · capitol.guide)

Navigate the U.S. Capitol complex: decode room codes, route buildings, check access, amenities.

- Trust score: 57/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `capitol.guide`: 57/100 (this document), [markdown](https://verifymcp.io/servers/guide-capitol-capitolguide/capitol.md), [page](https://verifymcp.io/servers/guide-capitol-capitolguide/capitol)

## Channel facts

- Endpoint: `https://capitol.guide/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1088 tokens (~120/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http guide-capitol-capitolguide https://capitol.guide/mcp
```

### Codex

```toml
[mcp_servers.guide-capitol-capitolguide]
url = "https://capitol.guide/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "guide-capitol-capitolguide": {
      "type": "remote",
      "url": "https://capitol.guide/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add guide-capitol-capitolguide --url https://capitol.guide/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  guide-capitol-capitolguide:
    url: "https://capitol.guide/mcp"
```

### Other

```json
{
  "mcpServers": {
    "guide-capitol-capitolguide": {
      "type": "http",
      "url": "https://capitol.guide/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-08-03 (score 57, +1)

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

### 2026-08-01 (score 56, +1)

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

### 2026-07-31 (score 55, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 57, +1)

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

### 2026-07-28 (score 56, +1)

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

### 2026-07-27 (score 55, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (9)

### `capitolguide_prep` (~43 tokens)

Pre-flight readiness check. Run before any other tool. Verifies secrets, KV, DB connectivity, and KB version + freshness. Returns a structured readiness report.

### `overview` (~46 tokens)

Operational snapshot for the caller's tenant: KB version + freshness, queue depths (itineraries / draft meetings / active nudges), and the recent tool-invocation tail. Read-only.

### `find_room` (~146 tokens)

Find a Capitol office by ROOM CODE (e.g. 'SH-217', '2310 Rayburn', '167 Russell', 'H-232'), by MEMBER NAME (e.g. 'Cornyn', 'Ted Cruz', 'Womack'), or by COMMITTEE ('Senate Judiciary', 'Ways and Means', 'House Armed Services'). A room code returns the decoded location plus who currently holds it; a name returns that member's current office; a committee returns its office / principal hearing room. Member & committee assignments are the 119th Congress (volatile, live-source-stamped).

Input parameters:

- `query` (string, required): A room code/address, or a member's name

### `route_between` (~180 tokens)

Turn-by-turn directions between two points in the Capitol complex. Each point can be a room code, a building name, OR a Metro station / landmark (e.g. 'Capitol South Metro' → '2412 Rayburn', 'Union Station' → '517 Hart', or to the 'Supreme Court' / 'Library of Congress'). Returns an ordered step list with mode (walk/tunnel/subway), minutes, and a flag wherever you re-clear security. Set accessible=true for a step-free route (or use accessible_route).

Input parameters:

- `accessible` (boolean): Prefer a step-free / accessible route
- `from` (string, required): Origin: room code, building name, or Metro station / landmark (e.g. 'Capitol South Metro')
- `to` (string, required): Destination: room code, building name, or Metro station / landmark

### `accessible_route` (~130 tokens)

Step-free / accessible directions between two points in the Capitol complex by mobility profile (wheelchair, limited_mobility, stroller, low_vision). Routes over elevators/ramps only, avoids stairs, and surfaces OCAS accommodation contacts. Use this instead of route_between when step-free matters.

Input parameters:

- `from` (string, required): Origin: room code, building name, or Metro station / landmark (e.g. 'Union Station')
- `mobility_profile` (string): Mobility profile (default: any step-free)
- `to` (string, required): Destination: room code, building name, or Metro station / landmark

### `check_access` (~100 tokens)

What access a visitor needs for a zone of the Capitol complex: (visitor_type × zone) → allowed?, credential, escort, lead time, required docs, security entrance, and the granting authority. INFORMS, never grants — final authority is the member office / Capitol Police / Secret Service. Rules are volatile and live-source-stamped.

Input parameters:

- `visitor_type` (string, required): Who is visiting
- `zone` (string, required): Which area of the complex

### `nearby` (~103 tokens)

Nearest restroom, exit, and food for a specific point — a room code (floor-specific, e.g. the exact nearest bathroom to SH-217), a building name, or GPS coordinates {lat, lon}. Returns specific named venues ranked by distance.

Input parameters:

- `lat` (number): Latitude (e.g. from device GPS) — pair with lon
- `location` (string): Room code or building name
- `lon` (number): Longitude — pair with lat

### `prohibited_items` (~120 tokens)

What you cannot bring into an area of the Capitol complex (security screening). zone: 'capitol_cvc' (the Capitol + Visitor Center — strictest, no food/water), 'gallery' (House/Senate galleries — no phones/cameras), or 'office_building' (the 6 office buildings — food & drink allowed). Always returns the universal weapon/hazard bans too. Volatile — live-source-stamped; confirm at visitthecapitol.gov before you travel.

Input parameters:

- `zone` (string, required): Which area you're entering

### `plan_day` (~109 tokens)

Optimize a multi-meeting Hill day. Give a list of meetings (each a member name or room code, with an optional time like '10:30a'). Returns a sequenced itinerary: batched by chamber side to minimize cross-campus crossings, the route + minutes between each stop, the cross-campus window flagged, 'leave-by' times when meetings are timed, and warnings for connections too tight to make.

Input parameters:

- `accessible` (boolean): Plan step-free routes
- `meetings` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/guide-capitol-capitolguide/capitol#diagnostics

## Score history

- 2026-08-03: 57
- 2026-08-02: 56
- 2026-08-01: 56
- 2026-07-31: 55
- 2026-07-30: 57
- 2026-07-29: 56
- 2026-07-28: 56
- 2026-07-27: 55
- 2026-07-26: 54

## Links

- Remote endpoint: https://capitol.guide/mcp
- Website: https://capitol.guide/
- Changelog RSS feed: https://verifymcp.io/servers/guide-capitol-capitolguide/capitol/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/guide-capitol-capitolguide/capitol/changelog.json
- HTML version of this page: https://verifymcp.io/servers/guide-capitol-capitolguide/capitol