Remote MCP · Endpoint

Peptide Library MCP server

No. Peptide Library answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://peptidelibrary.app/mcp

The last check completed an MCP handshake.

Registry name
app.peptidelibrary/peptide-library
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
416 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Peptide research profiles, evidence by tier, comparisons and educational content. No dosing.
Listing
From the official MCP registry (active).
Recent checks of Peptide Library
CheckedResultHandshake
12 minutes agoHandshake completed416 ms
9 days agoHandshake completed195 ms
9 days agoHandshake completed143 ms
11 days agoHandshake completed137 ms
12 days agoHandshake completed235 ms
13 days agoHandshake completed371 ms
14 days agoHandshake completed318 ms
14 days agoHandshake completed338 ms
16 days agoHandshake completed178 ms
19 days agoHandshake completed247 ms
21 days agoHandshake completed368 ms
24 days agoHandshake completed186 ms
26 days agoHandshake completed213 ms
28 days agoHandshake completed245 ms

The last 14 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 Peptide Library and makes no claim about it beyond what these checks measured.