Remote MCP · Endpoint

Artifact Publisher MCP server

No. Artifact Publisher answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://app.artifactpublisher.com/mcp

The last check completed an MCP handshake.

Registry name
com.artifactpublisher/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
645 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agents publish self-contained HTML to a stable review link, with page-level feedback and revoke.
Listing
From the official MCP registry (active).
Recent checks of Artifact Publisher
CheckedResultHandshake
52 minutes agoHandshake completed645 ms
3 days agoHandshake completed585 ms
12 days agoHandshake completed622 ms
13 days agoHandshake completed774 ms
14 days agoHandshake completed834 ms
15 days agoHandshake completed801 ms
17 days agoHandshake completed810 ms
18 days agoHandshake completed713 ms
18 days agoHandshake completed557 ms
20 days agoHandshake completed993 ms
22 days agoHandshake completed661 ms
25 days agoHandshake completed798 ms
27 days agoHandshake completed1.36 s
29 days agoHandshake completed815 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 Artifact Publisher and makes no claim about it beyond what these checks measured.