Is ca.veilpoint/opportunity-exchange up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://veilpoint.ca/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://veilpoint.ca/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://veilpoint.ca with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 72 tools: assess_procurement_relevance, assess_workforce_demand, check_business_health, check_comparability, check_opportunity_readiness, compare_communities, compare_municipalities, compare_outcomes, compare_roles, create_sandbox_business, evaluate_pathways, explain_business_claim, explain_confidence, explain_truth_state, find_connected_entities, find_potential_customers, find_potential_suppliers, get_business_evidence, get_business_health, get_business_health_markdown, get_community_economy, get_community_profile, get_data_providers, get_data_sources, get_economic_signal, get_economy_overview, get_emerging_signals, get_entity, get_entity_context, get_evidence, get_generated_asset, get_health_action_history, get_knowledge_graph_status, get_labour_demand, get_municipality_evidence_coverage, get_real_estate, get_rents, get_role, get_sector, get_source_provenance, get_trade_overview, get_wage_evidence, get_wages, grant_business_consent, inspect_knowledge_frontier, inspect_procurement_activity, investigate_economic_question, list_economic_signals, list_health_capabilities, list_noc_groups, list_roles, list_sandbox_businesses, list_sectors, query_knowledge_graph, rank_communities, recheck_business_health, report_health_action_complete, resolve_citation, resolve_entities, resolve_entity, run_business_study, run_business_study_markdown, search_businesses, search_employers, search_entities, search_hiring_activity, search_licensed_businesses, set_website_domain, start_health_action, summarize_credential_demand, traverse_relationships, update_business_record.

No change to its tools between 2026-09 and 2026-10.

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameca.veilpoint/opportunity-exchange
Endpointhttps://veilpoint.ca/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy