Remote MCP · Endpoint

io.github.Deesmo/arch-tools-mcp MCP server

No. io.github.Deesmo/arch-tools-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://archtools.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Deesmo/arch-tools-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
63 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
63 production tools for AI agents — one API key, pay per call in USDC (x402) or Stripe credits.
Listing
From the official MCP registry (active).
Recent checks of io.github.Deesmo/arch-tools-mcp
CheckedResultHandshake
1 hour agoHandshake completed135 ms
11 hours agoHandshake completed190 ms
1 day agoHandshake completed150 ms
2 days agoHandshake completed297 ms
4 days agoHandshake completed156 ms
4 days agoHandshake completed169 ms
5 days agoHandshake completed275 ms
6 days agoHandshake completed171 ms
8 days agoHandshake completed277 ms
11 days agoHandshake completed367 ms
13 days agoHandshake completed152 ms
16 days agoHandshake completed362 ms
18 days agoHandshake completed283 ms
20 days agoHandshake completed309 ms
22 days agoHandshake completed358 ms
24 days agoHandshake completed167 ms
26 days agoHandshake completed144 ms
27 days agoHandshake completed144 ms
29 days agoHandshake completed349 ms

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

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 io.github.Deesmo/arch-tools-mcp and makes no claim about it beyond what these checks measured.