Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh 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.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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.
| Argument | Type | Description |
|---|---|---|
| destination | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"destination": {
"enum": [
"mexico",
"canada",
"bvi",
"us_domestic"
],
"type": "string"
}
}
}Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)
| Argument | Type | Description |
|---|---|---|
| pet_id* | string | |
| destination* | string | |
| return_date | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"pet_id",
"destination"
],
"properties": {
"pet_id": {
"type": "string"
},
"destination": {
"enum": [
"mexico",
"canada",
"bvi",
"us_domestic"
],
"type": "string"
},
"return_date": {
"type": "string"
}
}
}List documents for a pet.
| Argument | Type | Description |
|---|---|---|
| pet_id* | string | |
| status | string | |
| category | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"pet_id"
],
"properties": {
"pet_id": {
"type": "string"
},
"status": {
"enum": [
"valid",
"expiring",
"expired",
"none"
],
"type": "string"
},
"category": {
"enum": [
"cdc_import_receipt",
"health_cert",
"rabies",
"microchip",
"permit",
"medical",
"service_esa",
"airline",
"photos"
],
"type": "string"
}
}
}List the household's pets (source of pet_id).
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}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).
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Validate the session, confirm the pet roster, report health. Call first.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| name | string | |
| email* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"email"
],
"properties": {
"name": {
"type": "string",
"maxLength": 80
},
"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,}$"
}
}
}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.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}