Remote MCP · Endpoint

TruePeptideSource MCP server

No. TruePeptideSource answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://truepeptidesource.com/mcp

The last check completed an MCP handshake.

Registry name
com.truepeptidesource/peptides
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
663 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Peptide reference and exact math: reconstitution units, blends, supply, dose ranges by origin.
Listing
From the official MCP registry (active).
Recent checks of TruePeptideSource
CheckedResultHandshake
36 minutes agoHandshake completed663 ms
3 days agoHandshake completed222 ms
13 days agoHandshake completed171 ms
14 days agoHandshake completed229 ms
15 days agoHandshake completed163 ms
16 days agoHandshake completed121 ms
17 days agoHandshake completed141 ms
18 days agoHandshake completed145 ms
19 days agoHandshake completed132 ms
20 days agoHandshake completed212 ms
22 days agoHandshake completed178 ms
25 days agoHandshake completed129 ms

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

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