Remote MCP · Endpoint

PatchDesign.AI MCP server

No. PatchDesign.AI answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://patchdesign.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.patchdesign/patch-designer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
356 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Design custom embroidered, woven, chenille, printed and PVC patches, price them, and link to order.
Listing
From the official MCP registry (active).
Recent checks of PatchDesign.AI
CheckedResultHandshake
2 days agoHandshake completed356 ms
3 days agoHandshake completed574 ms
3 days agoHandshake completed879 ms
5 days agoHandshake completed333 ms
6 days agoHandshake completed435 ms
7 days agoHandshake completed697 ms
8 days agoHandshake completed483 ms
9 days agoHandshake completed543 ms
11 days agoHandshake completed869 ms
13 days agoHandshake completed335 ms
16 days agoHandshake completed689 ms
18 days agoHandshake completed598 ms
20 days agoHandshake completed497 ms
22 days agoHandshake completed477 ms
24 days agoHandshake completed491 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 PatchDesign.AI and makes no claim about it beyond what these checks measured.