Skip to main content
Glama

Server Details

Canada Government Procurement MCP — CanadaBuys open data (keyless).

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
38.4% over 43 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-canada-tenders
GitHub Stars
1
Server Listing
mcp-canada-tenders

TDQS

A4.1/5.0

Scored across 33 tools

Disambiguation3/5

The descriptions do a lot of work steering between ask_pipeworx, ask_pipeworx_grounded, deep_research, and the entity tools, which helps. However ask_pipeworx_beta is explicitly admitted to be identical to ask_pipeworx right now, and the polymarket_* family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) plus entity_profile/recent_changes/compare_entities/resolve_entity have genuinely overlapping purposes that require reading long descriptions to separate.

Naming Consistency4/5

Almost everything is snake_case, and the dominant pattern is verb_noun (validate_claim, resolve_entity, compare_entities, discover_tools, scan_dependency, generate_llms_txt). A minority are noun-first (entity_profile, recent_alerts, recent_changes, deep_research), which is a minor deviation but still readable and consistent in style.

Tool Count3/5

33 tools is above the 25+ 'heavy' threshold and the surface spans wildly different domains (prediction markets, npm packages, AI-visibility marketing, government tenders, memory, subscriptions), so it is dense for a single server. The breadth is arguably justified for a gateway, but several tools are variants of one another, which inflates the count.

Completeness4/5

The lifecycle is broadly covered: discovery (discover_tools, suggest_questions), identity (resolve_entity), research (ask_pipeworx, deep_research, entity_profile, compare_entities, recent_changes), grounding (ask_pipeworx_grounded, validate_claim, search_within), memory (remember/recall/forget), and monitoring (subscribe/unsubscribe/list_subscriptions/recent_alerts). Minor gaps like no explicit document-fetch/citation-read tool, but agents can work around them.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server for Canadian procurement intelligence, enabling unified search of federal and Alberta tender opportunities, deadline tracking, profile-based matching, daily briefs, and AI-assisted bid analysis.
    -
  • F
    license
    A
    quality
    D
    maintenance
    MCP server for searching government tenders from CanadaBuys and SAM.gov with free stats and paid search, latest, and AI matching tools using x402 micropayments.
    4
    1
    -
  • A
    license
    A
    quality
    B
    maintenance
    An MCP server that gives Claude access to Canada's public procurement data from CanadaBuys, enabling search for tenders, awards, and spend summaries with traceable sources. It provides five tools: search_tenders, get_tender, search_awards, summarize_spend, and export_report.
    5
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.