Skip to main content
Glama
Sign In
uk-tenders-mcp

uk-tenders-mcp

by atz1man
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to uk-tenders-mcp

No user-submitted related servers found.

    Related Servers

    • Tender MCP

      OjasKord
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to find, score, and monitor government contract opportunities across UK, EU, and US with AI-powered relevance scoring.
      2
      103 npm
      1
      MIT

    • tender-radar-mcp

      zohaibaamer
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to search and retrieve unified UK and EU public procurement notices, match company profiles against open tenders, review upcoming deadlines, and run governed metric queries through a semantic layer without free-SQL access.
      6
      MIT
    • oro-intel-mcp

      oro-intel-mcpofficial

      oro-intel
      A
      license
      Not graded
      quality
      D
      maintenance
      UK public procurement data for AI agents. Tenders, contracts, buyer and supplier profiles over MCP and REST. 250 free credits.
      MIT

    • koko-call-mcp

      sugukurukabe
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server for searching Japanese government procurement bid notices (官公需) from the SME Agency's KKJ portal. Includes AI ranking, PDF requirement extraction, and CSV/calendar export.
      49 npm
      Apache 2.0

    • cerebro-mcp

      benjixone
      A
      license
      Not graded
      quality
      C
      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 4 tools

    Disambiguation4/5

    Each tool targets a distinct step in the workflow: browsing profiles, finding tenders, ranking them, and checking a company. The only soft overlap is between search_tenders and score_tenders, since both query the same sources and return similar fields, but the descriptions clearly separate 'find tenders' from 'which are worth bidding for'.

    Naming Consistency5/5

    All four tools follow a clean verb_noun snake_case pattern (list_profiles, search_tenders, score_tenders, get_company). The verb choice is also semantically accurate (list vs search vs score vs get), so names are both consistent and predictable.

    Tool Count4/5

    Four tools is lean but each has a clear role in a coherent pipeline: profiles -> search -> score, plus an external company lookup. It sits at the low end of the comfortable range; a tender-detail or source-listing tool would round out the surface without bloat.

    Completeness3/5

    Core discovery and qualification are covered, but there is no way to fetch a full tender notice (only summary fields with a source_url), no profile creation/editing, and get_company requires a company number with no name-based lookup. These gaps force agents to leave the server or ask the user for data mid-workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources