ca.veilpoint/opportunity-exchange
REMOTE · VEILPOINT.CA
Keyless Saskatchewan labour-market data: measured wages and rents, roles, jobs, outcomes, pathways.
Available components
Last scanned (3 hours ago)
Scores higher than 81% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Data and Analytics
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Oct 26 +57
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 72 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 21 Oct 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 14 Sept 26 0
- Stability: fail → pass ▲ security
- 13 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
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://veilpoint.ca/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of veilpoint.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| veilpoint.ca. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://veilpoint.ca/mcp | Unreachable | ||
| http (plaintext) | http://veilpoint.ca/mcp | HTTPS enforced |
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 →
list_roles ~36
The Saskatchewan occupation catalogue: id, title, NOC code, sector, hourly wage, demand score. Start here to find role ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sandbox_businesses ~26
List the sandbox businesses that exist, so you can resume working on one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sectors ~39
Sector rollups with provider-qualified hiring-record counts, median wage and occupation demand. Candidate profiles are excluded. Read meta.evidence before interpreting a count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_knowledge_graph ~368
Query the materialized semantic graph without downloading whole datasets. Resolve an entity name/code and optional municipality geography, then return typed facts and relationships. This supports municipality-by-NAICS GDP and business queries without encoding classifications in metric names. Missing facts or edges mean unknown, never zero or false.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | – | Bounded metric preset. municipal-economic-profile-v1 requires one municipality entity. |
| depth | integer | – | Hops to expand outward from entity; default 1. Above 1 adds an expansion block of nodes and edges annotated with the hop that reached them, so a containment chain such as municipality -> census-divis… |
| entity | string | – | Exact name, slug, graph id, NOC code, SGC code, source id, or provider id. |
| geography | string | – | Optional exact municipality name, slug, or SGC code for geography-scoped facts. |
| limit | integer | – | Maximum facts, relationships, or listed entities; default 25. |
| maxNodes | integer | – | Ceiling on entities across the whole expansion; default 200. Distinct from limit, which bounds one level — without it a depth of 2 from a municipality would pull every business in it. |
| metrics | array | – | Fact metrics, e.g. population. |
| minimumConfidence | string | – | – |
| predicates | array | – | Relationship predicates, e.g. classified_as or serves. |
| referencePeriodEnd | string | – | Inclusive ISO-8601 upper bound for fact reference periods. |
| referencePeriodStart | string | – | Inclusive ISO-8601 lower bound for fact reference periods. |
| truthStates | array | – | – |
| type | string | – | Optional entity-type constraint. |
No output schema declared.
No examples provided.
rank_communities ~75
Rank Saskatchewan communities by monthly discretionary income for exactly one role or explicit hourly wage.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of ranked communities, 1-20 (default 10). |
| occupation | string | – | Role id whose median wage should be modelled. |
| wage | number | – | Explicit positive hourly wage in CAD. |
No output schema declared.
No examples provided.
recheck_business_health ~82
Ask OEX to look again — what a business does after fixing something. Inspects the website if one is supplied. Rate-limited, and a check that could not run is reported as unable-to-verify rather than as fixed.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| checkId | string | – | Optional: recheck one finding rather than all. |
No output schema declared.
No examples provided.
report_health_action_complete ~61
Record that the owner says a finding is fixed. This is their claim, not OEX's: nothing renders as resolved until a recheck runs and the check actually passes.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| checkId | string | yes | – |
No output schema declared.
No examples provided.
resolve_citation ~83
Resolve a public graph assertion citation to its canonical entity or entities, exact assertion, source, observation time, truth state, confidence, publication scope, methodology and provenance. Accepts the OEX citation URN, token, or resolver URL returned beside a graph fact or relationship.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | citation.id, citation resolver URL, or versioned citation token. |
No output schema declared.
No examples provided.
resolve_entities ~102
Resolve a user-supplied name, slug, NOC code, SGC code, program, sector or governed source to its canonical OEX identity. Call this before joining datasets when the identifier is uncertain. Results include the correct follow-up MCP tool and arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches; default 8. |
| query | string | yes | Name, alternate title, slug, or official identifier. |
| type | string | – | Optional entity-type constraint. |
No output schema declared.
No examples provided.
resolve_entity ~77
Resolve user language or an official code to the canonical OEX identity and the correct next tool. Returns ranked candidates when the input is ambiguous.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches; default 8. |
| query | string | yes | Name, alternate title, slug, or official identifier. |
| type | string | – | Optional entity-type constraint. |
No output schema declared.
No examples provided.
run_business_study ~221
Run the Guided Business Study on a sandbox business: Business Health plus the three analytical instruments — Negative Space (what would be expected here and is not observed), Boundary Fracture (values that exist on one of the business’s own surfaces and never crossed to the other), and Strategic Node Finder (the one intervention that addresses several findings at once) — composed into one lineage-preserving result. Reads only the evidence OEX already holds; this tool never fetches the website. Every conclusion cites the evidence behind it, insufficient evidence returns explicit unknowns rather than guesses, and zero strategic nodes is a real answer.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| inspectWebsite | boolean | – | Optional, default false. Inspect the website on record before running, so the stages that compare the site against the record can actually look. Costs one bounded fetch of the claimed domain; without… |
| objective | string | – | Optional: what the business is trying to accomplish, in its own words. Carried into the study. |
No output schema declared.
No examples provided.
run_business_study_markdown ~101
The same Guided Business Study as a markdown document — the form a study is handed over in, with each stage’s findings beside its own evidence table.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| inspectWebsite | boolean | – | Optional, default false. Inspect the website on record before running, so the stages comparing the site against the record can look. Costs one bounded fetch. |
| objective | string | – | Optional: the business’s stated objective. |
No output schema declared.
No examples provided.
search_businesses ~112
Search governed municipal licensed-business snapshots without inferring operating health, employment, ownership, or hiring.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Rows to return, 1-200 (default 50). |
| municipalityId | string | yes | Municipality id. Only communities with a reviewed snapshot resolve. |
| offset | number | – | Rows to skip for paging. |
| q | string | – | Business-name contains match. |
| subsector | string | – | Three-digit NAICS subsector code to filter by, e.g. 484. |
No output schema declared.
No examples provided.
search_employers ~131
Search the public business directory by name, municipality, sector group and observed hiring flag. Preview providers return modelled activity scenarios, not business claims.
| Name | Type | Req | Description |
|---|---|---|---|
| hiring | boolean | – | true to filter on the disclosed hiring flag; preview providers expose modelled scenarios. |
| limit | integer | – | Result limit, 1-100 (default 25). |
| municipality | string | – | Municipality id from /api/v1/municipalities. |
| q | string | – | Case-insensitive text search over employer and sector names. |
| sector | string | – | Sector-group id from /api/v1/sectors. |
No output schema declared.
No examples provided.
search_entities ~68
Search across supported OEX entity classes using names, aliases, slugs, and official identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches; default 8. |
| query | string | yes | Name, alternate title, slug, or official identifier. |
| type | string | – | Optional entity-type constraint. |
No output schema declared.
No examples provided.
search_hiring_activity ~219
Source-attributed hiring-activity evidence, newest first and filterable by occupation, sector and geography. data.recordPurpose and each row recordPurpose are hiring_activity_evidence; rows are observations with isActionable=false, not jobs offered for application through OEX. Check observationDate, lastVerifiedAt, provenance, meta.evidence.truthState and synthetic before using a record as current evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size, 1-200 (default 50). |
| minWage | number | – | Minimum hourly wage, CAD. |
| municipality | string | – | Exact municipality name. |
| occupation | string | – | Role id from the occupation catalogue. |
| offset | integer | – | Pagination offset (default 0). |
| postedWithinDays | integer | – | Only postings newer than this many days. |
| q | string | – | Free-text search over title, employer and description. |
| region | string | – | Exact region name. |
| sector | string | – | Sector id from the sector list. |
| type | string | – | Employment type. |
No output schema declared.
No examples provided.
search_licensed_businesses ~184
Named businesses holding a municipal licence in one community, from an attributed City snapshot. Answers who exists and in which industry, NOT who is hiring — use search_employers for that. Each row is a licence held on the reference date: it is not a legal-entity register, not current beyond that date, incomplete for excluded licence categories, and not evidence of ownership, employment, size or operating health. Home-based licences carry no address.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Rows to return, 1-200 (default 50). |
| municipalityId | string | yes | Municipality id. Only communities with a reviewed snapshot resolve. |
| offset | number | – | Rows to skip for paging. |
| q | string | – | Business-name contains match. |
| subsector | string | – | Three-digit NAICS subsector code to filter by, e.g. 484. |
No output schema declared.
No examples provided.
set_website_domain ~75
Tell OEX the business's website so it can be inspected. Supplying a domain permits inspection; it does not assert that the business owns or controls it, and OEX will not publish the domain as the business's own on this basis alone.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| domain | string | yes | – |
No output schema declared.
No examples provided.
start_health_action ~56
Record that work on a finding has begun — the owner opening the action. Moves the finding's action state, which is what makes its history readable later.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| checkId | string | yes | – |
No output schema declared.
No examples provided.
summarize_credential_demand ~39
Aggregate hiring records associated with occupational credential requirements. Candidate profiles and holder counts are excluded; the result describes demand evidence, not a proven shortage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
traverse_relationships ~326
Traverse bounded, typed economic relationships from a resolved entity without treating missing edges as false.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | – | Bounded metric preset. municipal-economic-profile-v1 requires one municipality entity. |
| depth | integer | – | Hops to expand outward from entity; default 1. Above 1 adds an expansion block of nodes and edges annotated with the hop that reached them, so a containment chain such as municipality -> census-divis… |
| entity | string | – | Exact name, slug, graph id, NOC code, SGC code, source id, or provider id. |
| geography | string | – | Optional exact municipality name, slug, or SGC code for geography-scoped facts. |
| limit | integer | – | Maximum facts, relationships, or listed entities; default 25. |
| maxNodes | integer | – | Ceiling on entities across the whole expansion; default 200. Distinct from limit, which bounds one level — without it a depth of 2 from a municipality would pull every business in it. |
| metrics | array | – | Fact metrics, e.g. population. |
| minimumConfidence | string | – | – |
| predicates | array | – | Relationship predicates, e.g. classified_as or serves. |
| referencePeriodEnd | string | – | Inclusive ISO-8601 upper bound for fact reference periods. |
| referencePeriodStart | string | – | Inclusive ISO-8601 lower bound for fact reference periods. |
| truthStates | array | – | – |
| type | string | – | Optional entity-type constraint. |
No output schema declared.
No examples provided.
update_business_record ~90
Correct or complete the business's own record — the fix for most findings about missing or thin information. Supply only the fields you are changing; an omitted field is left alone, not cleared.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| businessId | string | yes | – |
| category | string | – | – |
| description | string | – | – |
| name | string | – | – |
| phone | string | – | – |
No output schema declared.
No examples provided.
How do I install the ca.veilpoint/opportunity-exchange MCP server?
ca.veilpoint/opportunity-exchange is a hosted endpoint at https://veilpoint.ca/mcp, 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 · veilpoint.ca
claude mcp add --transport http ca-veilpoint-opportunity-exchange 'https://veilpoint.ca/mcp'
What is the ca.veilpoint/opportunity-exchange MCP server?
ca.veilpoint/opportunity-exchange is an MCP server listed in the public MCP registry as ca.veilpoint/opportunity-exchange. Keyless Saskatchewan labour-market data: measured wages and rents, roles, jobs, outcomes, pathways. This page covers its hosted endpoint (https://veilpoint.ca/mcp).
Is the ca.veilpoint/opportunity-exchange MCP server safe to use?
ca.veilpoint/opportunity-exchange scores 80 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 ca.veilpoint/opportunity-exchange MCP server expose?
ca.veilpoint/opportunity-exchange exposes 72 tools: investigate_economic_question, inspect_knowledge_frontier, resolve_entities, get_entity_context, query_knowledge_graph, and 67 more. Their descriptions and schemas cost roughly 7,211 tokens of context every time the server is loaded.
Does the ca.veilpoint/opportunity-exchange MCP server require authentication?
Its publisher declares no required credentials for ca.veilpoint/opportunity-exchange. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ca.veilpoint/opportunity-exchange MCP server still maintained?
ca.veilpoint/opportunity-exchange is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.