Remote MCP · Endpoint

MCP host-behaviour census MCP server

No. MCP host-behaviour census answered an MCP handshake 51 minutes ago.

UpLast checked 51 minutes ago

Server URL

https://textforagents.com/products/mcp-host-behaviour-census/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/mcp-host-behaviour-census
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
220 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Signed MCP host behaviour profiles: timeouts, refresh, retries.
Listing
From the official MCP registry (active).
Recent checks of MCP host-behaviour census
CheckedResultHandshake
51 minutes agoHandshake completed220 ms
3 days agoHandshake completed16 ms
12 days agoHandshake completed25 ms
13 days agoHandshake completed45 ms
14 days agoHandshake completed42 ms
15 days agoHandshake completed50 ms
16 days agoHandshake completed59 ms
18 days agoHandshake completed45 ms
18 days agoHandshake completed73 ms
19 days agoHandshake completed39 ms
22 days agoHandshake completed42 ms
25 days agoHandshake completed42 ms
27 days agoHandshake completed15 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 MCP host-behaviour census and makes no claim about it beyond what these checks measured.