Remote MCP · Endpoint

Figshare MCP server

No. Figshare answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/figshare/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/figshare
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
51 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Figshare MCP.
Website
https://pipeworx.io/packs/figshare
Repository
https://github.com/pipeworx-io/mcp-figshare
Listing
From the official MCP registry (active).
Recent checks of Figshare
CheckedResultHandshake
1 hour agoHandshake completed185 ms
1 day agoHandshake completed274 ms
2 days agoHandshake completed261 ms
3 days agoHandshake completed154 ms
4 days agoHandshake completed95 ms
5 days agoHandshake completed245 ms
6 days agoHandshake completed622 ms
8 days agoHandshake completed706 ms
11 days agoHandshake completed68 ms
13 days agoHandshake completed59 ms
16 days agoHandshake completed93 ms
18 days agoHandshake completed69 ms
20 days agoHandshake completed140 ms
22 days agoHandshake completed58 ms
24 days agoHandshake completed52 ms
26 days agoHandshake completed61 ms
27 days agoHandshake completed69 ms
29 days agoHandshake completed42 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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