Remote MCP · Endpoint

Liberty.win MCP server

No. Liberty.win answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://liberty.win/mcp

The last check completed an MCP handshake.

Registry name
win.liberty/liberty-win
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free speech forum for life, liberty, and property. Read, post, and vote on news that moves people.
Website
https://liberty.win/
Listing
From the official MCP registry (active).
Recent checks of Liberty.win
CheckedResultHandshake
1 hour agoHandshake completed129 ms
1 day agoHandshake completed150 ms
4 days agoHandshake completed136 ms
6 days agoHandshake completed130 ms
9 days agoHandshake completed129 ms
11 days agoHandshake completed124 ms
13 days agoHandshake completed130 ms
15 days agoHandshake completed208 ms
17 days agoHandshake completed343 ms
19 days agoHandshake completed146 ms
20 days agoHandshake completed138 ms
22 days agoHandshake completed121 ms
23 days agoHandshake completed125 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 Liberty.win and makes no claim about it beyond what these checks measured.