MCP servers › io.github.xultrax-web › dogpolicies-mcp

MCP server · registry snapshot 2026-11-01 · last tested 2026-11-01

io.github.xultrax-web/dogpolicies-mcp

DogPolicies — the publisher's title

by xultrax-web · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗

Verified dog rules for California and Nevada travel: parks, beaches, hotels, fees, sourced and dated — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-11-01version 0.2.9JavaScriptMITstandard input/output, streamable HTTP26 tools

Summary

io.github.xultrax-web/dogpolicies-mcp is a remote and local MCP server listed in the official MCP registry at version 0.2.9, under the namespace of the GitHub account xultrax-web. Its linked repository, github.com/xultrax-web/dogpolicies-mcp, belongs to the same GitHub account. On 2026-11-01 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 30 resources and 5 prompts.

Record checks

9 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: no download figure available
Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote and local package
Transport: standard input/output, streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 26
Last tested: 2026-11-01

Tool list size

23,184 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (26 tools). Counted with Anthropic's token counter on 2026-11-01, from the tool list we read on 2026-11-01. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-01 (dogpolicies.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.2.9).

Add to your client

Worth knowing before you connect it

Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-11-01

Mode

read-only (no tool calls)

Latest version

0.2.9, published 2026-11-01 (registry, as of the 2026-11-01 snapshot)

First listed version

2026-11-01 (earliest version still in the registry; older removed versions would be earlier)

Version history

9 versions listed, all on 2026-11-01; 9 in the 90 days before the 2026-11-01 snapshot.

Most recent 9 versions

0.2.9 · 2026-11-01
0.2.8 · 2026-11-01
0.2.7 · 2026-11-01
0.2.6 · 2026-11-01
0.2.5 · 2026-11-01
0.2.4 · 2026-11-01
0.2.3 · 2026-11-01
0.2.2 · 2026-11-01
0.2.1 · 2026-11-01

(versions still listed in the registry only)

Registry data

snapshot 2026-11-01

Package and repository

checked 2026-11-01

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-31, listed on 2026-11-01 with version 0.2.9 (published 2026-11-01).

Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01.

What it is

What does this server offer?

Observed inventory

26tools

30resources

5prompts

None of its 26 tools are described as changing anything. For 26 the reading was uncertain, so no mark is shown.

dogpolicies_search_places
“Search parks, beaches, trails, hotels, campgrounds and cabin resorts in California and Nevada by name, location and dog rules.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
12 inputs
- querystring“Words to match in the name, city, county or brand”
- typestring“Kind of place; campground covers campgrounds and RV parks (some also rent cabins), cabins covers cabin resorts with no campground, restaurant covers restaurant…”
- dogs_allowedboolean“true: only places that allow dogs somewhere; false: only places that do not”
- off_leashboolean“true: only places where the managing agency allows dogs off leash, at least at some times”
- statestring“"CA" or "NV".”
- countystring“County name without "County", in California or Nevada, e.g.”
- regionstring“Region id, e.g.”
- 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-va…”
- nearobject“Limit to places near a point; results are sorted by distance”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_search_places
“Alias of dogpolicies_search_places, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
12 inputs
- querystring“Words to match in the name, city, county or brand”
- typestring“Kind of place; campground covers campgrounds and RV parks (some also rent cabins), cabins covers cabin resorts with no campground, restaurant covers restaurant…”
- dogs_allowedboolean“true: only places that allow dogs somewhere; false: only places that do not”
- off_leashboolean“true: only places where the managing agency allows dogs off leash, at least at some times”
- statestring“"CA" or "NV".”
- countystring“County name without "County", in California or Nevada, e.g.”
- regionstring“Region id, e.g.”
- 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-va…”
- nearobject“Limit to places near a point; results are sorted by distance”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_near
“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 dis…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- placestring“A city, county or area in California or Nevada, e.g.”
- nearobject“A point instead of a town; give one of place or near”
- radius_milesnumber“Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)”
- typesarray“Kinds to include; all by default”
- dogs_allowed_onlyboolean“Leave out places where dogs are not allowed”
- per_typeinteger“Nearest results to show per kind”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_near
“Alias of dogpolicies_near, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- placestring“A city, county or area in California or Nevada, e.g.”
- nearobject“A point instead of a town; give one of place or near”
- radius_milesnumber“Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)”
- typesarray“Kinds to include; all by default”
- dogs_allowed_onlyboolean“Leave out places where dogs are not allowed”
- per_typeinteger“Nearest results to show per kind”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_get_place
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idstringrequired“Place id, e.g.”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_get_place
“Alias of dogpolicies_get_place, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idstringrequired“Place id, e.g.”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_compare_places
“Which one is better for a dog?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idsarrayrequired“Two to six place ids from search results”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_compare_places
“Alias of dogpolicies_compare_places, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idsarrayrequired“Two to six place ids from search results”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_plan_trip
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
11 inputs
- placestring“A city, county or area in California or Nevada, e.g.”
- nearobject“A point instead of a town; give one of place or near”
- radius_milesnumber“Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)”
- dog_weight_lbnumber“The dog's weight in pounds”
- dogsinteger“Number of dogs”
- nightsinteger“Nights of the stay”
- max_total_feenumber“Most the guest will pay in pet fees for the whole stay, USD”
- stay_typesarray“Kinds of stay to consider”
- include_possibleboolean“Include stays that need a call to confirm”
- per_sectioninteger“Results per section”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_plan_trip
“Alias of dogpolicies_plan_trip, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
11 inputs
- placestring“A city, county or area in California or Nevada, e.g.”
- nearobject“A point instead of a town; give one of place or near”
- radius_milesnumber“Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)”
- dog_weight_lbnumber“The dog's weight in pounds”
- dogsinteger“Number of dogs”
- nightsinteger“Nights of the stay”
- max_total_feenumber“Most the guest will pay in pet fees for the whole stay, USD”
- stay_typesarray“Kinds of stay to consider”
- include_possibleboolean“Include stays that need a call to confirm”
- per_sectioninteger“Results per section”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_find_hotels
“Find hotels and motels in California and Nevada that will take a specific dog, with the estimated pet fee for the stay.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
15 inputs
- querystring“Words in the hotel name, city or brand”
- brandstring“Only this hotel brand”
- dog_weight_lbnumber“The dog's weight in pounds”
- dogsinteger“Number of dogs”
- nightsinteger“Nights of the stay”
- max_total_feenumber“Most the guest will pay in pet fees for the whole stay, USD”
- include_possibleboolean“Include hotels that need a call to confirm”
- statestring“"CA" or "NV".”
- countystring“County name without "County", in California or Nevada, e.g.”
- regionstring“Region id, e.g.”
- 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-va…”
- nearobject“Limit to places near a point; results are sorted by distance”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_find_hotels
“Alias of dogpolicies_find_hotels, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
15 inputs
- querystring“Words in the hotel name, city or brand”
- brandstring“Only this hotel brand”
- dog_weight_lbnumber“The dog's weight in pounds”
- dogsinteger“Number of dogs”
- nightsinteger“Nights of the stay”
- max_total_feenumber“Most the guest will pay in pet fees for the whole stay, USD”
- include_possibleboolean“Include hotels that need a call to confirm”
- statestring“"CA" or "NV".”
- countystring“County name without "County", in California or Nevada, e.g.”
- regionstring“Region id, e.g.”
- 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-va…”
- nearobject“Limit to places near a point; results are sorted by distance”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”

Show 14 more tools

dogpolicies_get_brand_policy
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- brandstringrequired“Brand id or name”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_get_brand_policy
“Alias of dogpolicies_get_brand_policy, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- brandstringrequired“Brand id or name”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_browse_answers
“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 of…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- slugstring“Question slug from the list, e.g.”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_browse_answers
“Alias of dogpolicies_browse_answers, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- slugstring“Question slug from the list, e.g.”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_route_stops
“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 pa…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
14 inputs
- routestring“Route id”
- nearobject“Start from the route mile nearest this point”
- from_milenumber“Start at this route mile”
- to_milenumber“Stop at this route mile”
- directionstring“Direction of travel.”
- kindsarray“Kinds of stops to include; all by default”
- dog_friendly_onlyboolean“Leave out stops where dogs are not allowed”
- dog_weight_lbnumber“The dog's weight in pounds”
- dogsinteger“Number of dogs”
- nightsinteger“Nights of the stay”
- max_total_feenumber“Most the guest will pay in pet fees for the whole stay, USD”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_route_stops
“Alias of dogpolicies_route_stops, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
14 inputs
- routestring“Route id”
- nearobject“Start from the route mile nearest this point”
- from_milenumber“Start at this route mile”
- to_milenumber“Stop at this route mile”
- directionstring“Direction of travel.”
- kindsarray“Kinds of stops to include; all by default”
- dog_friendly_onlyboolean“Leave out stops where dogs are not allowed”
- dog_weight_lbnumber“The dog's weight in pounds”
- dogsinteger“Number of dogs”
- nightsinteger“Nights of the stay”
- max_total_feenumber“Most the guest will pay in pet fees for the whole stay, USD”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_get_rule
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idstringrequired“Rule id, e.g.”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_get_rule
“Alias of dogpolicies_get_rule, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idstringrequired“Rule id, e.g.”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_changes_since
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- sincestringrequired“Date, YYYY-MM-DD”
- outcomestring“Only events with this outcome”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_changes_since
“Alias of dogpolicies_changes_since, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- sincestringrequired“Date, YYYY-MM-DD”
- outcomestring“Only events with this outcome”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_changes_near
“Verification events (confirmed, changed, source gone, blocked, disputed) since a date for places within a radius of a town, county or point, newest first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs, 1 required
- placestring“A city, county or area in California or Nevada, e.g.”
- nearobject“A point instead of a town; give one of place or near”
- radius_milesnumber“Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)”
- sincestringrequired“Date, YYYY-MM-DD”
- outcomestring“Only events with this outcome”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogrulebook_changes_near
“Alias of dogpolicies_changes_near, kept for older clients.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs, 1 required
- placestring“A city, county or area in California or Nevada, e.g.”
- nearobject“A point instead of a town; give one of place or near”
- radius_milesnumber“Search radius in miles around the town or point (an area is its own boundary; the radius is ignored)”
- sincestringrequired“Date, YYYY-MM-DD”
- outcomestring“Only events with this outcome”
- limitinteger“Maximum results to return”
- offsetinteger“Results to skip, for pagination”
- response_formatstring“'markdown' for readable text, 'json' for structured data”
dogpolicies_report_correction
“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).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 2 required
- place_idstringrequired“Place id from a search result”
- messagestringrequired“What is wrong, in the user's words”
- source_urlstring“The official page that shows the current rule, if the user has it”
- contactstring“How to reach the reporter, only if they offer it”
dogrulebook_report_correction
“Alias of dogpolicies_report_correction, kept for older clients.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 2 required
- place_idstringrequired“Place id from a search result”
- messagestringrequired“What is wrong, in the user's words”
- source_urlstring“The official page that shows the current rule, if the user has it”
- contactstring“How to reach the reporter, only if they offer it”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-01.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 176
Tools with a description: 100% of 26
Typical description length: 739 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 27,352 tokens for an agent to load (characters ÷ 4)
Naming: 26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package dogpolicies-mcp

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "dogpolicies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dogpolicies-mcp@0.2.9"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "dogpolicies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dogpolicies-mcp@0.2.9"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "dogpolicies-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "dogpolicies-mcp@0.2.9"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"dogpolicies-mcp","type":"stdio","command":"npx","args":["-y","dogpolicies-mcp@0.2.9"]}'

Claude Code

claude mcp add --transport stdio dogpolicies-mcp -- npx -y dogpolicies-mcp@0.2.9

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "dogpolicies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dogpolicies-mcp@0.2.9"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "dogpolicies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dogpolicies-mcp@0.2.9"
      ]
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.dogpolicies-mcp]
command = "npx"
args = ["-y", "dogpolicies-mcp@0.2.9"]

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "dogpolicies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dogpolicies-mcp@0.2.9"
      ]
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y dogpolicies-mcp@0.2.9

Optional settings the entry also lists (left out above): DOGPOLICIES_OFFLINE, DOGPOLICIES_BASE_URL.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-01 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://dogpolicies.com/mcp/

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

{
  "servers": {
    "dogpolicies-mcp": {
      "type": "http",
      "url": "https://dogpolicies.com/mcp/"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "dogpolicies-mcp": {
      "type": "streamableHttp",
      "url": "https://dogpolicies.com/mcp/",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

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

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.dogpolicies-mcp]
url = "https://dogpolicies.com/mcp/"

Zed · Zed settings file (command: zed: open settings file)

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://dogpolicies.com/mcp/ --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.2.9
Latest stable: 0.2.9
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-11-01. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-11-01 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-T19hsIQ7cRS0/IWvo…
Signature: signed and attested
License: MIT

Source: the package registry · 2026-11-01.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint dogpolicies.com/mcp/	Session opened	matches	our test · 2026-11-01
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-01
Version 0.2.9 on npm	Exists and can be installed	matches	npm · 2026-11-01
Repository github.com/xultrax-web/dogpolicies-mcp	Opens publicly	matches	api.github.com · 2026-11-01

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.xultrax-web · 2 servers
GitHub owner: a personal account (xultrax-web)
Build record: signed and attested

Repository: github.com/xultrax-web/dogpolicies-mcp
Stars: 1
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-11-01; security policy read from GitHub · 2026-11-01.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

Not ranked by downloads: no download figure available
Not ranked by stars: 1 star (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01 (security policy 2026-11-01). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.xultrax-web/dogpolicies-mcp

Answered from the data above

Who publishes io.github.xultrax-web/dogpolicies-mcp?

The registry ties the namespace io.github.xultrax-web to the GitHub account xultrax-web; only its owner can publish under it. Its linked repository, github.com/xultrax-web/dogpolicies-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.xultrax-web/dogpolicies-mcp safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.xultrax-web/dogpolicies-mcp need an API key or sign-in?

It opened a session without any credential on 2026-11-01. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.xultrax-web/dogpolicies-mcp been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does io.github.xultrax-web/dogpolicies-mcp publish a security policy?

Yes: its repository has a public security policy (github.com/xultrax-web/dogpolicies-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.2.9, the latest stable release on npm.

Where is the source code of io.github.xultrax-web/dogpolicies-mcp?

In github.com/xultrax-web/dogpolicies-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-01

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-01, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
2,241 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 26 tools, 30 resources, 5 prompts.
12,630 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-11-01; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-11-01

Hosting type

remote and local package

registry · 2026-11-01

MCP capability

completions, prompts, resources, tools

our test · 2026-11-01

Transport

standard input/output, streamable HTTP

registry · 2026-11-01

Required credentials

none declared

registry · 2026-11-01 · no declaration is not a guarantee

Package registry

npm

registry · 2026-11-01

Freshness

0–30 days

registry updatedAt · 2026-11-01

Lifecycle status

active

registry · 2026-11-01

License class

permissive

package registry · 2026-11-01

Integrity hash

declared (sri)

package registry · 2026-11-01

Signature / provenance

signed and attested

package registry · 2026-11-01

Dependency advisories

none known

npm audit · 2026-11-01

Popularity

not stated

npm has no download count yet: the package is 1 day old (the downloads API answered 0 on 4 asks)

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-11-01

Maintenance

active

api.github.com · 2026-11-01

Environment

either (remote or your machine)

where it runs, from the hosting type · 2026-11-01

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.xultrax-web/dogpolicies-mcp: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/io.github.xultrax-web/dogpolicies-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.xultrax-web/dogpolicies-mcp)](https://protocolprobe.com/mcp/servers/io.github.xultrax-web/dogpolicies-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology