_ registry / mcp streamable-http · checked 3m ago

capitolguide

https://capitol.guide

Registry code: 24f2084fe8173e4e

api record

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.

endpoint
https://capitol.guide/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is capitolguide live?
Yes — it answered the hub's last check (checked 3m ago). It answered 100% of checks over the last 30 days.
Is capitolguide free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does capitolguide have?
9 tools: check_access, plan_day, prohibited_items, route_between, nearby, accessible_route, find_room, capitolguide_prep, ….
Is capitolguide safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
271ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 254 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • find a us capitol office by room or member
  • get directions inside the capitol complex
  • plan a multi-meeting day on capitol hill
  • check visitor access and prohibited items
takes → gives
text → data
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open2 auth-required 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_room reads open 8h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "A room code/address, or a member's name"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • capitolguide_prep reads auth-required 15h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • overview reads auth-required 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • check_access reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "visitor_type",
        "zone"
      ],
      "properties": {
        "zone": {
          "enum": [
            "cvc_public",
            "capitol_tour",
            "house_gallery",
            "senate_gallery",
            "office_building",
            "committee_hearing",
            "subway",
            "grounds",
            "restricted"
          ],
          "type": "string",
          "description": "Which area of the complex"
        },
        "visitor_type": {
          "enum": [
            "public",
            "constituent",
            "advocate",
            "press",
            "staff",
            "vip"
          ],
          "type": "string",
          "description": "Who is visiting"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • plan_day reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "meetings"
      ],
      "properties": {
        "meetings": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "who"
            ],
            "properties": {
              "who": {
                "type": "string",
                "description": "Member name or room code"
              },
              "time": {
                "type": "string",
                "description": "Optional start time, e.g. '10:30a'"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 20,
          "minItems": 1
        },
        "accessible": {
          "type": "boolean",
          "description": "Plan step-free routes"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • prohibited_items reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "zone"
      ],
      "properties": {
        "zone": {
          "enum": [
            "capitol_cvc",
            "office_building",
            "gallery"
          ],
          "type": "string",
          "description": "Which area you're entering"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • route_between reads unknown 11h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Destination: room code, building name, or Metro station / landmark"
        },
        "from": {
          "type": "string",
          "description": "Origin: room code, building name, or Metro station / landmark (e.g. 'Capitol South Metro')"
        },
        "accessible": {
          "type": "boolean",
          "description": "Prefer a step-free / accessible route"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • nearby reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "anyOf": [
        {
          "required": [
            "location"
          ]
        },
        {
          "required": [
            "lat",
            "lon"
          ]
        }
      ],
      "properties": {
        "lat": {
          "type": "number",
          "description": "Latitude (e.g. from device GPS) — pair with lon"
        },
        "lon": {
          "type": "number",
          "description": "Longitude — pair with lat"
        },
        "location": {
          "type": "string",
          "description": "Room code or building name"
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • accessible_route reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Destination: room code, building name, or Metro station / landmark"
        },
        "from": {
          "type": "string",
          "description": "Origin: room code, building name, or Metro station / landmark (e.g. 'Union Station')"
        },
        "mobility_profile": {
          "enum": [
            "wheelchair",
            "limited_mobility",
            "stroller",
            "low_vision",
            "any"
          ],
          "type": "string",
          "description": "Mobility profile (default: any step-free)"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 24f2084fe8173e4e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/24f2084fe8173e4e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/24f2084fe8173e4e/badge.svg)](https://brick.blue/agent/24f2084fe8173e4e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.