Home / MCP registry index / io.github.xultrax-web/dogpolicies-mcp

DogPolicies

io.github.xultrax-web/dogpolicies-mcp in the official MCP registry. Endpoint https://dogpolicies.com/mcp/. Source: github.com/xultrax-web/dogpolicies-mcp.

The registry describes it as: Verified dog rules for California and Nevada travel: parks, beaches, hotels, fees, sourced and dated

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http dogpolicies-mcp https://dogpolicies.com/mcp/

{
  "mcpServers": {
    "dogpolicies-mcp": {
      "url": "https://dogpolicies.com/mcp/"
    }
  }
}

code --add-mcp '{"name":"dogpolicies-mcp","type":"http","url":"https://dogpolicies.com/mcp/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

dogpolicies_search_places dogrulebook_search_places dogpolicies_near dogrulebook_near dogpolicies_get_place dogrulebook_get_place dogpolicies_compare_places dogrulebook_compare_places dogpolicies_plan_trip dogrulebook_plan_trip dogpolicies_find_hotels dogrulebook_find_hotels dogpolicies_get_brand_policy dogrulebook_get_brand_policy dogpolicies_browse_answers dogrulebook_browse_answers dogpolicies_route_stops dogrulebook_route_stops dogpolicies_get_rule dogrulebook_get_rule dogpolicies_changes_since dogrulebook_changes_since dogpolicies_changes_near dogrulebook_changes_near dogpolicies_report_correction dogrulebook_report_correction

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): e39c1a2f7adc6f9f. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-xultrax-web-dogpolicies-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-xultrax-web-dogpolicies-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Travel MCP servers