Tolca
REMOTE · TOLCA.TONBOT.CA · 2 COMPONENTS
Know who you are paying before you pay: Québec contractor and company checks, plus web search. x402.
Available components
Last scanned (39 minutes ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 565 tokens (~188/item across 3 items; 3 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Tool “company_profile” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- Tool coverage: 100% → 85% ▼ functional
- Schema quality: 359 → 560 ▼ functional
- Tool coverage: 100% → 67% ▼ functional
- New tool “company_profile” functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://tolca.tonbot.ca/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tolca.tonbot.ca | CN=YE2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 556d32617caf3bf48e6fa85b64e8f84e99b |
| SANs: tolca.tonbot.ca | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tolca.tonbot.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| tonbot.ca. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tolca.tonbot.ca/mcp/public | Verified | 200 | |
| http (plaintext) | http://tolca.tonbot.ca/mcp/public | HTTPS enforced | 308 | https://tolca.tonbot.ca/mcp/public |
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 →
company_profile Company profile from a website or name ~206
Get a company's profile in one call, read live from its own website plus official registries: what it does, industry, services, service area, address, phones and emails published by the company (each with the page it came from), social links, and official screening (company registries, contractor licences, US, UK, EU and Canadian sanctions lists). Use when the user asks who a company is, how to contact it, or wants to research a prospect, supplier or partner. Provide domain (preferred) or name, optional city and country. Businesses only, no personal data. Free with a shared daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| country | string | – | ISO 3166 alpha-2, e.g. CA, US |
| domain | string | – | Company website or domain, e.g. acme.com |
| lang | string | – | – |
| name | string | – | Company name, used to find the website when no domain is given |
No output schema declared.
No examples provided.
qc_contractor_check Québec contractor check ~201
Check a Québec construction contractor against four official public data sources in one call: active RBQ licence (status, restrictions, bond, authorized work categories), RENA (businesses barred from public contracts and public subcontracts), environmental administrative penalties (MELCCFP) and public contracts awarded on SEAO (count, total amount, main public buyers, last 12 months). Returns a verdict ok / review / blocking / not_found with reasons, sources and extraction dates. Use when the user asks whether a Québec contractor, subcontractor or renovation company is licensed, trustworthy or eligible for public contracts. Provide neq, licence or name.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Answer language, default fr |
| licence | string | – | RBQ licence number, e.g. 8315-8105-31 |
| name | string | – | Business name, exact or partial |
| neq | string | – | Québec enterprise number (NEQ), 10 digits |
| Name | Type | Req | Description |
|---|---|---|---|
| environmental_penalties | array | yes | Matching environmental administrative penalties |
| notice | string | – | – |
| public_contracts | object | – | Public contracts awarded on SEAO in the last 12 months: contracts, total_cad, first_award, last_award, buyers, by_category, recent (up to 5), matched_by |
| query | object | yes | What was searched and how it matched |
| rbq | – | yes | RBQ licence record: licence, neq, name, status, restriction, bond, municipality, subcategory_labels, candidates |
| reasons | array | yes | Plain-language reasons for the verdict |
| rena | array | yes | Matching RENA entries (public-contract ban) |
| sources | array | yes | Official sources with extraction dates |
| verdict | string | yes | ok = active licence, no RENA, no penalty; review = something to look at; blocking = RENA listing or no active licence; not_found = no match |
| verdict_label | string | yes | – |
No examples provided.
qc_licence Québec RBQ licence lookup ~158
Fast lookup: does this Québec business hold an ACTIVE RBQ (Régie du bâtiment du Québec) construction licence right now? Returns active true/false, licence number, legal name, NEQ, municipality, restriction flag and authorized work categories. Good for checking several contractors one after another. For the RENA public-contract ban and environmental penalties, use qc_contractor_check. Provide neq, licence or name.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Answer language, default fr |
| licence | string | – | RBQ licence number, e.g. 8315-8105-31 |
| name | string | – | Business name, exact or partial |
| neq | string | – | Québec enterprise number (NEQ), 10 digits |
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | true if an ACTIVE RBQ licence was found |
| candidates | array | yes | Other possible matches when the name is ambiguous |
| categories | array | yes | Authorized RBQ work subcategories |
| licence | string|null | yes | – |
| municipality | string|null | yes | – |
| name | string|null | yes | – |
| neq | string|null | yes | – |
| note | string | – | – |
| query | object | yes | – |
| restricted | boolean|null | – | – |
| source | object | yes | – |
No examples provided.
How do I install the Tolca MCP server?
Tolca is a hosted endpoint at https://tolca.tonbot.ca/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tolca.tonbot.ca
claude mcp add --transport http yayabough-tolca 'https://tolca.tonbot.ca/mcp/public'
What is the Tolca MCP server?
Tolca is an MCP server listed in the public MCP registry as io.github.yayabough/tolca. Know who you are paying before you pay: Québec contractor and company checks, plus web search. x402. This page covers its hosted endpoint (https://tolca.tonbot.ca/mcp/public).
Is the Tolca MCP server safe to use?
Tolca scores 78 out of 100 on VerifyMCP. 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 Tolca MCP server expose?
Tolca exposes 3 tools: qc_contractor_check, qc_licence, company_profile. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Does the Tolca MCP server require authentication?
No. We connected to Tolca without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tolca MCP server still maintained?
Tolca is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.