Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DogPolicies

NPM · DOGPOLICIES-MCP · 2 COMPONENTS

Verified dog rules for California and Nevada travel: parks, beaches, hotels, fees, sourced and dated

84 Trust /100

Last scanned (8 hours ago)

Scores higher than 81% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to xultrax-web/dogpolicies-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 7012 tokens (~152/item across 46 items; 15 tools + 31 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 1.00 ▲ functional
  • 4 Nov 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Schema quality: 122 → 152 ▼ functional
    • Dependency health: 1.00 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Schema quality: excellent → good functional
    • Package version: 0.2.9 → 0.3.0 functional
    • Package version: 0.2.9 → 0.2.10 functional
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 83

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/dogpolicies-mcp@0.3.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo xultrax-web/dogpolicies-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/xultrax-web/dogpolicies-mcp/.github/workflows/publish.yml@refs/tags/v0.3.0
Rekor log index 3691915364
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c5ca3893b7032ed06019a485e15cd7503cd6ea2e5227d42f91c27d2ecffeaf136a040c200d2f24d8065dbc8ef96ecf9f289640385f6beb330f2efe8a9

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~5,877 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
dogpolicies_browse_answers ~153

Ready-made lists that answer common questions (list the state parks, national parks, beaches or hotels that allow dogs), such as "Which California national parks allow dogs?" or "Where can dogs go off leash on California beaches?". Without a slug, lists every question with its slug and result count. With a slug, returns that question's places.

NameTypeReqDescription
limitinteger–Maximum results to return
offsetinteger–Results to skip, for pagination
response_formatstring–'markdown' for readable text, 'json' for structured data
slugstring–Question slug from the list, e.g. "off-leash-dog-beaches-california"
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
licenseobjectyes–
placesarray––
questionsarray––
totalnumberyes–

No examples provided.

dogpolicies_changes_near ~263

Verification events (confirmed, changed, source gone, blocked, disputed) since a date for places within a radius of a town, county or point, newest first. The way to answer "has anything changed around Tahoe since my last trip?" or to re-check a saved itinerary. Example: "What changed near Monterey since September?" -> place="Monterey", since="2026-09-01"

NameTypeReqDescription
limitinteger–Maximum results to return
nearobject–A point instead of a town; give one of place or near
offsetinteger–Results to skip, for pagination
outcomestring–Only events with this outcome
placestring–A city, county or area in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay" or "Lake Tahoe"
radius_milesnumber–Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)
response_formatstring–'markdown' for readable text, 'json' for structured data
sincestringyesDate, YYYY-MM-DD
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
countnumberyes–
eventsarrayyes–
has_morebooleanyes–
labelstringyes–
licenseobjectyes–
radius_milesnumberyes–
totalnumberyes–

No examples provided.

dogpolicies_changes_since ~144

Everything that changed in the whole data set since a date: verification events and rule changes everywhere, newest first, so an agent can poll cheaply instead of re-reading every record. Each entry names the place, what happened (confirmed, changed, source_gone, blocked, disputed), who checked, and links the record.

NameTypeReqDescription
limitinteger–Maximum results to return
offsetinteger–Results to skip, for pagination
outcomestring–Only events with this outcome
response_formatstring–'markdown' for readable text, 'json' for structured data
sincestringyesDate, YYYY-MM-DD
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
countnumberyes–
eventsarrayyes–
has_morebooleanyes–
licenseobjectyes–
rule_changesarrayyes–
totalnumberyes–

No examples provided.

dogpolicies_compare_places ~150

Which one is better for a dog? Compare two to six places on the facts that decide a dog trip: dogs allowed, leash rule, where dogs may go, pet fee, weight limit, pets per room, restrictions, plus confidence, freshness and who confirmed each record. One row per fact, one column per place, every place with its citation. Answers "which one?" between candidates; ids come from any search result. Example: ids=["carmel-beach","asilomar-state-beach"].

NameTypeReqDescription
idsarrayyesTwo to six place ids from search results
response_formatstring–'markdown' for readable text, 'json' for structured data
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
licenseobjectyes–
placesarrayyes–
rowsarrayyes–

No examples provided.

dogpolicies_find_hotels ~575

Find hotels and motels in California and Nevada that will take a specific dog, with the estimated pet fee for the stay. Every amount is the hotel's pet fee, never the room rate: DogPolicies has no room prices. Each hotel is sorted into "match" (the policy says yes on everything asked), "possible" (nothing rules it out, but something needs a call: a hotel that decides case by case, an unstated weight limit, a limit the hotel lifts with its approval, an "up to" fee) or excluded (left out). Matches come first, cheapest pet fee first. The fee arithmetic is spelled out for every result. 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 Las Vegas hotel for my 60 lb dog" -> county="Clark", state="NV", dog_weight_lb=60

