Remote MCP · Endpoint

io.github.webweaver-nexus/webweaver-mcp-server MCP server

No. io.github.webweaver-nexus/webweaver-mcp-server answered an MCP handshake 19 hours ago.

UpLast checked 19 hours ago

Server URL

https://webweaver-nexus-mcp.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.webweaver-nexus/webweaver-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
WebWeaver Nexus services for MCP hosts: contact form (with UI), product overview, contact links.
Listing
From the official MCP registry (active).
Recent checks of io.github.webweaver-nexus/webweaver-mcp-server
CheckedResultHandshake
19 hours agoHandshake completed84 ms
2 days agoHandshake completed55 ms
4 days agoHandshake completed73 ms
6 days agoHandshake completed685 ms
8 days agoHandshake completed58 ms
9 days agoHandshake completed127 ms
10 days agoHandshake completed78 ms
13 days agoHandshake completed83 ms
14 days agoHandshake completed83 ms
16 days agoHandshake completed85 ms
17 days agoHandshake completed107 ms
18 days agoHandshake completed792 ms
20 days agoHandshake completed57 ms
21 days agoHandshake completed744 ms
21 days agoHandshake completed149 ms
22 days agoHandshake completed139 ms
23 days agoHandshake completed85 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 io.github.webweaver-nexus/webweaver-mcp-server and makes no claim about it beyond what these checks measured.