Remote MCP · Endpoint

io.github.capitalthought/customs-dog-mcp MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://customs.dog/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.capitalthought/customs-dog-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Pet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs.
Listing
From the official MCP registry (active).
Recent checks of io.github.capitalthought/customs-dog-mcp
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
10 days agoHandshake completed637 ms
12 days agoHandshake completed664 ms
15 days agoHandshake completed712 ms
17 days agoHandshake completed807 ms
19 days agoHandshake completed821 ms
21 days agoHandshake completed625 ms
23 days agoHandshake completed790 ms
25 days agoHandshake completed580 ms
26 days agoHandshake completed775 ms
28 days agoHandshake completed812 ms
29 days agoHandshake completed1.18 s

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.capitalthought/customs-dog-mcp and makes no claim about it beyond what these checks measured.