NameTypeReqDescription
areastring–Area id, the name a traveler gives the trip: san-francisco, east-bay, peninsula, south-bay, north-bay, lake-tahoe, big-sur, mendocino-coast, yosemite, death-valley
brandstring–Only this hotel brand
countystring–County name without "County", in California or Nevada, e.g. "Monterey" or "Washoe"
dog_weight_lbnumber–The dog's weight in pounds
dogsinteger–Number of dogs
include_possibleboolean–Include hotels that need a call to confirm
limitinteger–Maximum results to return
max_total_feenumber–Most the guest will pay in pet fees for the whole stay, USD
nearobject–Limit to places near a point; results are sorted by distance
nightsinteger–Nights of the stay
offsetinteger–Results to skip, for pagination
querystring–Words in the hotel name, city or brand
regionstring–Region id, e.g. central-coast, san-diego or reno-tahoe-nevada
response_formatstring–'markdown' for readable text, 'json' for structured data
statestring–"CA" or "NV". Also tells apart counties with the same name, such as Humboldt.
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
countnumberyes–
countsobjectyes–
has_morebooleanyes–
hotelsarrayyes–
licenseobjectyes–
offsetnumberyes–
totalnumberyes–

No examples provided.

dogpolicies_get_brand_policy ~142

A hotel chain's published pet policy: pets per room, weight limit, fee, rules, listed exceptions and how many California and Nevada properties carry it. 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). Example: brand="red-roof" or brand="Kimpton".

NameTypeReqDescription
brandstringyesBrand id or name
response_formatstring–'markdown' for readable text, 'json' for structured data
NameTypeReqDescription
answerstringyes–
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
factsarrayyes–
idstringyes–
licenseobjectyes–
namestringyes–
not_statedarrayyesExpected facts the sources do not state; never guess these
source_urlsarrayyes–
urlstringyes–
verified_atstringyes–

No examples provided.

dogpolicies_get_place ~202

The full record for one place you already know by id: every dog rule with its display text, the rules list, and each source with its URL, publisher, capture date and quote. A place on I-5 in California also carries its axis position (s meters from San Ysidro on the I-5 centerline, Caltrans mile, meters off the road, side of northbound travel, road elevation, strip) and, when it is the dog side of a paired stop, that pair: the exit and the people-stops near it (counted from OpenStreetMap, never named, not verified for restrooms). Takes a place id, as returned in every search result. Example: id="carmel-beach".

NameTypeReqDescription
idstringyesPlace id, e.g. "fort-funston"
response_formatstring–'markdown' for readable text, 'json' for structured data
NameTypeReqDescription
answerstringyes–
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
axis–yesWhere the place sits on the I-5 axis: s meters from San Ysidro, Caltrans mile, meters off the road, side of northbound travel, road elevation, strip; null off I-5
citationstringyesCopy-ready citation: answer, source, date checked, record URL, license
confidencestringyesstated: the place's own source says it; inferred_from_agency: an agency-wide rule; inherited_brand: the chain's policy, not confirmed by this hotel
confirmed_by–yes–
factsarrayyes–
freshnessstringyesfresh: inside its review interval; due: past it; stale: past twice it, confirm before you go; unreadable: the last check could not read the source
idstringyes–
licenseobjectyes–
namestringyes–
not_statedarrayyesExpected facts the sources do not state; never guess these
paired_stop–yes–
record_licensestringyes–
review_duestringyes–
rule_recordsarrayyes–
rulesarrayyes–
source_urlsarrayyes–
sourcesarrayyes–
statusstringyes–
typestringyes–
uidstringyesStable id that survives a rename
urlstringyes–
verified_atstringyes–

No examples provided.

dogpolicies_get_rule ~135

One rule (a fee, a leash rule, a weight limit) by its stable id, with its value, the source it cites, the quote, its confidence, the date it was verified and its freshness, plus the place's citation line. Rule ids look like "rul_<place uid>_<kind>" and appear in every place result as rule_records.

NameTypeReqDescription
idstringyesRule id, e.g. "rul_t6cqwy0x4ce2dmpq_fee"
response_formatstring–'markdown' for readable text, 'json' for structured data
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
licenseobjectyes–
placeobjectyes–
ruleobjectyes–

No examples provided.

dogpolicies_i5_conditions ~331

