Remote MCP · Endpoint
Official OpenAI Announcements & Model Releases — buy per-query in-session (openaiwatch) MCP server
No. Official OpenAI Announcements & Model Releases — buy per-query in-session (openaiwatch) answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://a2awire.com/mcp/data/openaiwatch-official-openai-announcements-model-releases-1336ac/http
The last check completed an MCP handshake.
- Registry name
- com.a2awire/data-openai-announcement-model-release-news
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 152 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- OpenAI announcements: models, releases, news. $0.01/query. Register in-session — free testnet funds.
- Repository
- https://github.com/ee324/a2awire
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 152 ms |
| 2 days ago | Handshake completed | 102 ms |
| 4 days ago | Handshake completed | 698 ms |
| 6 days ago | Handshake completed | 106 ms |
| 7 days ago | Handshake completed | 86 ms |
| 8 days ago | Handshake completed | 108 ms |
| 9 days ago | Handshake completed | 484 ms |
| 12 days ago | Handshake completed | 386 ms |
| 14 days ago | Handshake completed | 271 ms |
| 15 days ago | Handshake completed | 273 ms |
| 17 days ago | Handshake completed | 333 ms |
| 18 days ago | Handshake completed | 294 ms |
| 19 days ago | Handshake completed | 145 ms |
| 20 days ago | Handshake completed | 468 ms |
| 20 days ago | Handshake completed | 203 ms |
| 22 days ago | Handshake completed | 370 ms |
| 23 days ago | Handshake completed | 113 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 Official OpenAI Announcements & Model Releases — buy per-query in-session (openaiwatch) and makes no claim about it beyond what these checks measured.