Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
DogPolicies is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
2k
downloads a day
local
or remote
13
tools declared
What it does
Verified dog rules for California and Nevada travel: parks, beaches, hotels, fees, sourced and dated
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user dogpolicies-mcp '--' npx -y dogpolicies-mcp
# 2 — ask your agent for something these tools do
# dogpolicies_browse_answers, dogpolicies_changes_near, dogpolicies_changes_since and 10 more
DogPolicies costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
XWAll 2 servers
xultrax-web2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user dogpolicies-mcp '--' npx -y dogpolicies-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://dogpolicies.com/mcp/: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http dogpolicies-mcp https://dogpolicies.com/mcp/Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take DOGPOLICIES_OFFLINE (Set to 1 to never use the network (no data refresh, corrections return the web form URL)), DOGPOLICIES_BASE_URL (Site to refresh data from and file corrections to) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | — |
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. Use dogpolicies_changes_since for…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | Date, YYYY-MM-DD |
| outcome | string | no | Only events with this outcome |
| limit | yes | — | |
| offset | yes | — | |
| response_format | yes | — |
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,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | Date, YYYY-MM-DD |
| outcome | string | no | Only events with this outcome |
| limit | yes | — | |
| offset | yes | — | |
| response_format | yes | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Two to six place ids from search results |
| response_format | string | no | 'markdown' for readable text, 'json' for structured data |
Find hotels and motels in California and Nevada that will take a specific dog, with the estimated pet fee for the stay. 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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words in the hotel name, city or brand |
| brand | string | no | Only this hotel brand |
| include_possible | boolean | no | Include hotels that need a call to confirm |
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: ${ctx.graph.brands.map((b) =>
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand | string | yes | Brand id or name |
| response_format | yes | — |
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. Full rules and sources for one place: every fact with its display text, the rules list, and each source with its URL,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Place id, e.g. "fort-funston" |
| response_format | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Rule id, e.g. "rul_t6cqwy0x4ce2dmpq_fee" |
| response_format | yes | — |
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. The one call to make when a user names a place and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| types | array | no | Kinds to include; all by default |
| dogs_allowed_only | boolean | no | Leave out places where dogs are not allowed |
| per_type | integer | no | Nearest results to show per kind |
| response_format | string | no | 'markdown' for readable text, 'json' for structured data |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stay_types | array | no | Kinds of stay to consider |
| include_possible | boolean | no | Include stays that need a call to confirm |
| per_section | integer | no | Results per section |
| response_format | string | no | 'markdown' for readable text, 'json' for structured data |
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.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | yes | Place id from a search result |
| message | string | yes | What is wrong, in the user's words |
| source_url | string | no | — |
| contact | string | no | How to reach the reporter, only if they offer it |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route | string | no | Route id |
| near | object | no | Start from the route mile nearest this point |
| from_mile | number | no | Start at this route mile |
| to_mile | number | no | Stop at this route mile |
| direction | string | no | — |
| kinds | array | no | Kinds of stops to include; all by default |
| dog_friendly_only | boolean | no | Leave out stops where dogs are not allowed |
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.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to match in the name, city, county or brand |
| type | string | no | — |
| dogs_allowed | boolean | no | — |
| off_leash | boolean | no | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DogPolicies or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.2.9 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest46ea59b1016e3b6f786e9fb373e9a15aec06c6574c88d7730e461206ad442691
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest46ea59b1016e3b6f
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.9. Pin a release below and the command asks for exactly that one.
0.2.9
1 Nov 2026
latestNo release note was published with this version.
0.2.7
1 Nov 2026
No release note was published with this version.
0.2.4
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DogPolicies can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.