Remote MCP · Endpoint

New Runtime public records MCP server

No. New Runtime public records answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://newruntime.com/mcp

The last check completed an MCP handshake.

Registry name
com.newruntime/archive
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
288 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI-engineering archive: search, what is new, forecasts, URL context; paid x402 research tools.
Listing
From the official MCP registry (active).
Recent checks of New Runtime public records
CheckedResultHandshake
56 minutes agoHandshake completed288 ms
3 days agoHandshake completed302 ms
12 days agoHandshake completed308 ms
13 days agoHandshake completed342 ms
15 days agoHandshake completed687 ms
15 days agoHandshake completed342 ms
17 days agoHandshake completed283 ms
18 days agoHandshake completed304 ms
18 days agoHandshake completed365 ms
20 days agoHandshake completed291 ms
22 days agoHandshake completed392 ms
25 days agoHandshake completed285 ms
27 days agoHandshake completed288 ms
29 days agoHandshake completed317 ms

The last 14 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.

Listing data comes from the official MCP registry. Glide is not affiliated with New Runtime public records and makes no claim about it beyond what these checks measured.