govtenders-mcp
# govtenders-mcp
[](https://www.npmjs.com/package/govtenders-mcp)
[](https://opensource.org/licenses/MIT)
MCP server for government tender data. Search 11,000+ active contracts from CanadaBuys (Canada) and SAM.gov (United States).
Powered by [ONE-1](https://one-1-x402-production.up.railway.app/api/info) autonomous agent with [x402](https://x402.org) micropayments on Base.
## Setup
### Claude Desktop
Add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"govtenders": {
"command": "npx",
"args": ["govtenders-mcp"]
}
}
}
```
### Claude Code
```bash
claude mcp add govtenders -- npx govtenders-mcp
```
### Cursor / VS Code
Add to MCP settings:
```json
{
"govtenders": {
"command": "npx",
"args": ["govtenders-mcp"]
}
}
```
## Tools
| Tool | Description | Cost |
|------|-------------|------|
| `get_tender_stats` | Active tender count, countries, industries | Free |
| `search_tenders` | Search by industry, region, country, value range | $0.05 USDC |
| `get_latest_tenders` | Latest published tenders by date | $0.03 USDC |
| `match_tenders` | AI-powered semantic matching via Claude Haiku | $0.15 USDC |
## Example Queries
Once installed, ask your AI assistant:
- "Show me construction tenders in Ontario"
- "Find IT contracts in California over $500K"
- "What government contracts match my cybersecurity consulting business?"
- "How many active tenders are there right now?"
- "Get the latest government procurement opportunities"
## How It Works
The `get_tender_stats` tool is free and returns live statistics from the API. The search, feed, and match tools hit x402 payment-gated endpoints. Without a wallet configured, they return pricing info and direct URLs. The free stats tool alone provides valuable metadata about 11,000+ active opportunities.
## Payment
Paid endpoints use [x402](https://x402.org) micropayments in USDC on Base (eip155:8453). When a paid tool is called without payment credentials, it returns the price and a direct URL to the API endpoint.
## Links
- [Live API](https://one-1-x402-production.up.railway.app/api/info) — Free endpoint with tender stats
- [x402 Manifest](https://one-1-x402-production.up.railway.app/.well-known/x402.json) — Service discovery
- [Agent Card](https://one-1-x402-production.up.railway.app/.well-known/agent-card.json) — ERC-8004 identity
- [ERC-8004 NFT](https://basescan.org/nft/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432/20934) — On-chain agent identity
## License
MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: stats overview, structured search, recent tenders, and semantic matching. While search_tenders and match_tenders both return tenders, their input methods and intended use cases are well-differentiated by the descriptions.
All tool names follow a consistent verb_noun pattern with snake_case: get, search, get, match. The names are predictable and clearly indicate the action being performed.
Four tools is an appropriate and well-scoped set for a government tender discovery server. Each tool covers a distinct need without unnecessary overlap or bloat.
The tool surface covers the main discovery workflows: checking stats, searching with filters, getting latest updates, and semantic matching. A minor gap is the lack of a dedicated tool to fetch full details of a specific tender by ID, but the provided tools likely return sufficient information for most workflows.