Remote MCP · Endpoint

MintPage MCP server

No. MintPage answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mintpage.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.hlsitechio/mintpage
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
138 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Publish Markdown or HTML as a live, shareable web page in one tool call. Guest mode needs no key.
Listing
From the official MCP registry (active).
Recent checks of MintPage
CheckedResultHandshake
34 minutes agoHandshake completed138 ms
9 days agoHandshake completed252 ms
10 days agoHandshake completed232 ms
11 days agoHandshake completed117 ms
12 days agoHandshake completed272 ms
14 days agoHandshake completed142 ms
14 days agoHandshake completed146 ms
15 days agoHandshake completed150 ms
17 days agoHandshake completed231 ms
19 days agoHandshake completed165 ms
21 days agoHandshake completed194 ms
24 days agoHandshake completed184 ms
26 days agoHandshake completed744 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.

Listing data comes from the official MCP registry. Glide is not affiliated with MintPage and makes no claim about it beyond what these checks measured.