Remote MCP · Endpoint

Agent Data Tools: Utilities MCP server

No. Agent Data Tools: Utilities answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://agent-data-tools.revmesh2074.workers.dev/mcp/utilities

The last check completed an MCP handshake.

Registry name
io.github.Nutshell2000/agent-data-tools-utilities
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
111 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
111 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
Listing
From the official MCP registry (active).
Recent checks of Agent Data Tools: Utilities
CheckedResultHandshake
12 minutes agoHandshake completed213 ms
9 days agoHandshake completed793 ms
9 days agoHandshake completed62 ms
11 days agoHandshake completed879 ms
12 days agoHandshake completed73 ms
13 days agoHandshake completed964 ms
14 days agoHandshake completed56 ms
15 days agoHandshake completed76 ms
16 days agoHandshake completed54 ms
19 days agoHandshake completed108 ms
21 days agoHandshake completed73 ms
24 days agoHandshake completed298 ms
26 days agoHandshake completed159 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 Agent Data Tools: Utilities and makes no claim about it beyond what these checks measured.