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 1 hour ago.

UpLast checked 1 hour 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
168 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 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
1 hour agoHandshake completed168 ms
1 day agoHandshake completed236 ms
2 days agoHandshake completed119 ms
3 days agoHandshake completed86 ms
4 days agoHandshake completed246 ms
5 days agoHandshake completed228 ms
6 days agoHandshake completed174 ms
9 days agoHandshake completed745 ms
12 days agoHandshake completed154 ms
14 days agoHandshake completed388 ms
16 days agoHandshake completed309 ms
18 days agoHandshake completed165 ms
20 days agoHandshake completed57 ms
22 days agoHandshake completed150 ms
25 days agoHandshake completed667 ms
26 days agoHandshake completed635 ms
28 days agoHandshake completed286 ms
29 days agoHandshake completed44 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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.

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.