Remote MCP · Endpoint

Mintlify Docs MCP server

No. Mintlify Docs answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://www.mintlify.com/docs/mcp

The last check completed an MCP handshake.

Registry name
com.mintlify/searchmcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
136 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Mintlify's own documentation: setup, the mint CLI, docs.json, components, and pricing.
Listing
From the official MCP registry (active).
Recent checks of Mintlify Docs
CheckedResultHandshake
18 minutes agoHandshake completed136 ms
10 days agoHandshake completed173 ms
10 days agoHandshake completed135 ms
11 days agoHandshake completed219 ms
13 days agoHandshake completed148 ms
14 days agoHandshake completed135 ms
14 days agoHandshake completed119 ms
15 days agoHandshake completed213 ms
17 days agoHandshake completed204 ms
19 days agoHandshake completed150 ms
21 days agoHandshake completed158 ms
24 days agoHandshake completed176 ms
26 days agoHandshake completed165 ms
28 days agoHandshake completed266 ms

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

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