Remote MCP · Endpoint
Mode VC Chart: Open Weights vs. Proprietary AI: The Gap Stays at 42 Points MCP server
No. Mode VC Chart: Open Weights vs. Proprietary AI: The Gap Stays at 42 Points answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://modevc.com/api/mcp/chart-open-weights-vs-proprietary-arena-gap
The last check completed an MCP handshake.
- Registry name
- com.modevc/chart-open-weights-vs-proprietary-arena-gap
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 100 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Open weights briefly beat every proprietary model in early 2025 (deepseek-r1); today the best.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 100 ms |
| 2 days ago | Handshake completed | 95 ms |
| 4 days ago | Handshake completed | 94 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Mode VC Chart: Open Weights vs. Proprietary AI: The Gap Stays at 42 Points and makes no claim about it beyond what these checks measured.