Skip to content

DogPolicies MCP server

io.github.xultrax-web/dogpolicies-mcpxultrax-webstreamable-httpv0.6.1Scanned

Verified dog rules for California and Nevada travel: hotel pet fees, trip plans, highway stops

18 tools: 11 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 11 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

11 tools here change things. Govern them.

  • 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 DogPolicies MCP server can do

The DogPolicies MCP server is published by the GitHub account xultrax-web. It has 18 tools. It can create or change data (11 tools: dogpolicies_near, dogpolicies_plan_trip, dogpolicies_route_stops, dogpolicies_i5_corridor and 7 more), but cannot delete data. 7 tools only read.

2 tools bring in text other people can write (dogpolicies_browse_answers and dogpolicies_report_correction).

The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.

Last scanned Nov 22, 2026, version 0.6.1.

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.

18 tools

Changes things 11Claude Code: ask
  • dogpolicies_changes_nearHas anything changed around where I am going since my last trip or since a date: a fee, a leash rule, a closure?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
    Has anything changed around where I am going since my last trip or since a date: a fee, a leash rule, a closure? Re-checks a saved itinerary or a destination: one area, one place or one stretch of highway. Inputs: place (city, county, neighborhood, area or region: "Tahoe", "Alameda", "Monterey") or near={lat, lon}, with radius_miles; or place_id for one place; or route (i-5, us-101, highway-1 ...) with from_mile and to_mile for the listed stops on that stretch. since as YYYY-MM-DD; optional outcome (confirmed, changed, source_gone, blocked, disputed). Returns verification events for places in scope, newest first, each with the place, outcome, date and record link, the rule-change log entries for them, and on the hosted server a separate corrections list (corrections filed for those places or decided since the date, by ticket id and status). An empty list means nothing was re-checked or changed in that window; an unknown name is an answer with did_you_mean. Example: "What changed near Monterey since September?" -> place="Monterey", since="2026-09-01"

    Annotations the server declares

    • title: What changed near a town
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_changes_sinceWhat changed in the dog rules anywhere since a date: which fees, leash rules or closures were updated or found gone?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
    What changed in the dog rules anywhere since a date: which fees, leash rules or closures were updated or found gone? A cheap poll for new changes across all the data, without re-reading records. Input: since as YYYY-MM-DD; optional outcome (confirmed, changed, source_gone, blocked, disputed), for example "changed" for only real rule changes. Returns events newest first, each naming the place, what happened, who checked, the date and a link to the record. On the hosted server a separate corrections list shows corrections people filed or whose status changed since the date: ticket id, place, kind of fact, status (filed, verified, rejected), dates and a status_url; what the reporter wrote is never included.

    Annotations the server declares

    • title: Changes since a date
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_emergency_vetWhere is the nearest 24-hour or emergency animal hospital to this town, landmark or point: "my dog ate something near Kettleman City", "emergency vet near South Lake Tahoe tonight"…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
    Where is the nearest 24-hour or emergency animal hospital to this town, landmark or point: "my dog ate something near Kettleman City", "emergency vet near South Lake Tahoe tonight"? Returns the nearest hospitals with address, phone number, whether they are open 24 hours every day or take emergencies in published hours, any hours the hospital publishes for an upcoming holiday such as Thanksgiving, the straight-line distance, the hospital's own page and the date it was read. Mountain and desert stretches often have none close: the answer then names the nearest one anyway with its distance. It gives where, when and the phone number only: never medical advice. Tell the traveler to call ahead. Inputs: place as people say it (a city, county, neighborhood, airport) or near={lat, lon}; radius_miles (default 60, up to 200); open_24h_only (default false). Examples: - "My dog ate chocolate, we are near Kettleman City" -> place="Kettleman City" - "24-hour vet near South Lake Tahoe" -> place="South Lake Tahoe", open_24h_only=true - "Emergency vet near here" -> near={lat:38.68, lon:-119.75}

    Annotations the server declares

    • title: Nearest emergency vet
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_i5_conditionsIs I-5 open right now: lane closures, chain controls, road weather and sign messages on the freeway in California, and the nearest dog stop to each?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
    Is I-5 open right now: lane closures, chain controls, road weather and sign messages on the freeway in California, and the nearest dog stop to each? Live state, not rules: Caltrans feeds fetched within the last 15 minutes (fetched_at in the result), not verified rules. Covers the Grapevine and every other stretch of I-5 in California. Other highways are not covered. Inputs: from_mile and to_mile, or near={lat, lon} with direction and ahead_miles; with none, all of I-5 in California. Each condition is placed on the I-5 centerline (mile, s meters from San Ysidro) and matched to the nearest dog stop. If the feeds cannot be read the answer has outcome unavailable and the address of the live Caltrans page. A result older than two hours is marked stale. Examples: - "Is there a closure or chains on the Grapevine right now?" -> from_mile=170, to_mile=222 - "Weather and closures in the next 60 miles northbound from Redding" -> near={lat:40.59, lon:-122.39}, direction="north", ahead_miles=60

    Annotations the server declares

    • title: I-5 conditions now
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_i5_corridorWhat is on I-5 between here and there for a dog: the next restroom stops with a pet area, the stops on the Grapevine, between Sacramento and Redding?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
    What is on I-5 between here and there for a dog: the next restroom stops with a pet area, the stops on the Grapevine, between Sacramento and Redding? For the freeway in California only, by one of eleven named stretches (sandiego, orange-la, grapevine, kern-westside, westside, delta, sacramento, valley, tehama, shasta, siskiyou), a mile range, or a window ahead of a point. It covers I-5 only, with no hotel fee arithmetic and no closures or chain controls. Inputs: strip, or from_mile and to_mile (Caltrans odometer), or near={lat, lon} with direction (north or south) and ahead_miles; family=true keeps stops whose official source states restrooms and a pet area or dog park; paired=true adds exits with places for people nearby (counted from OpenStreetMap, never named, not verified for restrooms) matched to the nearest dog-legal place. With none of these it lists the stretches. Each stop carries its mile, s in meters from San Ysidro, the side of the road, distance off the freeway, and restrooms, water, pet area and hours as the source states them, with source URL and verified date. A rest area Caltrans reports fully closed right now carries closed_now (Caltrans' reason and end time); it stays in the list and the text names the first open stop instead. Examples: - "What is between the Grapevine and Kettleman?" -> strip="grapevine" and strip="kern-westside" - "The next 5 family stops northbound from Stockton" -> near={lat:37.95, lon:-121.29}, direction="north", family=true, limit=5 - "Every stop between mile 300 and 340" -> from_mile=300, to_mile=340

    Annotations the server declares

    • title: I-5 corridor by stretch
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_nearWhat can my dog do in or around this town, neighborhood or region: beaches, parks, trails, hotels, campgrounds, cabins, patios and rest areas, nearest first?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
    What can my dog do in or around this town, neighborhood or region: beaches, parks, trails, hotels, campgrounds, cabins, patios and rest areas, nearest first? Answers "dog-friendly things in X" questions, grouped by kind. It does not check hotels against a dog's weight or a fee budget. Input: place as people say it: a city, county, neighborhood or alias ("Van Nuys", "Koreatown", "Venice Beach", "the Mission", "DTLA"), an area or region ("Lake Tahoe", "East Bay", "Central Valley"), or near={lat, lon}. Small spelling slips ("Montery") are corrected and labeled. If nothing is inside the radius it widens to 30, 60, then 100 miles and says so. Each result carries the dog rule, verified date and source URL. An unknown name comes back as an answer with did_you_mean, the nearest towns and next (a larger town or county that is covered). Examples: - "What can my dog do in Carmel?" -> place="Carmel" - "Dog beaches and parks around South Lake Tahoe" -> place="South Lake Tahoe", types=["beach","park"] - "Anything dog-friendly in Van Nuys?" -> place="Van Nuys" - "Anything dog-friendly within 5 miles of here" -> near={lat:36.6, lon:-121.9}, radius_miles=5

    Annotations the server declares

    • title: What is near a town
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_plan_tripPlan a dog trip to a town: where can we stay with this dog, what is the pet fee for all the nights, what can we do each day, where can we eat?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
    Plan a dog trip to a town: where can we stay with this dog, what is the pet fee for all the nights, what can we do each day, where can we eat? One answer covers a whole stay, such as "three nights in Monterey with our 70 lb Lab, pet fees under $150" or "camping near Mammoth Lakes". It plans a stay at one destination, not the stops along a drive. Inputs: place (a city, county, neighborhood, area or region, with small spelling slips corrected) or near={lat, lon}; dog_weight_lb, dogs, nights, max_total_fee, stay_types. Optional: start_date (dates each day), stay_id (build the plan on that stay), save=true (adds trip_url, a dogpolicies.com page showing the plan; the plan travels inside the link, nothing is stored). Returns stays that fit with the whole-stay pet fee worked out (a pet fee, never a room rate), stays that need a call to confirm, and "days": for each night the stay, a morning beach, trail or off-leash area, an afternoon park and a dinner patio, each a real record with source URL and verified date; a slot the data cannot fill is null with the reason (dinner often is). "plan_stay" shows the fee arithmetic and whether the dog's weight and number fit. Within 10 miles of I-5 in California it adds the drive leg: the town's mile and the next family stops each way. An unknown town is an answer with did_you_mean. The markdown answer is laid out as a trip document for the traveler. Examples: - "Three nights in Monterey with our 70 lb Lab, pet fees under $100" -> place="Monterey", dog_weight_lb=70, nights=3, max_total_fee=100 - "A weekend in South Lake Tahoe with two small dogs" -> place="South Lake Tahoe", dogs=2, nights=2 - "Camping near Mammoth Lakes with a dog" -> place="Mono County", stay_types=["campground","cabins"] - "Plan 4 nights in Carmel with two dogs and give me a link" -> place="Carmel-by-the-Sea", dogs=2, nights=4, save=true

    Annotations the server declares

    • title: Plan a trip with a dog
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_report_correctionTell us a rule is wrong: the fee went up, a beach closed to dogs, a hotel now takes two pets.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Tell us a rule is wrong: the fee went up, a beach closed to dogs, a hotel now takes two pets. For a record the traveler says is wrong or out of date; this is the one tool that writes. The report goes to a person who re-reads the official source, and the record does not change until it is verified: a report is filed, not a fix. Inputs: place_id from a result, message (what is wrong, in the traveler's words), optional fact (which kind of fact is wrong), optional source_url of the official page, optional contact if the traveler offers one. No other personal detail is accepted. The answer carries a ticket id and a status_url. The ticket's status (filed, then verified or rejected) is public there; what they wrote is not.

    Annotations the server declares

    • title: Report a correction
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • dogpolicies_road_conditionsDo I need chains on I-80 to Tahoe right now?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
    Do I need chains on I-80 to Tahoe right now? Is US-50 open over Echo Summit? Is Highway 89 closed at Emerald Bay? Caltrans chain controls, lane and ramp closures, road-weather stations and message-sign text on I-80, US-50, I-15, I-5, US-395 and the Lake Tahoe highways SR-89, SR-28, SR-267 and SR-88, in California, each at its route mile with the nearest dog stop. Live state, not rules: Caltrans feed data fetched every 15 minutes (fetched_at in the result), never a verified fact. For the day of a mountain or desert drive: Donner Summit, Echo Summit, Cajon Pass, the Grapevine. It reports conditions, not places to stop: each condition carries only the nearest dog stop. Nevada roads (SR-207, SR-431) are not covered: the answer links Nevada 511. Inputs: route ("I-80", "80", "US 50", "Highway 89", "SR 28", "I-5"); a window as from_mile and to_mile, or town (a town or named stretch on the route: Truckee, Donner Pass, Emerald Bay, Brockway, South Lake Tahoe, Cajon Pass, Barstow) with direction and ahead_miles; direction alone keeps that direction's closures, signs and chain controls. With no window, the whole route in California. chain_controls_in_effect is true when a Caltrans chain-control point in the window reports a control (any status but R-0), with Caltrans' own wording; a sign that mentions chains is listed under signs with its text. Each weather station says whether its reading is current (the feeds sometimes carry readings months old; those numbers are left out of the text). A document older than two hours is marked stale; when no document can be read the answer has outcome unavailable and the address of Caltrans QuickMap, the live map. Examples: - "Do I need chains on I-80 to Tahoe right now?" -> route="I-80", direction="east" - "Is Highway 50 open over Echo Summit?" -> route="Highway 50", town="Echo Summit" - "Closures on I-15 from Barstow to the Nevada line" -> route="I-15", town="Barstow", direction="north", ahead_miles=120

    Annotations the server declares

    • title: Road conditions now: closures, chains, weather
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_route_stopsWhere can we stop with the dog along this highway, in driving order: rest areas, travel stops with dog parks, hotels, campgrounds, parks and beaches, each with its mile and distanc…1 finding

    Why it is in this group

    • The name "dogpolicies_route_stops" says "stop": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "dogpolicies_route_stops" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "dogpolicies_route_stops" says "stop": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Where can we stop with the dog along this highway, in driving order: rest areas, travel stops with dog parks, hotels, campgrounds, parks and beaches, each with its mile and distance off the road? For a drive on I-5, US-101, Highway 1, I-15, I-80 or US-50 in California, or I-15, I-80, US-50, US-95 or US-93 in Nevada (each route stops at the state line). It lists stops, not closures or chain controls. Inputs: route (default i-5), a start as near={lat, lon} or from_mile, direction (north, south, east, west), ahead_miles or to_mile, dog_weight_lb and max_total_fee for stays. On I-5 add family=true (restrooms and a pet area stated by the source) or paired=true (an exit with places for people, plus the nearest dog-legal place). Each stop has its mile, side, distance off the road, dog rule, source URL and verified date; stays carry the whole-stay pet fee. On I-5 a rest area Caltrans reports fully closed right now carries closed_now (Caltrans' reason and end time), is left out of the "first open stop" in the text, and stays in the list. Examples: - "Driving north on I-5 from Los Angeles with a 70 lb dog, where can we stop?" -> near={lat:34.05, lon:-118.24}, direction="north", dog_weight_lb=70 - "Pet areas on the Grapevine" -> from_mile=170, to_mile=222, kinds=["rest_area","park"] - "Next restroom stop for the whole family, dog included, 40 miles north of Harris Ranch" -> near={lat:36.25, lon:-120.25}, direction="north", ahead_miles=40, family=true - "Heading south on 101 from San Francisco, where can the dog run?" -> route="us-101", near={lat:37.77, lon:-122.42}, direction="south" - "Driving I-80 east from Reno with a dog" -> route="i-80-nevada", near={lat:39.53, lon:-119.81}, direction="east"

    Annotations the server declares

    • title: Dog stops along a highway
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_subscribe_changesCan you tell me if the dog rules change at Carmel Beach before our trip?1 finding

    Why it is in this group

    • The name "dogpolicies_subscribe_changes" says "subscribe": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "dogpolicies_subscribe_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "dogpolicies_subscribe_changes" says "subscribe": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Can you tell me if the dog rules change at Carmel Beach before our trip? Can I follow changes near Lake Tahoe, or along I-5? For hearing about changes later, without asking again: it answers with a feed link (Atom and JSON Feed) for one place, a town, county, area or neighborhood with a radius, or a highway's stops, which any feed reader can follow. It computes the links and counts only; it signs nobody up, stores nothing and sends no email. Inputs: one of place (a place id from any answer, e.g. "carmel-beach"), near (a town, county, area, region or neighborhood, e.g. "Lake Tahoe", "Monterey", "Van Nuys") with radius_miles, or route (i-5, us-101, highway-1, i-15, i-80, us-50, or a Nevada route ending in -nevada) with from_mile and to_mile. Returns atom_url and json_url, how many verification events, rule changes and corrections the scope had in the last 90 days, the page for the scope, and share_text: a sentence with the link, written for the traveler. An unknown name is an answer with did_you_mean. Examples: - "Tell me if the rules change at Carmel Beach" -> place="carmel-beach" - "Can I get alerts for dog rule changes around Lake Tahoe?" -> near="Lake Tahoe" - "Follow changes on the Grapevine stretch of I-5" -> route="i-5", from_mile=170, to_mile=222

    Annotations the server declares

    • title: Follow rule changes in a feed
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • dogpolicies_browse_answersWhich places match a common question, as a ready-made list: California national parks that allow dogs, off-leash dog beaches in California, state parks that allow dogs?Reads text others writeNo findings

    Why it is in this group

    • The name "dogpolicies_browse_answers" says "browse": a word for reading.

    What it can reach

    • untrusted-inputThe name "dogpolicies_browse_answers" says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Which places match a common question, as a ready-made list: California national parks that allow dogs, off-leash dog beaches in California, state parks that allow dogs? Covers broad "list the ..." questions that are not about one town. Each list is fixed; it takes no county, type or off-leash filter. Without a slug it lists every question with its slug and result count; with a slug it returns that question's places (for example "off-leash-dog-beaches-california"), each with the dog rule, verified date and URL.

    Annotations the server declares

    • title: Browse answered questions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_compare_placesWhich of these places is better for my dog: Carmel Beach or Asilomar, two parks, three hotels?No findings

    Why it is in this group

    • The name "dogpolicies_compare_places" says "compare": a word for reading.
    Description, as the server wrote it
    Which of these places is better for my dog: Carmel Beach or Asilomar, two parks, three hotels? Sets two to six known places side by side, fact by fact. Input: ids from search results ("carmel-beach", "asilomar-state-beach"); an exact name or a near miss resolves to the one clear match. Returns one row per fact (dogs allowed, leash rule, where dogs may go, pet fee, weight limit, pets per room, restrictions) and one column per place, with confidence, freshness, who confirmed it, and a citation for each. An id that matches nothing is listed under missing with close matches while the rest are still compared (outcome partial); fewer than two found is no_match with suggestions.

    Annotations the server declares

    • title: Compare places side by side
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_find_hotelsWill a hotel take my dog, and what will the pet fee come to: a 70 lb Lab under $50, two dogs for three nights near Palm Springs, the Motel 6 in Fresno?No findings

    Why it is in this group

    • The name "dogpolicies_find_hotels" says "find": a word for reading.
    Description, as the server wrote it
    Will a hotel take my dog, and what will the pet fee come to: a 70 lb Lab under $50, two dogs for three nights near Palm Springs, the Motel 6 in Fresno? Does the weight, dog-count and fee arithmetic for the stay, hotel by hotel, against each hotel's published pet policy. It answers for stays at specific hotels, not for a chain's policy in general, and it lists no other kind of place. Inputs: query (hotel name, city or brand), brand, county without "County", state "CA" or "NV", area (lake-tahoe, big-sur, east-bay), region, or near={lat, lon}; dog_weight_lb, dogs, nights, max_total_fee. Each hotel is a match, a possible (needs a call: case by case, weight unstated, "up to" fee) or excluded, with the arithmetic spelled out, the source URL and verified date. Amounts are pet fees, never room rates: there are no room prices here. Examples: - "Will a Monterey hotel take my 70 lb Lab for under $50?" -> county="Monterey", dog_weight_lb=70, max_total_fee=50 - "Two dogs, three nights near Palm Springs" -> near={lat:33.83, lon:-116.55}, dogs=2, nights=3 - "Is the Motel 6 in Fresno dog friendly?" -> query="Motel 6 Fresno" - "A hotel near LAX for my dog" -> query="LAX" (an airport code or name searches 5 miles around the airport) - "A Las Vegas hotel for my 60 lb dog" -> county="Clark", state="NV", dog_weight_lb=60

    Annotations the server declares

    • title: Find hotels for a dog
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_get_brand_policyWhat is this hotel chain's pet policy: how many pets, weight limit, fee, exceptions?No findings

    Why it is in this group

    • The name "dogpolicies_get_brand_policy" says "get": a word for reading.
    Description, as the server wrote it
    What is this hotel chain's pet policy: how many pets, weight limit, fee, exceptions? Answers chain-wide questions such as "What is Motel 6's pet policy?" or "Does Kimpton charge a pet fee?"; it does not work out one hotel's fee for a stay or say whether that hotel confirmed the chain policy. Brands covered: Best Western (best-western), Extended Stay America (extended-stay-america), Kimpton Hotels (kimpton), La Quinta by Wyndham (la-quinta), Motel 6 (motel-6), Red Roof Inn (red-roof). Input: brand id or name, e.g. "red-roof" or "Kimpton". Any other chain is not covered. Returns the published policy with the source URL, quote and verified date, and how many California and Nevada properties carry it.

    Annotations the server declares

    • title: Get hotel brand pet policy
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_get_placeWhat are the exact dog rules for this one place, and what is the official source: the quote, the publisher, the date checked?No findings

    Why it is in this group

    • The name "dogpolicies_get_place" says "get": a word for reading.
    Description, as the server wrote it
    What are the exact dog rules for this one place, and what is the official source: the quote, the publisher, the date checked? The leash rule, where dogs may go, fees and limits in full, with the official source and its quote, for one place known by id or name. Input: id as returned in any result (for example "carmel-beach"); an exact name works, and a near miss resolves to the one clear match, labeled resolved_from. An id nothing matches is an answer with did_you_mean, not an error. Returns every rule with display text and rule ids, each source with URL, publisher, capture date and quote, and facts the source does not state listed as not_stated. A place on I-5 in California also carries its position on the road (Caltrans mile, side, distance off the freeway) and any paired exit.

    Annotations the server declares

    • title: Get place details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_get_ruleWhere does this specific rule come from (a fee, a leash rule, a weight limit): what is the exact quote, the source and the date it was verified?No findings

    Why it is in this group

    • The name "dogpolicies_get_rule" says "get": a word for reading.
    Description, as the server wrote it
    Where does this specific rule come from (a fee, a leash rule, a weight limit): what is the exact quote, the source and the date it was verified? Takes one rule id and returns the evidence behind that single fact. Rule ids look like "rul_<place uid>_<kind>" and appear in every place result as rule_records. Returns the rule's value, the source it cites with the quote, confidence, verified date, freshness and the place's citation line.

    Annotations the server declares

    • title: Get one rule by id
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dogpolicies_search_placesCan my dog go to this place, or which parks, beaches, trails, campgrounds or patios allow dogs: "Can I bring my dog to Point Lobos?", "state parks in Marin that allow dogs", "off-l…1 finding

    Why it is in this group

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

    Findings

    • Info

      The description is 2,346 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...-> type="restaurant", open_on="2026-11-26", area="lake-tahoe", dogs_allowed=true"

      What this check looks for
    Description, as the server wrote it
    Can my dog go to this place, or which parks, beaches, trails, campgrounds or patios allow dogs: "Can I bring my dog to Point Lobos?", "state parks in Marin that allow dogs", "off-leash beaches near San Diego"? Answers for one named place or a filtered list of one kind; each result's id names the place's full record, with every rule and source. It is not a roundup of everything dog-friendly in a town, a hotel fee calculation, or a road report. Inputs: query (name, city or brand; words like "cabins", "hikes", "wineries" or "dog friendly hotels in Carmel" are read as the kind and the place), type (lodging, campground incl. RV parks, cabins, beach, park, trail, restaurant, rest_area, stop; "hotel", "dog park" or "hike" are read as these), dogs_allowed, off_leash, meal (breakfast, brunch, lunch or dinner: restaurants that state they serve it), open_on (a date, YYYY-MM-DD: restaurants whose own page says they are open that day, such as Thanksgiving), state "CA" or "NV", county without "County", area (lake-tahoe, big-sur, east-bay), or near={lat, lon}. Each result: yes, yes_restricted, no or varies, the rule in a sentence, verified date, URL and id. No match is an answer (outcome no_match) with did_you_mean, nearest and next. Nevada coverage is thin. Examples: - "Off-leash beaches near San Diego" -> type="beach", off_leash=true, near={lat:32.72, lon:-117.16} - "Can I bring my dog to Point Lobos?" -> query="Point Lobos" - "State parks in Marin County that allow dogs" -> type="park", county="Marin", dogs_allowed=true - "Lake Tahoe beaches in Nevada that allow dogs" -> type="beach", state="NV", dogs_allowed=true - "Off-leash dog parks in Las Vegas" -> type="park", off_leash=true, county="Clark", state="NV" - "RV parks in Fresno County that take dogs" -> type="campground", county="Fresno", dogs_allowed=true - "Dog-friendly cabins in June Lake" -> type="cabins", query="June Lake", dogs_allowed=true (query="June Lake cabins" works too) - "Restaurants with a dog-friendly patio in Alameda" -> type="restaurant", query="Alameda" - "Where can I take my dog to breakfast at Lake Tahoe?" -> type="restaurant", meal="breakfast", area="lake-tahoe", dogs_allowed=true - "Lake Tahoe restaurants open on Thanksgiving that allow dogs" -> type="restaurant", open_on="2026-11-26", area="lake-tahoe", dogs_allowed=true

    Annotations the server declares

    • title: Search places
    • readOnlyHint: true
    • destructiveHint: false
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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 16, 2026, 14:22 UTC, unchanged since Nov 16, 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
10
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
  • WarnThe whole server

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

    Matched text

    https://dogpolicies.com/mcp/: tools/list returned 17 tools to an anonymous client, including dogpolicies_near (write), dogpolicies_plan_trip (write), dogpolicies_route_stops (write), dogpolicies_i5_corridor (write), dogpolicies_i5_conditions (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 16, 2026
    • Tools that change things, listed without credentials: 8 to 10
  2. Nov 9, 2026
    • Tools that change things, listed without credentials: 12 to 8

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "dogpolicies_route_stops" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "dogpolicies_route_stops" says "stop": a word for a change.

    What this check looks for
  • The server marks "dogpolicies_subscribe_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "dogpolicies_subscribe_changes" says "subscribe": a word for a change.

    What this check looks for
  • The description is 2,346 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...-> type="restaurant", open_on="2026-11-26", area="lake-tahoe", dogs_allowed=true"

    What this check looks for

History

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

  1. Tools6 changed.~6 changedView diff
  2. Tools1 added, 1 changed.+1 added~1 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 10.View diff
    • Tools that change things, listed without credentials: 8 to 10
  4. Tools2 added, 15 changed.+2 added~15 changedView diff
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 12 -> 8.View diff
    • Tools that change things, listed without credentials: 12 to 8
  6. Tools9 changed.~9 changedView diff
  7. Tools2 added, 3 changed.+2 added~3 changedView diff
  8. Tools13 removed, 13 changed.−13 removed~13 changedView diff

Install

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

claude mcp add --transport http dogpolicies https://dogpolicies.com/mcp/
claude mcp add --transport http dogpolicies https://dogpolicies.com/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__dogpolicies__dogpolicies_search_places",
      "mcp__dogpolicies__dogpolicies_get_place",
      "mcp__dogpolicies__dogpolicies_compare_places",
      "mcp__dogpolicies__dogpolicies_find_hotels",
      "mcp__dogpolicies__dogpolicies_get_brand_policy",
      "mcp__dogpolicies__dogpolicies_browse_answers",
      "mcp__dogpolicies__dogpolicies_get_rule"
    ],
    "ask": [
      "mcp__dogpolicies__dogpolicies_near",
      "mcp__dogpolicies__dogpolicies_plan_trip",
      "mcp__dogpolicies__dogpolicies_route_stops",
      "mcp__dogpolicies__dogpolicies_i5_corridor",
      "mcp__dogpolicies__dogpolicies_i5_conditions",
      "mcp__dogpolicies__dogpolicies_road_conditions",
      "mcp__dogpolicies__dogpolicies_emergency_vet",
      "mcp__dogpolicies__dogpolicies_changes_since",
      "mcp__dogpolicies__dogpolicies_changes_near",
      "mcp__dogpolicies__dogpolicies_subscribe_changes",
      "mcp__dogpolicies__dogpolicies_report_correction"
    ],
    "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 dogpolicies. Review it before you use it.

Capability tags behind 2 rules
  • mcp__dogpolicies__dogpolicies_browse_answers untrusted-input
  • mcp__dogpolicies__dogpolicies_report_correction untrusted-input

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/io.github.xultrax-web/dogpolicies-mcp/verify?hash=cf3773267b23d56361aea981269cc4f21298b5e2d249008414f422b4d2c6ee90" | jq -e '.changed == false'

Pinned hash cf3773267b23, from Nov 22, 2026, 02:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.xultrax-web/dogpolicies-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.xultrax-web/dogpolicies-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.xultrax-web/dogpolicies-mcp.svg)](https://radar.anlyon.com/servers/io.github.xultrax-web/dogpolicies-mcp)

Source: MCP Registry · repository. Synced Nov 22, 2026, 02:17 UTC.

DogPolicies MCP server: questions and answers

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

Is the DogPolicies MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 11 of which can change, send or delete something, and 3 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 DogPolicies MCP server delete data?

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

Can the DogPolicies MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DogPolicies MCP server have?

18 tools: 11 write, 7 read. dogpolicies_near, dogpolicies_plan_trip, dogpolicies_route_stops, dogpolicies_i5_corridor, dogpolicies_i5_conditions, dogpolicies_road_conditions, dogpolicies_emergency_vet, dogpolicies_changes_since and 10 more.

Does the DogPolicies MCP server need sign-in or OAuth?

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

Does the DogPolicies MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DogPolicies MCP server changed its tools?

Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 22, 2026. Every change is on this page and in its Atom feed.