Remote MCP · Endpoint
io.github.Deesmo/arch-tools-mcp MCP server
No. io.github.Deesmo/arch-tools-mcp answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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.
- Website
- https://archtools.dev/
- Repository
- https://github.com/Deesmo/Arch-AI-Tools
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 135 ms |
| 12 hours ago | Handshake completed | 190 ms |
| 1 day ago | Handshake completed | 150 ms |
| 2 days ago | Handshake completed | 297 ms |
| 4 days ago | Handshake completed | 156 ms |
| 4 days ago | Handshake completed | 169 ms |
| 5 days ago | Handshake completed | 275 ms |
| 6 days ago | Handshake completed | 171 ms |
| 8 days ago | Handshake completed | 277 ms |
| 11 days ago | Handshake completed | 367 ms |
| 13 days ago | Handshake completed | 152 ms |
| 16 days ago | Handshake completed | 362 ms |
| 18 days ago | Handshake completed | 283 ms |
| 20 days ago | Handshake completed | 309 ms |
| 22 days ago | Handshake completed | 358 ms |
| 24 days ago | Handshake completed | 167 ms |
| 26 days ago | Handshake completed | 144 ms |
| 28 days ago | Handshake completed | 144 ms |
| 29 days ago | Handshake completed | 349 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.