Remote MCP · Endpoint

Nuget MCP server

No. Nuget answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/nuget/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nuget
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
130 ms
Tools exposed
48 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
NuGet MCP — .NET package registry
Listing
From the official MCP registry (active).
Recent checks of Nuget
CheckedResultHandshake
2 hours agoHandshake completed130 ms
22 hours agoHandshake completed175 ms
2 days agoHandshake completed52 ms
3 days agoHandshake completed102 ms
4 days agoHandshake completed121 ms
5 days agoHandshake completed96 ms
6 days agoHandshake completed80 ms
8 days agoHandshake completed118 ms
11 days agoHandshake completed1.28 s
13 days agoHandshake completed52 ms
16 days agoHandshake completed103 ms
18 days agoHandshake completed61 ms
20 days agoHandshake completed69 ms
22 days agoHandshake completed1.13 s
24 days agoFailed - the request timed out—
26 days agoHandshake completed70 ms
27 days agoHandshake completed55 ms
29 days agoHandshake completed52 ms

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

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