Remote MCP · Endpoint

Able.Style MCP server

No. Able.Style answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://able.style/mcp

The last check completed an MCP handshake.

Registry name
style.able/able-style-wardrobe-management
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
178 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Manage your wardrobe or closet, discover ways to wear your clothes, and get outfit suggestions.
Website
https://able.style/mcp
Listing
From the official MCP registry (active).
Recent checks of Able.Style
CheckedResultHandshake
34 minutes agoHandshake completed178 ms
9 days agoHandshake completed95 ms
10 days agoHandshake completed66 ms
11 days agoHandshake completed72 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed59 ms
14 days agoHandshake completed64 ms
15 days agoHandshake completed56 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed68 ms
21 days agoHandshake completed58 ms
24 days agoHandshake completed72 ms
26 days agoHandshake completed76 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Able.Style and makes no claim about it beyond what these checks measured.