General Tools
customs.dog
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://customs.dog/mcp
MCP server metadata
- Name
- customs.dog
- Version
- 2.2.0
Known tools 8
customs_check_rulesPer-destination pet border-entry requirements — NO account needed.
Inferred read-onlycustoms_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).
Inferred read-onlycustoms_check_trip_readinessCleared / caution / blocked for pet + destination + return_date.
Inferred read-onlycustoms_upcoming_tripsUpcoming trips from the household's connected travel calendar (TripIt/Flighty/Google/Apple), each with per-pet readiness (cleared/caution/blocked).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.customs-dog]
url = "https://customs.dog/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"customs-dog": {
"type": "http",
"url": "https://customs.dog/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: customs-dog
Remote MCP URL: https://customs.dog/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"customs-dog": {
"url": "https://customs.dog/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"customs-dog": {
"type": "http",
"url": "https://customs.dog/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "customs-dog",
"transport": "streamable-http",
"url": "https://customs.dog/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for customs.dog was fetched 2026-08-19T22:58:16.748Z.
customs.dog is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.