Remote MCP · Endpoint

Agent Tools MCP server

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

UpLast checked 33 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
dev.workers.jbarkules.agent-tools/agent-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
61 ms
Tools exposed
53 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
x402 agent tools: invoice/PDF extract, OCR, email risk, web to markdown, domain, FX, time
Listing
From the official MCP registry (deprecated).
Recent checks of Agent Tools
CheckedResultHandshake
33 minutes agoHandshake completed61 ms
3 days agoHandshake completed451 ms
13 days agoHandshake completed70 ms
13 days agoHandshake completed328 ms
15 days agoHandshake completed52 ms
16 days agoHandshake completed233 ms
17 days agoHandshake completed686 ms
18 days agoHandshake completed82 ms
18 days agoHandshake completed258 ms
20 days agoHandshake completed227 ms
22 days agoHandshake completed77 ms
25 days agoHandshake completed72 ms
27 days agoHandshake completed212 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 Tools and makes no claim about it beyond what these checks measured.