Customs Dog Mcp

io.github.capitalthoughtPublished by GitHub account capitalthoughtv2.1.0Updated Oct 24, 2026

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

The publisher's own server: Doom

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

A remote MCP server for pet travel paperwork: it looks up border-entry rules for dogs and, with an account, tracks a household's pets, documents and trip-readi

What you can do
Look up per-destination pet border-entry requirements and required documents, including re-entry to the US, without an account; omit the destination to list all corridors. Start a free account for a new user by email and send a magic sign-in link. Validate the session, confirm the pet roster and report health. Show household counts of pets and documents by status, expiring items, recent activity and usage stats. List the household's pets and their documents. Check trip readiness as cleared, caution or blocked for a pet, destination and return date. List upcoming trips from a connected travel calendar with per-pet readiness.
When to use it
Use it when someone asks what a dog needs to travel to a given country, or when a household wants to store and track pet travel documents and get readiness flags before upcoming trips.
Requirements
A remote endpoint; no local runtime or package. The rules lookup and signup need no account. Household features need a customs.dog account and a session, and upcoming trips need a connected travel calendar (TripIt, Flighty, Google or Apple).
Before you install
Signup sends a magic sign-in link to an email address, so the address must be the user's own. Household tools expose pet and document data and usage statistics. Readiness results are advisory; the server says clearance must never be asserted without the readiness check. Connecting a travel calendar shares trip data with the service.

Installation

In SourceWeft

  1. Open Customs Dog Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.capitalthought%2Fcustoms-dog-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

8

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.

Parametersdestination

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.

Parametersnameemailrequired

customs_prep

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

Takes no parameters.

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).

Takes no parameters.

customs_list_pets

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

Takes no parameters.

customs_list_documents

List documents for a pet.

Parameterspet_idrequiredstatuscategory

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.)

Parameterspet_idrequireddestinationrequiredreturn_date

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.

Takes no parameters.

Version history

1
  1. v2.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Doomscore integrations