Current Caltrans lane closures, road-weather station readings, changeable-message-sign text and chain-control status on I-5 in California, each placed on the I-5 centerline (s meters from San Ysidro and the Caltrans mile) and matched to the nearest DogPolicies dog stop. Conditions come from Caltrans' CWWP2 feeds fetched within the last 15 minutes (fetched_at in the result) and are not verified rules. The window is a mile range (from_mile, to_mile) or a point with a direction and ahead_miles; with none, the whole of I-5 in California. Needs the network (the document is read from dogpolicies.com); offline the result is an error with code offline. 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

NameTypeReqDescription
ahead_milesnumber–Window in miles from near
directionstring–Direction of travel from near
from_milenumber–Start of a mile range
nearobject–A point on or near I-5
response_formatstring–'markdown' for readable text, 'json' for structured data
to_milenumber–End of a mile range
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
chain_controlsarrayyes–
chains_in_effectbooleanyes–
closuresarrayyes–
fetched_atstringyes–
licenseobjectyes–
noticestringyes–
signsarrayyes–
sourceobjectyes–
weatherarrayyes–
window–yes–

No examples provided.

dogpolicies_i5_corridor ~747

The I-5 corridor in California as eleven named stretches (strips) on the I-5 centerline, from San Ysidro (s = 0 m) to the Oregon line (s ≈ 1,281,400 m), and the dog stops in any stretch, mile range or window ahead of a point. Every stop carries its s in meters from San Ysidro, its Caltrans odometer mile, the side of the road it serves (right or left of northbound travel, or both), its distance off the freeway, the road's elevation, and restrooms, water, pet area, dog park and hours as its official source states them. A family stop is one whose official source states restrooms and a pet area or dog park. A paired stop is a freeway exit with places to stop for people nearby (located through OpenStreetMap, counted by kind, never named and not verified for restrooms) matched to the nearest DogPolicies place that allows dogs within about a mile, with its rule and source. With no stretch, miles or point, the result is the list of stretches with their s and mile ranges and stop counts. Strips: sandiego (San Ysidro → Camp Pendleton), orange-la (Camp Pendleton → East LA), grapevine (East LA → Wheeler Ridge), kern-westside (Wheeler Ridge → Kettleman), westside (Kettleman → Santa Nella), delta (Santa Nella → Stockton), sacramento (Stockton → Woodland), valley (Woodland → Williams), tehama (Williams → Red Bluff), shasta (Red Bluff → Mt Shasta), siskiyou (Mt Shasta → Siskiyou Summit). Examples: - "What is between the Grapevine and Kettleman?" -> strip="grapevine" (East LA to Wheeler Ridge) and strip="kern-westside" (Wheeler Ridge to Kettleman) - "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 - "Exits with somewhere for people and a park for the dog in the Sacramento stretch" -> strip="sacramento", paired=true

NameTypeReqDescription
ahead_milesnumber–Window in miles from near in the direction of travel
directionstring–Direction of travel from near; north means increasing s
dog_friendly_onlyboolean–Leave out stops where dogs are not allowed
familyboolean–Only family stops
from_milenumber–Start of a mile range (Caltrans odometer)
kindsarray–Kinds of stops to include; all by default
limitinteger–Maximum stops to return
nearobject–A point on or near I-5; the window starts at the nearest point of the road
offsetinteger–Stops to skip
pairedboolean–Also list the paired stops in the window
response_formatstring–'markdown' for readable text, 'json' for structured data
stripstring–A stretch by id (sandiego, orange-la, grapevine, kern-westside, westside, delta, sacramento, valley, tehama, shasta, siskiyou)
to_milenumber–End of a mile range
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
axis_versionstringyes–
licenseobjectyes–
paired_stopsarrayyes–
stopsarrayyes–
stripsarrayyes–
totalnumberyes–
window–yes–

No examples provided.

dogpolicies_near ~345

Anything for dogs around a town, county or point: everything dog-related nearby, grouped by kind: beaches, parks, trails, hotels, campgrounds, cabins, places to eat and rest areas, each sorted by distance, with the dog rule and citation for each. Answers "what can I do with my dog there?" for a named place. Takes a town or county name (no coordinates needed) or a point. 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 within 5 miles of here" -> near={lat:36.6, lon:-121.9}, radius_miles=5

