Remote MCP · Endpoint

Elicitation-Destination Verdict MCP server

No. Elicitation-Destination Verdict answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://textforagents.com/products/elicitation-destination-verdict/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/elicitation-destination-verdict
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
24 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Grade MCP elicitation destinations against the approved set before consent.
Listing
From the official MCP registry (active).
Recent checks of Elicitation-Destination Verdict
CheckedResultHandshake
3 days agoHandshake completed24 ms
6 days agoHandshake completed64 ms
16 days agoHandshake completed44 ms
17 days agoHandshake completed63 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed43 ms
21 days agoHandshake completed54 ms
21 days agoHandshake completed49 ms
22 days agoHandshake completed43 ms
24 days agoHandshake completed47 ms
25 days agoHandshake completed53 ms

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

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