Remote MCP · Endpoint

Toys Hub MCP server

No. Toys Hub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
361 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed361 ms
2 days agoHandshake completed400 ms
4 days agoHandshake completed622 ms
6 days agoHandshake completed387 ms
8 days agoHandshake completed443 ms
9 days agoHandshake completed460 ms
11 days agoHandshake completed487 ms
12 days agoHandshake completed450 ms
13 days agoHandshake completed154 ms
16 days agoHandshake completed351 ms
17 days agoHandshake completed349 ms
19 days agoHandshake completed365 ms
21 days agoHandshake completed394 ms
22 days agoHandshake completed356 ms
23 days agoHandshake completed419 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 Toys Hub and makes no claim about it beyond what these checks measured.