ca.veilpoint/opportunity-exchange
REMOTE · VEILPOINT.CA · SCANNED SEP 20
Keyless Saskatchewan labour-market data: measured wages and rents, roles, jobs, outcomes, pathways.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8036 tokens (~111/item across 72 items; 72 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 72 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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'
{
"mcpServers": {
"ca-veilpoint-opportunity-exchange": {
"url": "https://veilpoint.ca/mcp"
}
}
} {
"servers": {
"ca-veilpoint-opportunity-exchange": {
"type": "http",
"url": "https://veilpoint.ca/mcp"
}
}
} [mcp_servers.ca-veilpoint-opportunity-exchange] url = "https://veilpoint.ca/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ca-veilpoint-opportunity-exchange": {
"type": "remote",
"url": "https://veilpoint.ca/mcp",
"enabled": true
}
}
} openclaw mcp add ca-veilpoint-opportunity-exchange --url 'https://veilpoint.ca/mcp' --transport streamable-http
mcp_servers:
ca-veilpoint-opportunity-exchange:
url: "https://veilpoint.ca/mcp" {
"McpServers": {
"ca-veilpoint-opportunity-exchange": {
"Transport": "http",
"Url": "https://veilpoint.ca/mcp"
}
}
} assistant mcp add ca-veilpoint-opportunity-exchange -t streamable-http -u 'https://veilpoint.ca/mcp'
{
"mcpServers": {
"ca-veilpoint-opportunity-exchange": {
"type": "http",
"url": "https://veilpoint.ca/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +1
- The server rewrote its instructions, which are the text every model session reads security
- 12 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “inspect_knowledge_frontier” functional
- 10 Sept 26 +1
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 91 to 93.
- 28 Aug 26 0
- Tool “check_business_health” rewrote its description, which is the text the model reads security
- “check_business_health” reworded the description of “website” cosmetic
- 27 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “check_opportunity_readiness” functional
- New tool “list_health_capabilities” functional
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 20 Sept 2026 · Probed https://veilpoint.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=veilpoint.ca | CN=YE2,O=Let's Encrypt,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 674f49e18d86df0961db13bfbdac660047e |
| SANs: veilpoint.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 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 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https:; worker-src 'self' blob:; child-src 'self' blob:; manifest-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
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 | Verified | 200 | |
| http (plaintext) | http://veilpoint.ca/mcp | HTTPS enforced | 301 | https://veilpoint.ca/mcp |
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.
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?
No. We connected to ca.veilpoint/opportunity-exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ca.veilpoint/opportunity-exchange MCP server still maintained?
ca.veilpoint/opportunity-exchange is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.