NameTypeReqDescription
dogs_allowed_onlyboolean–Leave out places where dogs are not allowed
nearobject–A point instead of a town; give one of place or near
per_typeinteger–Nearest results to show per kind
placestring–A city, county or area in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay" or "Lake Tahoe"
radius_milesnumber–Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)
response_formatstring–'markdown' for readable text, 'json' for structured data
typesarray–Kinds to include; all by default
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
centerobjectyes–
groupsarrayyes–
labelstringyes–
licenseobjectyes–
radius_milesnumberyes–
totalnumberyes–

No examples provided.

dogpolicies_plan_trip ~550

Plan a stay in a California or Nevada town with a dog, in one call: where to stay (hotels, campgrounds and cabins that will take this dog, with the pet fee for the whole stay worked out), what to do (beaches, parks and trails that allow dogs, nearest first) and where to eat (patios that take dogs), every item with its citation. When the town is within 10 miles of I-5 in California, the result also carries the drive leg on the I-5 axis: the town's position (Caltrans mile and s meters from San Ysidro), the next family stops (restrooms and a pet area or dog park stated by their official source) in each direction within 60 miles, and the paired stops (an exit with people-stops nearby, counted from OpenStreetMap and never named, matched to the nearest dog-legal place) within 10 miles. Inputs: the town or county and the dog: weight, how many dogs, nights, and the most the user will pay in pet fees. 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"]

NameTypeReqDescription
dog_weight_lbnumber–The dog's weight in pounds
dogsinteger–Number of dogs
include_possibleboolean–Include stays that need a call to confirm
max_total_feenumber–Most the guest will pay in pet fees for the whole stay, USD
nearobject–A point instead of a town; give one of place or near
nightsinteger–Nights of the stay
per_sectioninteger–Results per section
placestring–A city, county or area in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay" or "Lake Tahoe"
radius_milesnumber–Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)
response_formatstring–'markdown' for readable text, 'json' for structured data
stay_typesarray–Kinds of stay to consider
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
askedobjectyes–
attribution_textstringyes–
attribution_urlstringyes–
i5–yesWhen the town is within 10 miles of I-5 in California: the trip's position on the I-5 axis, the next family stops in each direction within 60 miles, and the paired stops within 10 miles
labelstringyes–
licenseobjectyes–
outingsarrayyes–
radius_milesnumberyes–
stay_countsobjectyes–
staysarrayyes–

No examples provided.

dogpolicies_report_correction ~183

File a correction when a user says a rule on a record is wrong or has changed (a fee went up, a beach closed to dogs, a hotel now takes two pets). The report goes to a person who re-reads the official source; nothing is published automatically and the record does not change until it is verified. Takes the place id, a sentence or two on what is wrong, and optionally the official page the user saw. The only personal detail it accepts is an optional contact the user offers.

NameTypeReqDescription
contactstring–How to reach the reporter, only if they offer it
messagestringyesWhat is wrong, in the user's words
place_idstringyesPlace id from a search result
source_urlstring–The official page that shows the current rule, if the user has it
NameTypeReqDescription
place_idstringyes–
report_idstring|nullyes–
statusstringyes–
urlstringyes–

No examples provided.

dogpolicies_route_stops ~1,326

