Remote MCP · Endpoint

Provider Trust — Verify a Source or Provider MCP server

No. Provider Trust — Verify a Source or Provider answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://squeezeos-api.onrender.com/mcp/provider-trust

The last check completed an MCP handshake.

Registry name
com.scriptmasterlabs/provider-trust
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
280 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown.
Listing
From the official MCP registry (active).
Recent checks of Provider Trust — Verify a Source or Provider
CheckedResultHandshake
1 hour agoHandshake completed280 ms
2 days agoHandshake completed117 ms
4 days agoHandshake completed118 ms
5 days agoHandshake completed297 ms
7 days agoHandshake completed291 ms
8 days agoHandshake completed269 ms
9 days agoHandshake completed269 ms
12 days agoHandshake completed303 ms
13 days agoHandshake completed279 ms
15 days agoHandshake completed301 ms
16 days agoHandshake completed279 ms
18 days agoHandshake completed239 ms
19 days agoHandshake completed272 ms
20 days agoHandshake completed271 ms
20 days agoHandshake completed115 ms
21 days agoHandshake completed247 ms
22 days agoHandshake completed292 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 Provider Trust — Verify a Source or Provider and makes no claim about it beyond what these checks measured.