← Registry

General Tools

capitol.guide

Provides navigation and operational information for the Capitol complex.

1 endpoint9 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://capitol.guide/mcp

No auth detected

MCP server metadata

Name
capitolguide
Version
0.1.0
Capabilities
tools
Server instructions

Capitol navigation concierge. Decode room codes & members, route the complex, plan a multi-meeting day, check access, list prohibited items, find amenities. The 7 navigation tools (find_room, route_between, accessible_route, check_access, nearby, prohibited_items, plan_day) are PUBLIC — call them with no auth. Only capitolguide_prep and overview need a capability token (Authorization: Bearer …). Informs & prepares access; never grants it — final authority is the member office / Capitol Police / Secret Service.

Known tools 9

capitolguide_prep

Pre-flight readiness check.

Inferred read-only
overview

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

Inferred read-only
find_room

Find a Capitol office by ROOM CODE (e.

Inferred read-only
route_between

Turn-by-turn directions between two points in the Capitol complex.

Inferred read-only
accessible_route

Step-free / accessible directions between two points in the Capitol complex by mobility profile (wheelchair, limited_mobility, stroller, low_vision).

Inferred read-only
check_access

What access a visitor needs for a zone of the Capitol complex: (visitor_type × zone) → allowed?

Inferred read-only
nearby

Nearest restroom, exit, and food for a specific point — a room code (floor-specific, e.

Inferred read-only
prohibited_items

What you cannot bring into an area of the Capitol complex (security screening).

Inferred read-only
plan_day

Optimize a multi-meeting Hill day.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.capitolguide]
url = "https://capitol.guide/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "capitolguide": {
      "type": "http",
      "url": "https://capitol.guide/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: capitolguide
Remote MCP URL: https://capitol.guide/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "capitolguide": {
      "url": "https://capitol.guide/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "capitolguide": {
      "type": "http",
      "url": "https://capitol.guide/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "capitolguide",
  "transport": "streamable-http",
  "url": "https://capitol.guide/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for capitol.guide was fetched 2026-08-03T18:22:31.951Z and is being refreshed.

Trust status Neutral

capitol.guide is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.