Remote MCP · Endpoint

Bing News MCP server

No. Bing News answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/bing-news/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/bing-news
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Bing News MCP — keyword news search via Bing News RSS, keyless.
Listing
From the official MCP registry (active).
Recent checks of Bing News
CheckedResultHandshake
2 hours agoHandshake completed85 ms
20 hours agoHandshake completed81 ms
1 day agoHandshake completed106 ms
2 days agoHandshake completed942 ms
4 days agoHandshake completed1.59 s
7 days agoHandshake completed901 ms
9 days agoHandshake completed4.04 s
12 days agoHandshake completed844 ms
14 days agoHandshake completed191 ms
16 days agoHandshake completed79 ms
18 days agoHandshake completed1.02 s
20 days agoHandshake completed368 ms
22 days agoHandshake completed59 ms
24 days agoHandshake completed1.01 s

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

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