Dog-friendly stops along a California or Nevada highway, in driving order: rest areas (Caltrans rest areas with pet areas; Nevada rest areas, where leashed dogs are allowed), travel stops with dog parks, hotels, cabin resorts and campgrounds or RV parks near the road (all checked against the dog's weight and the pet-fee budget) and parks or beaches that allow dogs. Each stop has its mile on the route and its distance off the road. Each route covers one state and stops at the state line. California miles follow the Caltrans odometer: north on I-5 (from the Mexican border), US-101 (from Los Angeles), Highway 1 (from Dana Point) and I-15 (i-15, San Diego to Primm); east on I-80 (i-80, San Francisco to the Nevada line) and US-50 (us-50, West Sacramento to Stateline). Nevada routes count Nevada mileposts from the California line, matching the exit numbers: north on I-15 (i-15-nevada), east on I-80 (i-80-nevada) and US-50 (us-50-nevada, Stateline to Utah); north on US-95 (us-95-nevada, California line to Oregon) and US-93 (us-93-nevada, Hoover Dam to Idaho), whose miles include the stretches they share with other highways. Where Highway 1 runs on US-101, stops on that stretch say so in on_road. A starting point is set with from_mile or near, plus a direction; ahead_miles limits the window to that many miles from the start in the direction of travel. On I-5 in California each stop also carries its position on the I-5 centerline in meters from San Ysidro (s_m), miles_ahead of the start along the direction of travel, the side of the road it serves (right or left of northbound travel, or both), its distance off the freeway, the road's elevation in meters and the stretch (strip) it is in, plus restrooms, water, pet_area, dog_park and hours as its official source states them. With family=true only stops whose official source states restrooms and a pet area or dog park are returned. With paired=true the result also lists paired stops: a freeway exit in the window with places…

NameTypeReqDescription
ahead_milesnumber–Window in miles from the start (near or from_mile) in the direction of travel; an alternative to to_mile
directionstring–Direction of travel. Route miles increase going north, or east on I-80 and US-50; north and east both mean increasing miles
dog_friendly_onlyboolean–Leave out stops where dogs are not allowed
dog_weight_lbnumber–The dog's weight in pounds
dogsinteger–Number of dogs
familyboolean–Only stops whose official source states restrooms and a pet area or dog park (I-5 in California)
from_milenumber–Start at this route mile
kindsarray–Kinds of stops to include; all by default
limitinteger–Maximum results to return
max_total_feenumber–Most the guest will pay in pet fees for the whole stay, USD
nearobject–Start from the route mile nearest this point
nightsinteger–Nights of the stay
offsetinteger–Results to skip, for pagination
pairedboolean–Also list the paired stops in the window: an exit with people-stops nearby and the nearest dog-legal place (I-5 in California)
response_formatstring–'markdown' for readable text, 'json' for structured data
routestring–Route id
to_milenumber–Stop at this route mile
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
countnumberyes–
guidestringyes–
has_morebooleanyes–
licenseobjectyes–
offsetnumberyes–
paired_stopsarray––
routestringyes–
startobject––
stopsarrayyes–
totalnumberyes–

No examples provided.

dogpolicies_search_places ~631

Search parks, beaches, trails, hotels, campgrounds and cabin resorts in California and Nevada by name, location and dog rules. Returns one page of places with a one-line answer ("Yes, on a leash no longer than 6 feet."), status (yes, yes_restricted, no, varies), verification date and page URL. Each result includes the place id. 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 - "Restaurants with a dog-friendly patio in Alameda" -> type="restaurant", query="Alameda"

NameTypeReqDescription
areastring–Area id, the name a traveler gives the trip: san-francisco, east-bay, peninsula, south-bay, north-bay, lake-tahoe, big-sur, mendocino-coast, yosemite, death-valley
countystring–County name without "County", in California or Nevada, e.g. "Monterey" or "Washoe"
dogs_allowedboolean–true: only places that allow dogs somewhere; false: only places that do not
limitinteger–Maximum results to return
nearobject–Limit to places near a point; results are sorted by distance
off_leashboolean–true: only places where the managing agency allows dogs off leash, at least at some times
offsetinteger–Results to skip, for pagination
querystring–Words to match in the name, city, county or brand
regionstring–Region id, e.g. central-coast, san-diego or reno-tahoe-nevada
response_formatstring–'markdown' for readable text, 'json' for structured data
statestring–"CA" or "NV". Also tells apart counties with the same name, such as Humboldt.
typestring–Kind of place; campground covers campgrounds and RV parks (some also rent cabins), cabins covers cabin resorts with no campground, restaurant covers restaurants, cafes, bars, breweries and tasting ro…
NameTypeReqDescription
as_ofstringyesDate the data was built (YYYY-MM-DD)
attribution_textstringyes–
attribution_urlstringyes–
countnumberyes–
has_morebooleanyes–
licenseobjectyes–
offsetnumberyes–
placesarrayyes–
totalnumberyes–

No examples provided.

Install

How do I install the DogPolicies MCP server?

DogPolicies runs locally as an npm package, launched with npx -y dogpolicies-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · dogpolicies-mcp

# add to Claude Code
claude mcp add xultrax-web-dogpolicies-mcp -- npx -y dogpolicies-mcp
Common questions

What is the DogPolicies MCP server?

DogPolicies is an MCP server listed in the public MCP registry as io.github.xultrax-web/dogpolicies-mcp. Verified dog rules for California and Nevada travel: parks, beaches, hotels, fees, sourced and dated. This page covers its npm package (dogpolicies-mcp).

Is the DogPolicies MCP server safe to use?

DogPolicies scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DogPolicies MCP server expose?

DogPolicies exposes 15 tools: dogpolicies_search_places, dogpolicies_near, dogpolicies_get_place, dogpolicies_compare_places, dogpolicies_plan_trip, and 10 more. Their descriptions and schemas cost roughly 5,877 tokens of context every time the server is loaded.

Is the DogPolicies MCP server still maintained?

DogPolicies is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the DogPolicies MCP server under?

DogPolicies declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.