Remote MCP · Endpoint

Usitc Edis MCP server

No. Usitc Edis answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/usitc-edis/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/usitc-edis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
72 ms
Tools exposed
43 tools
Uptime, last 30 days
86.7% from 15 checks
Described by its publisher as
USITC IDS (Investigations Database System, ids.usitc.gov) — the CASE
Listing
From the official MCP registry (active).
Recent checks of Usitc Edis
CheckedResultHandshake
2 hours agoHandshake completed72 ms
2 days agoHandshake completed70 ms
4 days agoHandshake completed73 ms
6 days agoHandshake completed54 ms
8 days agoHandshake completed62 ms
9 days agoHandshake completed68 ms
11 days agoHandshake completed62 ms
12 days agoHandshake completed93 ms
14 days agoHandshake completed47 ms
16 days agoFailed - the request timed out—
17 days agoFailed - the request timed out—
19 days agoHandshake completed809 ms
20 days agoHandshake completed951 ms
21 days agoHandshake completed1.04 s
22 days agoHandshake completed1.54 s

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

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 Usitc Edis and makes no claim about it beyond what these checks measured.