Skip to content

io.github.capitalthought/customs-dog-mcp

by capitalthought · remote · no sign-in to list tools · v2.1.0 · published by GitHub user capitalthought

Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.

Changes · 4
CompareRegistry entry

8 tools: 4 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http customs-dog https://customs.dog/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

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 4Claude Code: allow
  • customs_list_documentsList documents for a pet.No findings

    Why it is in this group

    • The name "customs_list_documents" says "list": a word for reading.
    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).No findings

    Why it is in this group

    • The description's first verb is "count": a word for reading.
    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.

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/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.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. It assumes the server is installed as customs-dog. Review it before you use it.