Customs Dog MCP

Reliability

Latest check failed 5 h ago: initialize returned HTTP 500

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "customs-dog-mcp": {
      "type": "http",
      "url": "https://customs.dog/mcp"
    }
  }
}

8 tools

• customs_check_rules

  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_start_signup

  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_prep

  Validate the session, confirm the pet roster, report health. Call first.

• customs_overview

  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_list_pets

  List the household's pets (source of pet_id).

• customs_list_documents

  List documents for a pet.

• customs_check_trip_readiness

  Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)

• customs_upcoming_trips

  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.

Security scan

Recent checks