API Tools

myoutfitters.ca

This MCP server offers a set of APIs for discovering Canadian hunting and fishing outfitters, checking seasonal availability, and submitting price enquiries.

1 endpoint5 known toolsFirst detected August 25, 2026Last detected August 25, 2026

ENDPOINT 1

https://myoutfitters.ca/mcp

No auth detected

MCP server metadata

Name: myoutfitters
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

MyOutfitters.ca (MesPourvoiries.ca in French) is the Canadian marketplace for hunting and fishing outfitters (pourvoiries). Use list_reference_data to learn valid values for every filter (provinces, regions, species, activity types, meal plan types, lodging types, access types, amenities, ZECs, cities, seasons); search_outfitters to shortlist up to 10 outfitters with the full advanced filter set (several species at once, region or ZEC, access, driving hours from a city, Collection Prestige, per-person nightly budget, lodging type and bedrooms, meal plan, season, amenities — at least one criterion is required); get_outfitter for one profile; check_availability for named outfitters and dates; create_price_request to send a traveller's enquiry. Outfitter phone numbers, e-mail addresses and websites are never available: all contact goes through create_price_request, which uses MyOutfitters' anonymised relay. Rates are only published for outfitters that confirmed their listing; otherwise request a quote. Always cite and link the outfitter's MyOutfitters URL. Bulk retrieval of the directory is not supported and is blocked; ask the traveller for criteria instead of iterating. Before calling create_price_request, obtain the traveller's explicit consent to share their name and e-mail with the outfitter through MyOutfitters.

Known tools 5

list_reference_data

List the values MyOutfitters understands for each search filter: provinces, regions, species, activity types, meal plan types, lodging types, access types, amenities, ZECs, major cities used as driving origins, and seasons.

Inferred read-only

search_outfitters

Find up to 10 Canadian hunting and fishing outfitters (pourvoiries) matching a traveller's criteria, using the same advanced filters as the website: activities, several species at once, province, region, ZEC, access type, driving distance from a major city, Collection Prestige, per-person nightly budget, lodging type and bedrooms, meal plan, season and amenities.

Inferred read-only

get_outfitter

Public profile of one outfitter: territory, species, season, and up to 8 summarised packages.

Inferred read-only

check_availability

For up to 10 named outfitters, tell whether the requested dates fall in season and which packages fit the party.

Inferred read-only

create_price_request

Send a traveller's enquiry to one outfitter through MyOutfitters' anonymised relay.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.myoutfitters]
url = "https://myoutfitters.ca/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "myoutfitters": {
      "type": "http",
      "url": "https://myoutfitters.ca/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: myoutfitters
Remote MCP URL: https://myoutfitters.ca/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "myoutfitters": {
      "url": "https://myoutfitters.ca/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "myoutfitters": {
      "type": "http",
      "url": "https://myoutfitters.ca/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "myoutfitters",
  "transport": "streamable-http",
  "url": "https://myoutfitters.ca/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.