Remote MCP · Endpoint

Pinchy MCP server

No. Pinchy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.trypinchy.com/mcp

The last check completed an MCP handshake.

Registry name
com.trypinchy/pinchy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
615 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find coupon and promo codes for any online store, ordered by how likely they are to work.
Listing
From the official MCP registry (active).
Recent checks of Pinchy
CheckedResultHandshake
1 hour agoHandshake completed615 ms
2 days agoHandshake completed726 ms
4 days agoHandshake completed604 ms
5 days agoHandshake completed578 ms
7 days agoHandshake completed3.15 s
8 days agoHandshake completed684 ms
9 days agoHandshake completed547 ms
12 days agoHandshake completed740 ms
13 days agoHandshake completed633 ms
15 days agoHandshake completed582 ms
16 days agoHandshake completed3.30 s
18 days agoHandshake completed572 ms
19 days agoHandshake completed647 ms
20 days agoHandshake completed870 ms
20 days agoHandshake completed635 ms
21 days agoHandshake completed608 ms
22 days agoHandshake completed623 ms

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

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