Tolca MCP Server
# tolca-mcp
MCP server for **Tolca**: know who you're paying before you pay.
- **qc_contractor_check**: Québec contractor check in one call. RBQ licence, RENA (barred from public contracts), environmental penalties, SEAO public contracts. Verdict `ok` / `review` / `blocking` / `not_found`, with sources and extraction dates.
- **qc_licence**: does this business hold an active RBQ licence right now?
Free daily quota, no API key, no account. Deterministic JSON (no LLM in the loop).
## Install
Claude Code:
```bash
claude mcp add tolca -- npx -y tolca-mcp
```
Claude Desktop, Cursor, VS Code, any stdio MCP client:
```json
{
"mcpServers": {
"tolca": { "command": "npx", "args": ["-y", "tolca-mcp"] }
}
}
```
Prefer remote? Use the hosted endpoint directly: `https://tolca.tonbot.ca/mcp/public` (streamable HTTP).
## More tools (pay per call, x402)
The paid MCP server at `https://tolca.tonbot.ca/mcp` adds **web_search** (10 results + clean text of the top pages, $0.008), **business_verification** (sanctions, Canadian federal corporations, UK Companies House, GLEIF) and more, paid in USDC on Base per call. Point this bridge at it with `TOLCA_MCP_URL=https://tolca.tonbot.ca/mcp`.
## How it works
This package is a thin stdio bridge: it lists the tools of the hosted Tolca server and forwards each call. The data and checks run on tolca.tonbot.ca.
Data: Régie du bâtiment du Québec, Autorité des marchés publics, MELCCFP, SEAO (Données Québec, CC-BY 4.0).
MIT licence. Website: https://tolca.tonbot.ca
TDQS
Scored across 2 tools
The two tools overlap on RBQ licence checks, but descriptions clearly distinguish qc_licence as a fast single-source lookup and qc_contractor_check as a comprehensive multi-source verification. The explicit pointer from qc_licence to qc_contractor_check for additional checks reduces potential confusion.
Both names use snake_case and a 'qc_' prefix, but the structure is inconsistent: qc_licence is a simple noun while qc_contractor_check is noun_verb. There is no predictable verb_noun pattern, though the names remain readable.
Only two tools are provided, which feels thin for a contractor verification domain that could support separate checks per data source or batch operations. However, the comprehensive tool consolidates most needs, making the count borderline rather than severely lacking.
The tools cover four key public data sources (RBQ, RENA, environmental penalties, SEAO) and support lookup by NEQ, licence, or name. This is strong coverage for the stated purpose, though other potential checks like workplace safety or legal disputes are not addressed.