Remote MCP · Endpoint

Toys Hub MCP server

No. Toys Hub answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://toyshub.al/mcp

The last check completed an MCP handshake.

Registry name
al.toyshub/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
568 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Browse Toys Hub: products, prices in ALL, stock, delivery and checkout links. Read-only, no sign-in.
Listing
From the official MCP registry (active).
Recent checks of Toys Hub
CheckedResultHandshake
6 hours agoHandshake completed568 ms
9 days agoHandshake completed398 ms
10 days agoHandshake completed394 ms
11 days agoHandshake completed397 ms
12 days agoHandshake completed464 ms
14 days agoHandshake completed456 ms
15 days agoHandshake completed626 ms
15 days agoHandshake completed1.18 s
17 days agoHandshake completed425 ms
19 days agoHandshake completed677 ms
22 days agoHandshake completed403 ms
24 days agoHandshake completed379 ms
26 days agoHandshake completed361 ms
28 days agoHandshake completed400 ms

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

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