Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TenderTrail: Canadian government contracts

NPM · TENDERTRAIL-MCP

Canadian federal tenders, RFPs, contract awards and expiring contracts (recompete leads).

Available components

0 this week 65 Trust /100

Last scanned (17 hours ago)

Scores higher than 37% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1093 tokens (~121/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 50

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/tendertrail-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 111 packages
Packages resolved 111
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,093 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
awards_search ~138

PAID $0.02 USDC per successful call. Government of Canada contract awards since Aug 2022 (29k+ awards) by keyword, supplier, department, date range and minimum value. Returns totals plus the most recent matches.

NameTypeReqDescription
buyerstring–Department name
fromstring–Award date from (YYYY-MM-DD)
limitnumber–1-25, default 10
minValuenumber–Minimum value in CAD
qstring–Keywords
supplierstring–Supplier name
tostring–Award date to (YYYY-MM-DD)

No output schema declared.

No examples provided.

buyer_profile ~94

PAID $0.05 USDC per successful call. One department's spending: total awards and value, top suppliers (incumbents), top categories, yearly trend, non-competitive share, contracts expiring in 12 months and its tenders open now. Ambiguous names return candidates and are not charged.

NameTypeReqDescription
namestringyesDepartment or agency name (fuzzy), e.g. 'Shared Services Canada'

No output schema declared.

No examples provided.

contracts_expiring ~185

PAID $0.05 USDC per successful call. Government of Canada contracts that end within N days: incumbent supplier, buying department, value (CAD), end date, procurement method, whether it was non-competitive, and open tenders from the same buyer that may be the re-tender. Errors and not-found are not charged.

NameTypeReqDescription
buyerstring–Department name, e.g. 'Shared Services Canada'
excludeStandingOffersboolean–Exclude standing offers and supply arrangements
limitnumber–1-25, default 10
minValuenumber–Minimum contract value in CAD
qstring–Keywords (title/description/category)
supplierstring–Incumbent supplier name
withinDaysnumber–Ending within this many days (1-730, default 365)

No output schema declared.

No examples provided.

demo_expiring_contracts ~124

FREE, no wallet needed. Top 3 (by value) Government of Canada contracts ending within N days that match the keywords, with incumbent, department, value (CAD) and end date, plus the total count and value of all matches. Rate-limited per day. Use contracts_expiring for the full list with re-tender signals.

NameTypeReqDescription
qstring–Keywords, e.g. 'cybersecurity', 'janitorial', 'translation'
withinDaysnumber–Ending within this many days (90, 180 or 365)

No output schema declared.

No examples provided.

demo_open_tenders ~69

FREE, no wallet needed. Up to 5 Government of Canada tenders/RFPs open now on CanadaBuys matching the keywords, with closing date and the official notice link. Rate-limited per day.

NameTypeReqDescription
qstring–Keywords, e.g. 'cybersecurity'

No output schema declared.

No examples provided.

export_expiring_contracts ~167

PAID $1.00 USDC per successful call (requires TENDERTRAIL_MAX_PER_CALL_USD >= 1). Up to 1,000 Government of Canada contracts ending soon, sorted by value, saved to a local CSV or JSON file for CRM import. Same filters as contracts_expiring.

NameTypeReqDescription
buyerstring–Department
excludeStandingOffersboolean–Exclude standing offers and supply arrangements
formatstring–Default csv
limitnumber–1-1000, default 1000
minValuenumber–Minimum CAD
qstring–Keywords
supplierstring–Incumbent
withinDaysnumber–1-730, default 365

No output schema declared.

No examples provided.

supplier_profile ~86

PAID $0.05 USDC per successful call. One company's Government of Canada business: total awards and value, top departments, top categories, yearly trend, non-competitive share, active contracts and contracts expiring in 12 months. Ambiguous names return candidates and are not charged.

NameTypeReqDescription
namestringyesSupplier name (fuzzy), e.g. 'Oracle Canada'

No output schema declared.

No examples provided.

tender_history ~81

PAID $0.01 USDC per successful call. What TenderTrail has observed for one tender: first seen, amendments, closing-date changes, and when it left the open list (early exit can mean cancellation). Use a ref from tenders_search.

NameTypeReqDescription
refstringyesTender reference, e.g. 'cb-536-24115079'

No output schema declared.

No examples provided.

tenders_search ~149

PAID $0.01 USDC per successful call. Search Government of Canada tenders, RFPs and RFQs open now on CanadaBuys by keyword, province, category and closing window. Returns title, department, closing date, days to close, regions and the official notice URL.

NameTypeReqDescription
categorystring–GD goods, SRV services, CNST construction, SRVTGD services related to goods
closingWithinDaysnumber–Only tenders closing within N days
limitnumber–1-25, default 10
provincestring–Province or region, e.g. 'Ontario'
qstring–Keywords

No output schema declared.

No examples provided.

Install

How do I install the TenderTrail: Canadian government contracts MCP server?

TenderTrail: Canadian government contracts runs locally as an npm package, launched with npx -y tendertrail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tendertrail-mcp

# add to Claude Code
claude mcp add tendertrail-tendertrail-mcp -- npx -y tendertrail-mcp
Common questions

What is the TenderTrail: Canadian government contracts MCP server?

TenderTrail: Canadian government contracts is an MCP server listed in the public MCP registry as io.github.tendertrail/tendertrail-mcp. Canadian federal tenders, RFPs, contract awards and expiring contracts (recompete leads). This page covers its npm package (tendertrail-mcp).

Is the TenderTrail: Canadian government contracts MCP server safe to use?

TenderTrail: Canadian government contracts scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TenderTrail: Canadian government contracts MCP server expose?

TenderTrail: Canadian government contracts exposes 9 tools: demo_expiring_contracts, demo_open_tenders, contracts_expiring, tenders_search, tender_history, and 4 more. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.

Is the TenderTrail: Canadian government contracts MCP server still maintained?

TenderTrail: Canadian government contracts is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the TenderTrail: Canadian government contracts MCP server under?

TenderTrail: Canadian government contracts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the TenderTrail: Canadian government contracts MCP server?

VerifyMCP ran 14 checks on TenderTrail: Canadian government contracts, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about TenderTrail: Canadian government contracts: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.