Remote MCP · Endpoint

Shoptegrity MCP server

No. Shoptegrity answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.shopteg.com/mcp

The last check completed an MCP handshake.

Registry name
com.shopteg/shoptegrity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
503 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
See who gets your money, catch fake holiday discounts, and find independent and local sellers.
Listing
From the official MCP registry (active).
Recent checks of Shoptegrity
CheckedResultHandshake
34 minutes agoHandshake completed503 ms
9 days agoHandshake completed1.09 s
10 days agoHandshake completed532 ms
11 days agoHandshake completed551 ms
12 days agoHandshake completed549 ms
14 days agoHandshake completed488 ms
14 days agoHandshake completed665 ms
15 days agoHandshake completed485 ms
17 days agoHandshake completed1.11 s
19 days agoHandshake completed592 ms
21 days agoHandshake completed547 ms
24 days agoHandshake completed512 ms
26 days agoHandshake completed993 ms

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

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