Customs Dog Mcp
Let an agent look up pet border entry rules and manage household travel documents when you build pet-travel or relocation assistant products.
Overview
io.github.capitalthought/customs-dog-mcp is a MCP server for the Build phase that exposes pet travel border rules and household document workflows over streamable HTTP.
What is this MCP server?
- Remote streamable-http MCP at https://customs.dog/mcp
- Keyless mode: entry rules lookup and sign-up flows without storing secrets in the client
- Keyed mode: household pet document storage and border-readiness workflows
- Pet travel and customs readiness domain rather than generic document OCR
- Website and product surface at customs.dog (registry version 2.1.0)
- Remote URL https://customs.dog/mcp
- streamable-http transport
What problem does it solve?
Pet border rules and document checklists are fragmented, so agents and apps give vague travel advice without a dedicated compliance-oriented tool.
Who is it for?
Builders prototyping or shipping pet-travel, relocation, or pet-care SaaS who want a hosted MCP instead of scraping government sites.
Skip if: Teams with no pet-travel domain need, or products that cannot use third-party hosted remotes for sensitive document data.
What do I get? / Deliverables
After you add the remote MCP URL, your agent can query entry rules keylessly or use keyed household doc flows inside supported clients.
- Remote MCP endpoint wired into agent configuration
- Agent-driven entry rule lookups and signup paths
- Optional keyed household document workflows in your product
Recommended MCP Servers
Journey fit
Most builders integrate remote MCP during implementation, but the same server supports quick prototypes and content-heavy pet-travel features later. Streamable HTTP remote at customs.dog/mcp is an external API integration your agent calls, not in-repo codegen.
How it compares
Domain-specific hosted MCP API, not a general passport OCR skill or self-hosted stdio tool.
Common Questions / FAQ
Who is io.github.capitalthought/customs-dog-mcp for?
Solo builders and small teams creating pet travel assistants, border checklists, or household pet document hubs who want agent-callable rules and signup flows.
When should I use io.github.capitalthought/customs-dog-mcp?
Use it when integrating travel-readiness features in Build, or when validating a pet-travel MVP that needs real entry-rule lookups via MCP.
How do I add io.github.capitalthought/customs-dog-mcp to my agent?
Register the remote MCP URL https://customs.dog/mcp as streamable-http in your agent client; use keyless tools first, then account keys for household document features per customs.dog docs.