Skip to main content
Glama
matematicsolutions

us-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to us-eli-mcp

No user-submitted related servers found.

    Related Servers

    • CongressMCP-bridge

      amurshak
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for the Congress.gov API that consolidates 91 operations into 6 comprehensive legislative tools that can be used by any MCP client (i.e. Claude Desktop), or MCP-compatible AI agent, to query and reason about congressional data.
      4 npm
      1
      JavaScript
      MIT

    • CongressMCP-full

      amurshak
      A
      license
      A
      quality
      A
      maintenance
      The open Congress.gov MCP server. Provides comprehensive access to the Congress.gov API through 6 organized toolsets, enabling AI systems to retrieve and interact with legislative data from the United States Congress with a clean, unified interface.
      24
      112 PyPI
      32
      Sustainable Use v1.0

    • Congress.gov API MCP Server

      bsmi021
      A
      license
      Not graded
      quality
      C
      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

    • br-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the Brazilian Chamber of Deputies open-data API, enabling search and retrieval of federal legislative bills and their status.
      15
      1
      Apache 2.0

    • 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
    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.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct legal source and action: bills, code packages, Federal Register, case law, CFR sections, and a coverage tool. The search/get pairs are clearly separated by resource type, and even similar regulatory sources (Federal Register vs CFR) are distinct.

    Naming Consistency4/5

    All tools follow the 'us_' prefix with a verb_noun pattern (search_, get_, list_). The only outlier is 'us_coverage', which uses a noun instead of verb_noun, and 'get_case' is shorter than 'get_federal_register_doc', but overall the pattern is consistent and predictable.

    Tool Count5/5

    11 tools is well-scoped for a legal research connector covering multiple sources. Each tool serves a clear purpose, and the count is within the ideal 3-15 range, not feeling bloated or sparse.

    Completeness4/5

    The server provides search and retrieval for each major legal source: bills, code packages, Federal Register, case law, and CFR. The coverage tool explicitly identifies gaps and fallbacks, which mitigates incompleteness. Minor missing operations like a direct 'get CFR section' tool are workable through search and history tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources