Skip to main content
Glama
cstillick

who_reps-mcp

by cstillick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to who_reps-mcp

No user-submitted related servers found.

    Related Servers

    • CivicLens Cook County

      eshaambhattad-tech
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to look up every layer of local government for any Cook County address, including representatives, finances, and agendas, with provenance and certainty levels for data.
      -

    • oravan

      cm2489
      A
      license
      A
      quality
      A
      maintenance
      Remote MCP server for nonpartisan U.S. Congress data: plain-language bill decodes (bilingual EN/ES), representative lookup by ZIP with district-office phones, and what's-moving urgency ranking. Read-only, keyless.
      5
      1
      AGPL 3.0

    • Bucky

      markbucky
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables cited site feasibility and pre-development project workflows for Canada and the US, returning lot, zoning, permitted uses, and material envelope details with provenance for a given street address.
      Apache 2.0

    • civic-awareness-mcp

      julianken
      A
      license
      A
      quality
      D
      maintenance
      Provides tools to search and retrieve US federal and state legislative data, including bills, votes, campaign contributions, and legislator information, with provenance tracking.
      8
      1
      MIT

    • mcp-openstates

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Access U.S. state legislative data including bills, legislators, and votes across all 50 states via the OpenStates API.
      43 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: lookup_officials and lookup_by_district differ in input (address vs. chamber+district), list_districts provides district IDs, get_official_details gives detailed info on a single official, and ping is a health check. No ambiguity.

    Naming Consistency4/5

    Tool names follow a pattern of verb_noun (list_districts, get_official_details, lookup_by_district, lookup_officials) with one exception (ping). The verbs 'list', 'get', and 'lookup' are thematically coherent, though using 'lookup' for two tools could cause slight confusion.

    Tool Count4/5

    Five tools is a reasonable count for a focused domain like legislative representation lookup. Each tool serves a distinct function, and the set feels neither sparse nor bloated.

    Completeness4/5

    The tool set covers core operations: address-based lookup, district-based lookup, district listing, and official details. Missing features like coordinate-based lookup or batch queries are minor gaps that don't significantly hinder typical use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources