Remote MCP · Endpoint

Agent Tools MCP MCP server

No. Agent Tools MCP answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://agent-tools-mcp.yvan11.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.why-see/agent-tools-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
227 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
32 free MCP tools for data validation, text optimization, and synthetic test data.
Listing
From the official MCP registry (active).
Recent checks of Agent Tools MCP
CheckedResultHandshake
34 minutes agoHandshake completed227 ms
9 days agoHandshake completed248 ms
10 days agoHandshake completed217 ms
11 days agoHandshake completed239 ms
12 days agoHandshake completed502 ms
14 days agoHandshake completed248 ms
14 days agoHandshake completed205 ms
15 days agoHandshake completed259 ms
17 days agoHandshake completed691 ms
19 days agoHandshake completed136 ms
21 days agoHandshake completed218 ms
24 days agoHandshake completed466 ms
26 days agoHandshake completed540 ms
28 days agoHandshake completed121 ms

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

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 Agent Tools MCP and makes no claim about it beyond what these checks measured.