Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://customs.dog/mcp8 tools · 903mscustoms_check_rulesPer-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.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.
| Parameter | Type | Description |
|---|---|---|
| destination | string | — |
customs_start_signupinjection riskStart 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.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.
t for a NEW user by email and send them a magic sign-in link (no password). Use this to onboard someone…| Parameter | Type | Description |
|---|---|---|
| email* | string | — |
| name | string | — |
customs_prepValidate the session, confirm the pet roster, report health. Call first.Validate the session, confirm the pet roster, report health. Call first.
No input schema was published for this tool.
customs_overviewCounts 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).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 input schema was published for this tool.
customs_list_petsList the household's pets (source of pet_id).List the household's pets (source of pet_id).
No input schema was published for this tool.
customs_list_documentsList documents for a pet.List documents for a pet.
| Parameter | Type | Description |
|---|---|---|
| pet_id* | string | — |
| category | string | — |
| status | string | — |
customs_check_trip_readinessCleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)
| Parameter | Type | Description |
|---|---|---|
| pet_id* | string | — |
| destination* | string | — |
| return_date | string | — |
customs_upcoming_tripsUpcoming 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.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 input schema was published for this tool.
8 of 8 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.