Remote MCP · Endpoint

npm Release Tracker — new Node.js packages & JavaScript dependency updates (npmwatch) MCP server

No. npm Release Tracker — new Node.js packages & JavaScript dependency updates (npmwatch) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/npmwatch-new-npm-package-releases-javascript-dependency-updates-9aad2b/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-npm-release-node-package-javascript-dependency
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
57 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
npm releases: Node package versions, daily. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/npmwatch-new-npm-package-releases-javascript-dependency-updates-9aad2b
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of npm Release Tracker — new Node.js packages & JavaScript dependency updates (npmwatch)
CheckedResultHandshake
2 hours agoHandshake completed57 ms
2 days agoHandshake completed150 ms
4 days agoHandshake completed667 ms
6 days agoHandshake completed635 ms
7 days agoHandshake completed286 ms
8 days agoHandshake completed44 ms
9 days agoHandshake completed652 ms
12 days agoHandshake completed532 ms
14 days agoHandshake completed374 ms
15 days agoHandshake completed327 ms
17 days agoHandshake completed316 ms
18 days agoHandshake completed280 ms
19 days agoHandshake completed217 ms
20 days agoHandshake completed450 ms
20 days agoHandshake completed312 ms
22 days agoHandshake completed444 ms
23 days agoHandshake completed128 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with npm Release Tracker — new Node.js packages & JavaScript dependency updates (npmwatch) and makes no claim about it beyond what these checks measured.