Remote MCP · Endpoint

My Wed Paper Wedding Tools MCP server

No. My Wed Paper Wedding Tools answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mywedpaper.com/mcp/wedding-tools

The last check completed an MCP handshake.

Registry name
com.mywedpaper/wedding-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.04 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Wedding crosswords, newspaper templates, and printing guidance in English and French.
Listing
From the official MCP registry (active).
Recent checks of My Wed Paper Wedding Tools
CheckedResultHandshake
20 minutes agoHandshake completed1.04 s
9 days agoHandshake completed298 ms
9 days agoHandshake completed1.07 s
11 days agoHandshake completed1.05 s
12 days agoHandshake completed463 ms
13 days agoHandshake completed1.08 s
14 days agoHandshake completed1.03 s
15 days agoHandshake completed1.09 s
16 days agoHandshake completed1.00 s
19 days agoHandshake completed1.02 s
21 days agoHandshake completed1.02 s
24 days agoHandshake completed820 ms
26 days agoHandshake completed337 ms
28 days agoHandshake completed2.45 s

The last 14 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 My Wed Paper Wedding Tools and makes no claim about it beyond what these checks measured.