Remote MCP · Endpoint

Wever Labs Agent Products MCP server

No. Wever Labs Agent Products answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://weverlabs.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.CodeWever/wever-labs-products
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
604 ms
Tools exposed
162 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
514 main tools, 498 production tools for agents; Base USDC x402 and shared free tier.
Listing
From the official MCP registry (active).
Recent checks of Wever Labs Agent Products
CheckedResultHandshake
5 hours agoHandshake completed604 ms
9 days agoHandshake completed388 ms
10 days agoHandshake completed172 ms
11 days agoHandshake completed124 ms
12 days agoHandshake completed336 ms
14 days agoHandshake completed107 ms
14 days agoHandshake completed4.16 s
15 days agoHandshake completed98 ms
17 days agoHandshake completed403 ms
19 days agoHandshake completed121 ms
21 days agoHandshake completed304 ms
24 days agoHandshake completed2.76 s
26 days agoHandshake completed2.99 s
28 days agoHandshake completed257 ms

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

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