io.github.capitalthought/customs-dog-mcp
REMOTE · CUSTOMS.DOG
Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Available components
Last scanned (20 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Oct 26 −52
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://customs.dog/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=customs.dog | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fe3daa30165e655f13171d97ead26911 |
| SANs: customs.dog, www.customs.dog, *.www.customs.dog | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of customs.dog. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dog. | present | 56555 | 8 | Verified |
| customs.dog. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 500 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://customs.dog/mcp | HTTP error | 500 | |
| http (plaintext) | http://customs.dog/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
customs_check_rules ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | – |
No output schema declared.
No examples provided.
customs_check_trip_readiness ~66
Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| pet_id | string | yes | – |
| return_date | string | – | – |
No output schema declared.
No examples provided.
customs_list_documents ~37
List documents for a pet.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| pet_id | string | yes | – |
| status | string | – | – |
No output schema declared.
No examples provided.
customs_list_pets ~21
List the household's pets (source of pet_id).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
customs_overview ~43
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
customs_prep ~24
Validate the session, confirm the pet roster, report health. Call first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
customs_start_signup ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| name | string | – | – |
No output schema declared.
No examples provided.
customs_upcoming_trips ~54
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.capitalthought/customs-dog-mcp server?
io.github.capitalthought/customs-dog-mcp is a hosted endpoint at https://customs.dog/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · customs.dog
claude mcp add --transport http capitalthought-customs-dog-mcp 'https://customs.dog/mcp'
What is the io.github.capitalthought/customs-dog-mcp server?
io.github.capitalthought/customs-dog-mcp is listed in the public MCP registry as io.github.capitalthought/customs-dog-mcp. Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs. This page covers its hosted endpoint (https://customs.dog/mcp).
Is the io.github.capitalthought/customs-dog-mcp server safe to use?
io.github.capitalthought/customs-dog-mcp scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.capitalthought/customs-dog-mcp server expose?
io.github.capitalthought/customs-dog-mcp exposes 8 tools: customs_check_rules, customs_start_signup, customs_prep, customs_overview, customs_list_pets, and 3 more. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.
Does the io.github.capitalthought/customs-dog-mcp server require authentication?
Its publisher declares no required credentials for io.github.capitalthought/customs-dog-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.capitalthought/customs-dog-mcp server still maintained?
io.github.capitalthought/customs-dog-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.