mcp
ca.myoutfitters/mcpVersion 1.0.0Search Canadian hunting and fishing outfitters, check availability, and send price requests.
Status
Responds1032 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:41 UTC
- Latency
- 1032 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://myoutfitters.ca/mcpResponds1032 msNo sign-in
Claude Code
claude mcp add --transport http myoutfitters https://myoutfitters.ca/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: myoutfitters
Remote MCP server URL: https://myoutfitters.ca/mcpCursor
{
"mcpServers": {
"myoutfitters": {
"url": "https://myoutfitters.ca/mcp"
}
}
}VS Code
code --add-mcp '{"name":"myoutfitters","type":"http","url":"https://myoutfitters.ca/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
8 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_availabilityFor up to 10 named outfitters, tell whether the requested dates fall in season and which packages fit the party. Returns a verdict per outfitter, never raw inventory. | Not declared | Yes | Yes | No |
create_price_requestSend a traveller's enquiry to one outfitter through MyOutfitters' anonymised relay. Requires the traveller's own name and e-mail, given with their consent. The outfitter replies by e-mail; neither side sees the other's raw contact details. | No | No | Not declared | No |
fetchRetrieve one MyOutfitters outfitter document by the id returned by `search` (e.g. 'PV-0009') or by its MyOutfitters URL. Returns id, title, url, readable text and metadata. No phone, e-mail or website is ever returned. | Not declared | Yes | Yes | No |
get_booking_optionsFor one outfitter, return how a stay can be booked: booking mode (online payment on MyOutfitters, or a price request through MyOutfitters' anonymised relay), the packages that fit the party and the requested dates, indicative per-person rates when the listing is confirmed, the season window and the exact next step. Optionally pass dates and party size to filter the packages and get a season/availability verdict. | Not declared | Yes | Yes | No |
get_outfitterPublic profile of one outfitter: territory, species, season, and up to 8 summarised packages. Rates appear only when the outfitter has confirmed its listing. No phone, e-mail or website is ever returned. | Not declared | Yes | Yes | No |
list_reference_dataList 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. Contains no outfitter data. | Not declared | Yes | Yes | No |
searchFree-text search over MyOutfitters' Canadian hunting and fishing outfitters (pourvoiries). Returns up to 10 documents with id, title and URL; pass an id to `fetch` for the full profile. For precise multi-criteria filtering (species, region, budget, lodging, dates) prefer search_outfitters. No phone, e-mail or website is ever returned. | Not declared | Yes | Yes | No |
search_outfittersFind 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, single-lodging capacity, bedrooms, two-person and one-person bed counts, meal plan, season and equipment/amenities. Lodging criteria (capacity, bedrooms, beds, amenities) must all be met by the SAME cabin. At least one criterion is required — the full directory is never returned. Results carry no phone number, e-mail or website: enquiries go through create_price_request. Call list_reference_data to learn the valid values for any filter. | Not declared | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Repository
- Not given
- Categories (suggested)
- Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared