Remote MCP · Endpoint

Sampling Quota Guard MCP server

No. Sampling Quota Guard answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://textforagents.com/products/sampling-quota-guard/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/sampling-quota-guard
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
41 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Per-server MCP sampling allowance, scope clamp and pre-connect verdict.
Listing
From the official MCP registry (active).
Recent checks of Sampling Quota Guard
CheckedResultHandshake
30 minutes agoHandshake completed41 ms
3 days agoHandshake completed46 ms
13 days agoHandshake completed18 ms
14 days agoHandshake completed20 ms
15 days agoHandshake completed16 ms
16 days agoHandshake completed15 ms
17 days agoHandshake completed15 ms
18 days agoHandshake completed14 ms
19 days agoHandshake completed14 ms
21 days agoHandshake completed14 ms
23 days agoHandshake completed13 ms
25 days agoHandshake completed15 ms
28 days agoHandshake completed16 ms

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

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