Remote MCP · Endpoint

JapanFold MCP server

No. JapanFold answered an MCP handshake 17 minutes ago.

Up · key neededLast checked 17 minutes ago

Server URL

https://api.japanfold.aiand.com/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
io.github.japanfold/japanfold
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.09 s
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Fold proteins, co-fold ligands with binding affinity, design binders and embed sequences.
Listing
From the official MCP registry (active).
Recent checks of JapanFold
CheckedResultHandshake
17 minutes agoHandshake completed1.09 s
9 days agoHandshake completed456 ms
9 days agoHandshake completed462 ms
11 days agoHandshake completed636 ms
12 days agoHandshake completed619 ms
13 days agoHandshake completed653 ms
14 days agoHandshake completed815 ms
14 days agoHandshake completed622 ms
16 days agoHandshake completed664 ms
19 days agoHandshake completed795 ms
21 days agoHandshake completed643 ms
24 days agoHandshake completed679 ms
26 days agoHandshake completed667 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 JapanFold and makes no claim about it beyond what these checks measured.