customs-dog-mcp
Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"customs-dog-mcp": {
"url": "https://customs.dog/mcp"
}
}
}Remote endpoints
https://customs.dog/mcpstreamable-httpWhat it can do
Tool inventory
Tools (8)
🟢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.
Input Schema
{
"type": "object",
"properties": {
"destination": {
"type": "string",
"enum": [
"mexico",
"canada",
"bvi",
"us_domestic"
]
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡customs_start_signup(email, name)
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.
Input Schema
{
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email",
"pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
},
"name": {
"type": "string",
"maxLength": 80
}
},
"required": [
"email"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪customs_prep
Validate the session, confirm the pet roster, report health. Call first.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪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).
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢customs_list_pets
List the household's pets (source of pet_id).
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢customs_list_documents(pet_id, category, status)
List documents for a pet.
Input Schema
{
"type": "object",
"properties": {
"pet_id": {
"type": "string"
},
"category": {
"type": "string",
"enum": [
"cdc_import_receipt",
"health_cert",
"rabies",
"microchip",
"permit",
"medical",
"service_esa",
"airline",
"photos"
]
},
"status": {
"type": "string",
"enum": [
"valid",
"expiring",
"expired",
"none"
]
}
},
"required": [
"pet_id"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢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.)
Input Schema
{
"type": "object",
"properties": {
"pet_id": {
"type": "string"
},
"destination": {
"type": "string",
"enum": [
"mexico",
"canada",
"bvi",
"us_domestic"
]
},
"return_date": {
"type": "string"
}
},
"required": [
"pet_id",
"destination"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪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.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence