Remote MCP · Endpoint

cite-gate MCP server

No. cite-gate answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.mlpc.co.kr/mcp

The last check completed an MCP handshake.

Registry name
kr.co.mlpc/cite-gate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Checks that every quote in an AI-written script appears word for word in its source.
Listing
From the official MCP registry (active).
Recent checks of cite-gate
CheckedResultHandshake
1 hour agoHandshake completed103 ms
1 day agoHandshake completed50 ms
2 days agoHandshake completed78 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed162 ms
7 days agoHandshake completed118 ms
9 days agoHandshake completed61 ms
12 days agoHandshake completed66 ms
14 days agoHandshake completed84 ms
16 days agoHandshake completed85 ms
18 days agoHandshake completed91 ms
20 days agoHandshake completed67 ms
22 days agoHandshake completed85 ms
24 days agoHandshake completed56 ms

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