Remote MCP · Endpoint

Peptul MCP server

No. Peptul answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.peptul.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.peptul/peptul
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
162 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live research peptide prices, price history, vendor trust records and a reconstitution calculator.
Listing
From the official MCP registry (active).
Recent checks of Peptul
CheckedResultHandshake
1 hour agoHandshake completed162 ms
2 days agoHandshake completed495 ms
4 days agoHandshake completed656 ms
5 days agoHandshake completed254 ms
7 days agoHandshake completed822 ms
8 days agoHandshake completed285 ms
9 days agoHandshake completed734 ms
12 days agoHandshake completed511 ms
13 days agoHandshake completed213 ms
15 days agoHandshake completed965 ms
16 days agoHandshake completed540 ms
17 days agoHandshake completed482 ms
18 days agoHandshake completed610 ms
19 days agoHandshake completed420 ms
20 days agoHandshake completed111 ms
21 days agoHandshake completed109 ms
22 days agoHandshake completed111 ms

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

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