Remote MCP · Endpoint

Wever Labs Agent Products MCP server

No. Wever Labs Agent Products answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
2.76 s
Tools exposed
57 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agent commerce: 27 tools, 10 production services, signed authority, planning, Base USDC x402.
Listing
From the official MCP registry (active).
Recent checks of Wever Labs Agent Products
CheckedResultHandshake
1 hour agoHandshake completed2.76 s
2 days agoHandshake completed2.99 s
4 days agoHandshake completed257 ms
6 days agoHandshake completed241 ms
8 days agoHandshake completed271 ms
10 days agoHandshake completed124 ms
12 days agoHandshake completed405 ms
13 days agoHandshake completed2.34 s
14 days agoHandshake completed506 ms
16 days agoHandshake completed349 ms
18 days agoHandshake completed355 ms
20 days agoHandshake completed326 ms
21 days agoHandshake completed281 ms
23 days agoHandshake completed277 ms

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

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.