Remote MCP · Endpoint

gl.parse/mcp MCP server

No. gl.parse/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.parse.gl/mcp

The last check completed an MCP handshake.

Registry name
gl.parse/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
256 ms
Tools exposed
52 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
See how ChatGPT, Claude, Perplexity, and Gemini cite brands, prompts, and sources.
Listing
From the official MCP registry (active).
Recent checks of gl.parse/mcp
CheckedResultHandshake
1 hour agoHandshake completed256 ms
2 days agoHandshake completed50 ms
4 days agoHandshake completed56 ms
5 days agoHandshake completed50 ms
7 days agoHandshake completed45 ms
8 days agoHandshake completed311 ms
9 days agoHandshake completed41 ms
12 days agoHandshake completed59 ms
13 days agoHandshake completed53 ms
15 days agoHandshake completed37 ms
16 days agoHandshake completed57 ms
18 days agoHandshake completed38 ms
19 days agoHandshake completed35 ms
20 days agoHandshake completed37 ms
20 days agoHandshake completed42 ms
21 days agoHandshake completed54 ms
22 days agoHandshake completed318 ms

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

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