Skip to main content
Glama

Related Servers

Alternatives to sam-gov-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and retrieve U.S. federal contract opportunities from SAM.gov by department, date range, and result limit, including direct links to official opportunity pages.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search federal contracts, analyze agency spending, track competitor wins, and monitor small business set-aside opportunities using SAM.gov, USASpending.gov, and FPDS data.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Search and analyze U.S. federal government contracts and opportunities from SAM.gov. Tools for keyword search, contract details, competitive analysis, and capability statement drafting — built for AI agents via x402 USDC micropayments.
      3
      2
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to search and analyze federal government contract opportunities and awards from SAM.gov and USASpending.gov, with tools for contract search, detail, agency spending, and trending sectors.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search and retrieve US government contracts, look up NAICS codes, list indexed states, and score contract fit for a business profile. Provides access to live state and local procurement data through natural language without raw HTTP.
      7
      95 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for querying SAM.gov federal contract opportunities, providing precise search, retrieval, and attachment tools with full source traceability and explicit abstention when data is absent.
      5
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools occupy clearly separate roles: free-text discovery (search_opportunities), exact-record retrieval by noticeId (get_opportunity), and a static reference lookup (list_set_aside_codes). The search-vs-get boundary is explicitly spelled out, so there is no plausible misselection.

    Naming Consistency5/5

    All three names follow the same snake_case verb_noun pattern (get_/list_/search_ + resource), with the verb matching the operation performed. No mixed conventions or vague verbs.

    Tool Count4/5

    Three tools is on the thin side but is coherent for a narrowly scoped read-only search surface; nothing is redundant or padding. A slightly richer surface (e.g. a description/attachment retrieval call) would make the count feel less minimal.

    Completeness3/5

    Search, single-record fetch, and set-aside codes cover the core lookup loop, but get_opportunity explicitly stops at links and never downloads attachments or full descriptions, leaving an agent at a dead end for the details procurement work usually needs. Reference data is also partial (only set-aside codes, no NAICS/PSC lists).

    Maintenance

    ActivityNo data
    ResponsivenessSyncing