Remote MCP · Endpoint

Trisport MCP server

No. Trisport answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.trisport.ro/mcp/

The last check completed an MCP handshake.

Registry name
ro.trisport/store
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.25 s
Tools exposed
10 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
Romanian sports store: search products, sizes, stock, delivery and build a trisport.ro cart link.
Listing
From the official MCP registry (active).
Recent checks of Trisport
CheckedResultHandshake
1 hour agoHandshake completed1.25 s
12 hours agoHandshake completed487 ms
1 day agoHandshake completed367 ms
2 days agoHandshake completed395 ms
4 days agoHandshake completed375 ms
4 days agoHandshake completed440 ms
5 days agoHandshake completed702 ms
6 days agoHandshake completed397 ms
8 days agoHandshake completed635 ms
11 days agoHandshake completed367 ms
13 days agoHandshake completed374 ms
16 days agoHandshake completed367 ms
18 days agoHandshake completed366 ms
20 days agoHandshake completed368 ms
22 days agoHandshake completed382 ms
24 days agoFailed - the server returned an HTTP error—

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

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