Remote MCP · Endpoint

No-Shell Agent Architect MCP MCP server

No. No-Shell Agent Architect MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ai-automation-operating-pack.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.loved0543-dotcom/no-shell-agent-architect-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.
Listing
From the official MCP registry (active).
Recent checks of No-Shell Agent Architect MCP
CheckedResultHandshake
1 hour agoHandshake completed134 ms
1 day agoHandshake completed107 ms
2 days agoHandshake completed64 ms
3 days agoHandshake completed63 ms
4 days agoHandshake completed58 ms
5 days agoHandshake completed107 ms
6 days agoHandshake completed82 ms
9 days agoHandshake completed75 ms
11 days agoHandshake completed190 ms
14 days agoHandshake completed61 ms
16 days agoHandshake completed133 ms
18 days agoHandshake completed89 ms
20 days agoHandshake completed150 ms
22 days agoHandshake completed125 ms
24 days agoHandshake completed61 ms
26 days agoHandshake completed75 ms
27 days agoHandshake completed58 ms
29 days agoHandshake completed118 ms

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

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 No-Shell Agent Architect MCP and makes no claim about it beyond what these checks measured.