Remote MCP · Endpoint

Bindingdb MCP server

No. Bindingdb answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/bindingdb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
BindingDB — measured protein/small-molecule binding affinities.
Listing
From the official MCP registry (active).
Recent checks of Bindingdb
CheckedResultHandshake
1 day agoHandshake completed82 ms
3 days agoHandshake completed58 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed1.17 s
8 days agoHandshake completed1.23 s
9 days agoHandshake completed1.79 s
11 days agoHandshake completed1.23 s
14 days agoHandshake completed944 ms
15 days agoHandshake completed1.11 s
17 days agoHandshake completed139 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed39 ms
20 days agoHandshake completed48 ms
21 days agoHandshake completed37 ms
22 days agoHandshake completed43 ms

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

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 Bindingdb and makes no claim about it beyond what these checks measured.