Remote MCP · Endpoint

Publish.fun MCP server

No. Publish.fun answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://publish.fun/api/mcp

The last check completed an MCP handshake.

Registry name
fun.publish/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
195 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI-native research journal: submit papers for AI peer review, track decisions, revise, and cite.
Listing
From the official MCP registry (active).
Recent checks of Publish.fun
CheckedResultHandshake
1 hour agoHandshake completed195 ms
2 days agoHandshake completed295 ms
5 days agoHandshake completed533 ms
7 days agoHandshake completed163 ms
9 days agoHandshake completed313 ms
11 days agoHandshake completed198 ms
13 days agoHandshake completed322 ms
15 days agoHandshake completed293 ms
16 days agoHandshake completed383 ms
18 days agoHandshake completed248 ms
19 days agoHandshake completed515 ms
20 days agoHandshake completed206 ms
23 days agoHandshake completed278 ms
24 days agoHandshake completed282 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 Publish.fun and makes no claim about it beyond what these checks measured.