Skip to main content
Glama
JonnyWaffles

va-lis-mcp

by JonnyWaffles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to va-lis-mcp

No user-submitted related servers found.

    Related Servers

    • legiscan

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying legislative data from the LegiScan API, including bills and votes, via natural language through an MCP gateway.
      2 npm
      MIT

    • cdgmcp

      adathouse
      F
      license
      A
      quality
      C
      maintenance
      Exposes a Congress.gov-style legislative GraphQL API to MCP clients, enabling querying bills, actions, committee activities, and cosponsors via natural language.
      7
      -

    • Congress.gov API MCP Server

      bsmi021
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying U.S. legislative data from Congress.gov API using MCP resources for direct lookups and tools for searching and retrieving related data.
      8
      MIT

    • 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

    • mcp-data-va

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and querying Virginia Open Data (datahub.va.gov) via the Socrata API, providing tools to search datasets, run SoQL queries, and retrieve metadata.
      4 npm
      MIT

    • LegiScan MCP Server

      sh-patterson
      A
      license
      A
      quality
      B
      maintenance
      Provides access to legislative data from all 50 US states through the LegiScan API, enabling comprehensive search and retrieval of bills, votes, legislators, and legislative session information.
      10
      4 npm
      11
      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

    A4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources (bills, members, committees, meetings, calendars), but get_bill_votes and get_roll_call both cover votes, and get_bill_patrons vs get_bill's patrons field overlap. Descriptions are detailed enough to disambiguate, though the vote-related pair could still cause misselection.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: get_* for single resources, list_* for collections, check_api_key as the lone exception but still a clear verb_noun. No mixed conventions or vague verbs.

    Tool Count4/5

    22 tools is on the higher end but justified by the breadth of legislative data (bills, members, committees, meetings, calendars, votes). Each tool covers a distinct data need; the count feels slightly heavy but not bloated.

    Completeness5/5

    The surface covers the legislative domain thoroughly: sessions, bills with text/summaries/history/patrons/votes, members with their bills/votes/committees, committees with rosters/meetings/dockets, floor calendars, and API key validation. No obvious dead ends; the descriptions even document workarounds for LIS API limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources