Skip to main content
Glama
dam2452

atlas-przetargow-mcp-py

by dam2452
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to atlas-przetargow-mcp-py

No user-submitted related servers found.

    Related Servers

    • Atlas Przetargów

      atlasprzetargow
      A
      license
      A
      quality
      D
      maintenance
      Search 800 000+ Polish public tenders (BZP + TED) from Claude Desktop, Cursor, Continue. Provides 8 tools for tender search, buyer/contractor profiles by NIP, market statistics, plus a glossary of 90+ Polish public procurement terms.
      8
      340 npm
      3
      MIT

    • LexSocket MCP Server

      lexsocket
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables search and analysis of European public procurement tenders, including EU above-threshold (TED) and below-threshold from 11 national sources, with hybrid search and filtering.
      MIT

    • tendermcp

      oivoodoo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to search recent EU TED and Spanish PLACSP tender notices by keyword, country, and source, and to retrieve individual notices by id. A free tier returns five notices without source links, while an API key from tender.bitscorp.co unlocks every notice and call.
      MIT

    • cerebro-mcp

      benjixone
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and analyzing government tenders, contract awards, and pre-tender pipelines from 21 official sources, with tools for tender search, award intelligence, and detailed notice retrieval.
      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.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools map to clearly distinct resource/action pairs: search vs detail vs timeline vs entity profiles vs stats. The only potential confusion is between get_tender_offers and extract_contract_value, since both parse notice text and can return offer prices, but their focus (offer statistics vs all monetary amounts) is documented.

    Naming Consistency4/5

    Tool names almost all follow a verb_noun snake_case pattern like search_tenders, get_tender, and get_category_stats. raw_request is the lone deviation, but it is clearly an escape hatch and does not create confusion.

    Tool Count5/5

    Twelve tools is well within the ideal range for a domain-specific read-only API wrapper. Each tool covers a meaningful facet—search, detail, timeline, offers, entities, CPV lookup, stats—and none feels redundant.

    Completeness5/5

    The server covers core tender workflows: searching, retrieving details, following notice timelines, extracting offer/contract values, and resolving buyer/contractor entities. It also provides CPV and regional statistics plus a raw_request escape hatch for endpoints not yet wrapped, so agents rarely hit dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources