customs-dog-mcp server
io.github.capitalthought/customs-dog-mcpcapitalthoughtstreamable-httpv2.1.0Scanned
Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
8 tools: 4 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the customs-dog-mcp server can do
The customs-dog-mcp server is published by the GitHub account capitalthought. It has 8 tools. It can create or change data (4 tools: customs_check_rules, customs_start_signup, customs_check_trip_readiness and customs_upcoming_trips), but cannot delete data. 4 tools only read.
2 tools read private data (customs_overview and customs_list_documents).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 21, 2026, version 2.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 4Claude Code: ask
customs_check_rulesPer-destination pet border-entry requirements — NO account needed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Per-destination pet border-entry requirements — NO account needed. What documents a dog needs to enter a country and re-enter the US. Use this to answer 'what does my pet need to travel to X?' for anyone. Omit `destination` to list every corridor.
customs_check_trip_readinessCleared / caution / blocked for pet + destination + return_date.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)
customs_start_signupStart a FREE customs.dog account for a NEW user by email and send them a magic sign-in link (no password).No findings
Why it is in this group
- The name "customs_start_signup" says "start": a word for a change.
Description, as the server wrote it Start a FREE customs.dog account for a NEW user by email and send them a magic sign-in link (no password). Use this to onboard someone who wants to store and track their pet's travel documents after you've shown them their border requirements.
customs_upcoming_tripsUpcoming trips from the household's connected travel calendar (TripIt/Flighty/Google/Apple), each with per-pet readiness (cleared/caution/blocked).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Upcoming trips from the household's connected travel calendar (TripIt/Flighty/Google/Apple), each with per-pet readiness (cleared/caution/blocked). Use to proactively flag paperwork needed before travel.
Only reads 4Show 4 read-only tools
customs_list_documentsList documents for a pet.Reads private dataNo findings
Why it is in this group
- The name "customs_list_documents" says "list": a word for reading.
What it can reach
- private-dataThe name "customs_list_documents" says "list" and "document": it reads documents.
- private-dataThe description's first sentence says "list" and "document": it reads documents.
Description, as the server wrote it List documents for a pet.
customs_list_petsList the household's pets (source of pet_id).No findings
Why it is in this group
- The name "customs_list_pets" says "list": a word for reading.
Description, as the server wrote it List the household's pets (source of pet_id).
customs_overviewCounts of pets/documents by status, what's expiring soon, recent household activity, and MCP usage stats (per-tool call counts, public-tier reach, verdict distribution).Reads private dataNo findings
Why it is in this group
- The description's first verb is "count": a word for reading.
What it can reach
- private-dataThe description's first sentence says "count" and "document": it reads documents.
Description, as the server wrote it Counts of pets/documents by status, what's expiring soon, recent household activity, and MCP usage stats (per-tool call counts, public-tier reach, verdict distribution).
customs_prepValidate the session, confirm the pet roster, report health.No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it Validate the session, confirm the pet roster, report health. Call first.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:03 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 500
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 500.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 429 to 500
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 500.View diff
- HTTP status of an anonymous initialize: 429 to 500
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 4 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 2.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http customs-dog https://customs.dog/mcpclaude mcp add --transport http customs-dog https://customs.dog/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__customs-dog__customs_prep",
"mcp__customs-dog__customs_overview",
"mcp__customs-dog__customs_list_pets",
"mcp__customs-dog__customs_list_documents"
],
"ask": [
"mcp__customs-dog__customs_check_rules",
"mcp__customs-dog__customs_start_signup",
"mcp__customs-dog__customs_check_trip_readiness",
"mcp__customs-dog__customs_upcoming_trips"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as customs-dog. Review it before you use it.
Capability tags behind 2 rules
- mcp__customs-dog__customs_overview private-data
- mcp__customs-dog__customs_list_documents private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.capitalthought/customs-dog-mcp/verify?hash=d4419c497cfdd01ac306927c0c3e0ed70d38d790069f5c81e0d42dc8ee5ded2b" | jq -e '.changed == false'Pinned hash d4419c497cfd, from Oct 21, 2026, 19:09 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.capitalthought/customs-dog-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.capitalthought/customs-dog-mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:26 UTC.
customs-dog-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the customs-dog-mcp server safe?
- No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the customs-dog-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the customs-dog-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the customs-dog-mcp server have?
- 8 tools: 4 write, 4 read. customs_check_rules, customs_start_signup, customs_check_trip_readiness, customs_upcoming_trips, customs_prep, customs_overview, customs_list_pets and customs_list_documents.
Does the customs-dog-mcp server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the customs-dog-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the customs-dog-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.