Remote MCP · Endpoint

Veliane Discovery Plus MCP server

No. Veliane Discovery Plus answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://velianediscoveryplus.aplusz.app/mcp

The last check completed an MCP handshake.

Registry name
app.aplusz.velianediscoveryplus/veliane
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
109 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Facts, price, safety and join links for Veliane, free marriage-minded matchmaking.
Listing
From the official MCP registry (active).
Recent checks of Veliane Discovery Plus
CheckedResultHandshake
15 minutes agoHandshake completed109 ms
9 days agoHandshake completed91 ms
9 days agoHandshake completed60 ms
11 days agoHandshake completed125 ms
12 days agoHandshake completed95 ms
13 days agoHandshake completed125 ms
14 days agoHandshake completed97 ms
14 days agoHandshake completed70 ms
16 days agoHandshake completed223 ms
19 days agoHandshake completed146 ms
21 days agoHandshake completed58 ms
24 days agoHandshake completed86 ms
26 days agoHandshake completed95 ms
28 days agoHandshake completed71 ms

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