Remote MCP · Endpoint
ai.promptarch/mcp MCP server
No. ai.promptarch/mcp answered an MCP handshake 8 hours ago.
UpLast checked 8 hours ago
Server URL
https://mcp.promptarch.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.promptarch/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 712 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Research-backed linting + generation for agent context files (CLAUDE.md, AGENTS.md, Cursor rules).
- Website
- https://promptarch.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 8 hours ago | Handshake completed | 712 ms |
| 2 days ago | Handshake completed | 624 ms |
| 4 days ago | Handshake completed | 609 ms |
| 5 days ago | Handshake completed | 475 ms |
| 7 days ago | Handshake completed | 786 ms |
| 8 days ago | Handshake completed | 600 ms |
| 9 days ago | Handshake completed | 545 ms |
| 12 days ago | Handshake completed | 751 ms |
| 13 days ago | Handshake completed | 471 ms |
| 15 days ago | Handshake completed | 591 ms |
| 16 days ago | Handshake completed | 493 ms |
| 17 days ago | Handshake completed | 675 ms |
| 18 days ago | Handshake completed | 719 ms |
| 19 days ago | Handshake completed | 554 ms |
| 20 days ago | Handshake completed | 793 ms |
| 21 days ago | Handshake completed | 444 ms |
| 23 days ago | Handshake completed | 458 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 ai.promptarch/mcp and makes no claim about it beyond what these checks measured.