Remote MCP · Endpoint

NewVSTs MCP server

No. NewVSTs answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://newvsts.com/mcp

The last check completed an MCP handshake.

Registry name
com.newvsts/newvsts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
New audio plugin releases and intro deals: live prices, deal end dates, format/OS filters.
Website
https://newvsts.com/developers/
Listing
From the official MCP registry (active).
Recent checks of NewVSTs
CheckedResultHandshake
6 days agoHandshake completed62 ms
7 days agoHandshake completed109 ms
7 days agoHandshake completed108 ms
9 days agoHandshake completed74 ms
10 days agoHandshake completed43 ms
11 days agoHandshake completed110 ms
12 days agoHandshake completed82 ms
13 days agoHandshake completed99 ms
15 days agoHandshake completed398 ms
17 days agoHandshake completed96 ms
20 days agoHandshake completed148 ms
22 days agoHandshake completed84 ms
24 days agoHandshake completed102 ms

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

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