mcp server
customs-dog-mcp
Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Description as published by the maintainer. Source
- version 2.1.0
- active
active — Registry entry last updated 2026-06-09.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
customs_check_rules(destination)- 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_readiness(pet_id, destination, return_date)- Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.) Required: pet_id, destination.
customs_list_documents(pet_id, status, category)- List documents for a pet. Required: pet_id.
customs_list_pets- List the household's pets (source of pet_id).
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_prep- Validate the session, confirm the pet roster, report health. Call first.
customs_start_signup(name, email)- 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. Required: email.
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.
Last successful function declaration observed on . Source: https://customs.dog/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://customs.dog/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 2.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-09 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-09 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | customs.dog | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | customs.dog |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json