Skip to content

capitolguide MCP server

guide.capitol/capitolguidecapitol.guidestreamable-httpv0.1.0Scanned

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

9 tools: 2 do something that can't be undone, 6 change things and 1 only read.

Tools: 0 delete, 2 irreversible, 6 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 2
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the capitolguide MCP server can do

The capitolguide MCP server is published by capitol.guide, a domain the MCP Registry verified. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (route_between and accessible_route) and create or change data (6 tools: capitolguide_prep, overview, check_access, nearby and 2 more), but cannot delete data. 1 tool only reads.

7 tools bring in text other people can write (find_room, route_between, accessible_route and 4 more); 2 tools can send data out of your system (route_between and accessible_route).

The fixed checks matched 4 findings (tool-shadowing, annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Can't be undone 2Claude Code: ask
  • accessible_routeStep-free / accessible directions between two points in the Capitol complex by mobility profile (wheelchair, limited_mobility, stroller, low_vision).Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "accessible_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • route_betweenTurn-by-turn directions between two points in the Capitol complex.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "route_between" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Changes things 6Claude Code: ask
  • capitolguide_prepPre-flight readiness check.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The description contains "any other tool", wording about other tools or servers.

      Matched text

      description: "Pre-flight readiness check. Run before any other tool. Verifies secrets, KV, DB connectivity,..."

      What this check looks for
    Description, as the server wrote it
    Pre-flight readiness check. Run before any other tool. Verifies secrets, KV, DB connectivity, and KB version + freshness. Returns a structured readiness report.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • check_accessWhat 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 a…Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...plex: (visitor_type × zone) → allowed?, credential, escort, lead time, required docs, secu..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • nearbyNearest restroom, exit, and food for a specific point — a room code (floor-specific, e.g.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • overviewOperational snapshot for the caller's tenant: KB version + freshness, queue depths (itineraries / draft meetings / active nudges), and the recent tool-invocation tail.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • plan_dayOptimize a multi-meeting Hill day.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • prohibited_itemsWhat you cannot bring into an area of the Capitol complex (security screening).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • find_roomFind a Capitol office by ROOM CODE (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "find_room" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://capitol.guide/mcp: tools/list returned 9 tools to an anonymous client, including route_between (irreversible), accessible_route (irreversible), capitolguide_prep (write), overview (write), check_access (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 8
    • Protocol version: none to 2024-11-05
  2. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 8 to 0
    • Protocol version: 2024-11-05 to none

Findings

Matches of fixed checks, with the text they matched.

3 warn1 info
  • The description contains "any other tool", wording about other tools or servers.

    Matched text

    description: "Pre-flight readiness check. Run before any other tool. Verifies secrets, KV, DB connectivity,..."

    What this check looks for
  • The server marks "route_between" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "accessible_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...plex: (visitor_type × zone) → allowed?, credential, escort, lead time, required docs, secu..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 8 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 8
    • Protocol version: none to 2024-11-05
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 8 to 0
    • Protocol version: 2024-11-05 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__capitolguide__find_room"
    ],
    "ask": [
      "mcp__capitolguide__capitolguide_prep",
      "mcp__capitolguide__overview",
      "mcp__capitolguide__route_between",
      "mcp__capitolguide__accessible_route",
      "mcp__capitolguide__check_access",
      "mcp__capitolguide__nearby",
      "mcp__capitolguide__prohibited_items",
      "mcp__capitolguide__plan_day"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as capitolguide. Review it before you use it.

Capability tags behind 7 rules
  • mcp__capitolguide__find_room untrusted-input
  • mcp__capitolguide__route_between untrusted-input, outbound
  • mcp__capitolguide__accessible_route untrusted-input, outbound
  • mcp__capitolguide__check_access untrusted-input
  • mcp__capitolguide__nearby untrusted-input
  • mcp__capitolguide__prohibited_items untrusted-input
  • mcp__capitolguide__plan_day untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/guide.capitol/capitolguide/verify?hash=b2322f2bf57767dbb5c2fc04dab5671dfe99117e374795e7d68303024633cd20" | jq -e '.changed == false'

Pinned hash b2322f2bf577, from Nov 15, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/guide.capitol/capitolguide/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for guide.capitol/capitolguide
[![Anlyon Radar](https://radar.anlyon.com/badge/guide.capitol/capitolguide.svg)](https://radar.anlyon.com/servers/guide.capitol/capitolguide)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

capitolguide MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the capitolguide MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the capitolguide MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the capitolguide MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: route_between and accessible_route.

What tools does the capitolguide MCP server have?

9 tools: 2 irreversible, 6 write, 1 read. route_between, accessible_route, capitolguide_prep, overview, check_access, nearby, prohibited_items, plan_day and 1 more.

Does the capitolguide MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the capitolguide MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): route_between and accessible_route.

Has the capitolguide MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.