Remote MCP · Endpoint

MintPage MCP server

No. MintPage answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://mintpage-mcp.netlify.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.hlsitechio/mintpage
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.73 s
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 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
57 minutes agoHandshake completed1.73 s
3 days agoHandshake completed121 ms
12 days agoHandshake completed419 ms
13 days agoHandshake completed354 ms
15 days agoHandshake completed224 ms
15 days agoHandshake completed116 ms
17 days agoHandshake completed117 ms
18 days agoHandshake completed147 ms
18 days agoHandshake completed142 ms
20 days agoHandshake completed1.60 s
22 days agoHandshake completed120 ms
25 days agoHandshake completed311 ms
27 days agoHandshake completed238 ms
29 days agoHandshake completed613 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 MintPage and makes no claim about it beyond what these checks measured.