Remote MCP · Endpoint

PreShiftIQ MCP server

No. PreShiftIQ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.preshiftiq.com/mcp

The last check completed an MCP handshake.

Registry name
com.preshiftiq/shiftiq-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Independent buyer-side matching for supply chain technology selection.
Listing
From the official MCP registry (active).
Recent checks of PreShiftIQ
CheckedResultHandshake
1 hour agoHandshake completed124 ms
2 days agoHandshake completed156 ms
5 days agoHandshake completed151 ms
7 days agoHandshake completed592 ms
9 days agoHandshake completed165 ms
11 days agoHandshake completed158 ms
13 days agoHandshake completed146 ms
15 days agoHandshake completed136 ms
17 days agoHandshake completed115 ms
18 days agoHandshake completed309 ms
19 days agoHandshake completed180 ms
20 days agoHandshake completed151 ms
23 days agoHandshake completed213 ms
24 days agoHandshake completed157 ms

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

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