Remote MCP · Endpoint

AgentScout MCP server

No. AgentScout answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://agentscout-mcp.agentscouthq.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
com.agentscouthq/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
260 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only search over 1,771 AI agent tools and 248 MCP servers. No sign-up needed.
Listing
From the official MCP registry (active).
Recent checks of AgentScout
CheckedResultHandshake
37 minutes agoHandshake completed260 ms
4 days agoHandshake completed335 ms
7 days agoHandshake completed148 ms
16 days agoHandshake completed191 ms
16 days agoHandshake completed86 ms
18 days agoHandshake completed103 ms
19 days agoHandshake completed104 ms
20 days agoHandshake completed112 ms
21 days agoHandshake completed68 ms
22 days agoHandshake completed102 ms
23 days agoHandshake completed105 ms
26 days agoHandshake completed58 ms
29 days agoHandshake completed65 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 AgentScout and makes no claim about it beyond what these checks measured.