Remote MCP · Endpoint

JAWD Jaw Trainers MCP server

No. JAWD Jaw Trainers answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://mcp.jawd.in/mcp

The last check completed an MCP handshake.

Registry name
in.jawd/jawd
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
300 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Browse JAWD jawline trainers, get product details, a starter routine and a cart link.
Listing
From the official MCP registry (active).
Recent checks of JAWD Jaw Trainers
CheckedResultHandshake
46 minutes agoHandshake completed300 ms
3 days agoHandshake completed499 ms
13 days agoHandshake completed247 ms
13 days agoHandshake completed334 ms
15 days agoHandshake completed192 ms
16 days agoHandshake completed149 ms
17 days agoHandshake completed118 ms
18 days agoHandshake completed162 ms
18 days agoHandshake completed181 ms
20 days agoHandshake completed197 ms
22 days agoHandshake completed144 ms
25 days agoHandshake completed283 ms
27 days agoHandshake completed242 ms
30 days agoHandshake completed154 ms

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

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