Skip to content

myoutfitters.ca MCP server

ca.myoutfitters/mcpmyoutfitters.castreamable-httpv1.0.0Scanned

Search Canadian hunting and fishing outfitters, check availability, and send price requests.

8 tools: 1 do something that can't be undone, 1 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 1 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the myoutfitters.ca MCP server can do

The myoutfitters.ca MCP server is published by myoutfitters.ca, a domain the MCP Registry verified. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_price_request) and create or change data (1 tool: check_availability), but cannot delete data. 6 tools only read.

1 tool reads private data (fetch); 1 tool brings in text other people can write (search_outfitters); 1 tool can send data out of your system (create_price_request). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Can't be undone 1Claude Code: ask
  • create_price_requestSend a traveller's enquiry to one outfitter through MyOutfitters' anonymised relay.Can send data outNo findings

    Why it is in this group

    • The name "create_price_request" says "create": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Send 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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Changes things 1Claude Code: ask
  • check_availabilityFor up to 10 named outfitters, tell whether the requested dates fall in season and which packages fit the party.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    For 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • fetchRetrieve one MyOutfitters outfitter document by the id returned by `search` (e.g.Reads private dataNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
    Description, as the server wrote it
    Retrieve 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • 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 …No findings

    Why it is in this group

    • The name "get_booking_options" says "get": a word for reading.
    Description, as the server wrote it
    For 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_outfitterPublic profile of one outfitter: territory, species, season, and up to 8 summarised packages.No findings

    Why it is in this group

    • The name "get_outfitter" says "get": a word for reading.
    Description, as the server wrote it
    Public 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • 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 c…No findings

    Why it is in this group

    • The name "list_reference_data" says "list": a word for reading.
    Description, as the server wrote it
    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. Contains no outfitter data.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "search_outfitters" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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, 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__myoutfitters__create_price_request"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://myoutfitters.ca/mcp: tools/list returned 8 tools to an anonymous client, including create_price_request (irreversible), check_availability (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http myoutfitters https://myoutfitters.ca/mcp
claude mcp add --transport http myoutfitters https://myoutfitters.ca/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__myoutfitters__list_reference_data",
      "mcp__myoutfitters__search",
      "mcp__myoutfitters__fetch",
      "mcp__myoutfitters__search_outfitters",
      "mcp__myoutfitters__get_outfitter",
      "mcp__myoutfitters__get_booking_options"
    ],
    "ask": [
      "mcp__myoutfitters__check_availability",
      "mcp__myoutfitters__create_price_request"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as myoutfitters. Review it before you use it.

Capability tags behind 3 rules
  • mcp__myoutfitters__fetch private-data
  • mcp__myoutfitters__search_outfitters untrusted-input
  • mcp__myoutfitters__create_price_request outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ca.myoutfitters/mcp/verify?hash=b80a5d04edd9edfe3ddd64c3564133856ef68ad6cb7a0a7aee631103f20a0d05" | jq -e '.changed == false'

Pinned hash b80a5d04edd9, from Nov 12, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ca.myoutfitters/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ca.myoutfitters/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ca.myoutfitters/mcp.svg)](https://radar.anlyon.com/servers/ca.myoutfitters/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

myoutfitters.ca MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the myoutfitters.ca MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the myoutfitters.ca MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the myoutfitters.ca MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: create_price_request.

What tools does the myoutfitters.ca MCP server have?

8 tools: 1 irreversible, 1 write, 6 read. create_price_request, check_availability, list_reference_data, search, fetch, search_outfitters, get_outfitter and get_booking_options.

Does the myoutfitters.ca MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the myoutfitters.ca MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_price_request.

Has the myoutfitters.ca MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.