Remote MCP · Endpoint

Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch) MCP server

No. Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/techlaunchwatch-agent-tool-releases-tech-announcements-be9b9e/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-agent-tool-release-tech-announcement-tracker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
63 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent & dev-tool releases daily: versions, changelogs. Register in-session — free testnet funds.
Website
https://a2awire.com/data/techlaunchwatch-agent-tool-releases-tech-announcements-be9b9e
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch)
CheckedResultHandshake
2 hours agoHandshake completed63 ms
2 days agoHandshake completed72 ms
4 days agoHandshake completed41 ms
6 days agoHandshake completed45 ms
7 days agoHandshake completed53 ms
8 days agoHandshake completed72 ms
9 days agoHandshake completed519 ms
12 days agoHandshake completed561 ms
14 days agoHandshake completed536 ms
15 days agoHandshake completed349 ms
17 days agoHandshake completed468 ms
18 days agoHandshake completed321 ms
19 days agoHandshake completed352 ms
20 days agoHandshake completed559 ms
20 days agoHandshake completed368 ms
22 days agoHandshake completed367 ms
23 days agoHandshake completed552 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 Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch) and makes no claim about it beyond what these checks measured.