Remote MCP · Endpoint

Bindingdb MCP server

No. Bindingdb answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes 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
49 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 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
12 minutes agoHandshake completed49 ms
9 days agoHandshake completed119 ms
9 days agoHandshake completed66 ms
11 days agoHandshake completed159 ms
12 days agoHandshake completed114 ms
13 days agoHandshake completed76 ms
14 days agoHandshake completed126 ms
15 days agoHandshake completed170 ms
16 days agoHandshake completed62 ms
19 days agoHandshake completed88 ms
22 days agoHandshake completed57 ms
24 days agoHandshake completed208 ms
26 days agoHandshake completed53 ms
28 days agoHandshake completed81 ms

The last 14 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.

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.