Remote MCP · Endpoint

io.github.giachi85it-ux/customswise MCP server

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

DownLast checked 1 hour ago

Server URL

https://customswise-api.onrender.com/mcp

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

Registry name
io.github.giachi85it-ux/customswise
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
41.2% from 17 checks
Described by its publisher as
Practitioner-verified EU customs facts: classification, duty, origin, procedures. x402.
Listing
From the official MCP registry (active).
Recent checks of io.github.giachi85it-ux/customswise
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoHandshake completed307 ms
5 days agoHandshake completed136 ms
7 days agoHandshake completed158 ms
8 days agoHandshake completed303 ms
9 days agoHandshake completed144 ms
12 days agoHandshake completed136 ms
13 days agoHandshake completed145 ms
15 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—

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

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.giachi85it-ux/customswise and makes no claim about it beyond what these checks measured.