Remote MCP · Endpoint

Tariff & HS Code Duty Finder MCP server

No. Tariff & HS Code Duty Finder answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://tariffs.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/tariffs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
164 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find an HS code, HTS code or customs code, and read the customs duty or import tax.
Listing
From the official MCP registry (active).
Recent checks of Tariff & HS Code Duty Finder
CheckedResultHandshake
44 minutes agoHandshake completed164 ms
3 days agoHandshake completed149 ms
13 days agoHandshake completed153 ms
13 days agoHandshake completed196 ms
15 days agoHandshake completed176 ms
15 days agoHandshake completed162 ms
17 days agoHandshake completed1.31 s
18 days agoHandshake completed170 ms
18 days agoHandshake completed185 ms
20 days agoHandshake completed170 ms
22 days agoHandshake completed5.21 s
25 days agoHandshake completed123 ms
27 days agoHandshake completed148 ms
29 days agoHandshake completed176 ms

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

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 Tariff & HS Code Duty Finder and makes no claim about it beyond what these checks measured.