Remote MCP · Endpoint

Tailor MCP server

No. Tailor answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.tailor.tech/

The last check completed an MCP handshake.

Registry name
tech.tailor/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
278 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Tailor Platform for AI assistants: search, list and read the platform documentation.
Listing
From the official MCP registry (active).
Recent checks of Tailor
CheckedResultHandshake
2 hours agoHandshake completed278 ms
2 days agoHandshake completed980 ms
4 days agoHandshake completed931 ms
5 days agoHandshake completed225 ms
7 days agoHandshake completed270 ms
8 days agoHandshake completed221 ms
9 days agoHandshake completed740 ms
12 days agoHandshake completed677 ms
13 days agoHandshake completed640 ms
15 days agoHandshake completed764 ms
17 days agoHandshake completed200 ms
18 days agoHandshake completed435 ms
19 days agoHandshake completed809 ms
20 days agoHandshake completed658 ms
20 days agoHandshake completed195 ms
21 days agoHandshake completed208 ms

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