No-Shell Agent Architect MCP
REMOTE · AI-AUTOMATION-OPERATING-PACK.VERCEL.APP · SCANNED SEP 24
Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 685 tokens (~97/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the No-Shell Agent Architect MCP server?
No-Shell Agent Architect MCP is a hosted endpoint at https://ai-automation-operating-pack.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai-automation-operating-pack.vercel.app
claude mcp add --transport http loved0543-dotcom-no-shell-agent-architect-mcp 'https://ai-automation-operating-pack.vercel.app/api/mcp'
{
"mcpServers": {
"loved0543-dotcom-no-shell-agent-architect-mcp": {
"url": "https://ai-automation-operating-pack.vercel.app/api/mcp"
}
}
} {
"servers": {
"loved0543-dotcom-no-shell-agent-architect-mcp": {
"type": "http",
"url": "https://ai-automation-operating-pack.vercel.app/api/mcp"
}
}
} [mcp_servers.loved0543-dotcom-no-shell-agent-architect-mcp] url = "https://ai-automation-operating-pack.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"loved0543-dotcom-no-shell-agent-architect-mcp": {
"type": "remote",
"url": "https://ai-automation-operating-pack.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add loved0543-dotcom-no-shell-agent-architect-mcp --url 'https://ai-automation-operating-pack.vercel.app/api/mcp' --transport streamable-http
mcp_servers:
loved0543-dotcom-no-shell-agent-architect-mcp:
url: "https://ai-automation-operating-pack.vercel.app/api/mcp" {
"McpServers": {
"loved0543-dotcom-no-shell-agent-architect-mcp": {
"Transport": "http",
"Url": "https://ai-automation-operating-pack.vercel.app/api/mcp"
}
}
} assistant mcp add loved0543-dotcom-no-shell-agent-architect-mcp -t streamable-http -u 'https://ai-automation-operating-pack.vercel.app/api/mcp'
{
"mcpServers": {
"loved0543-dotcom-no-shell-agent-architect-mcp": {
"type": "http",
"url": "https://ai-automation-operating-pack.vercel.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://ai-automation-operating-pack.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai-automation-operating-pack.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-automation-operating-pack.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://ai-automation-operating-pack.vercel.app/api/mcp | HTTPS enforced | 308 | https://ai-automation-operating-pack.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_automation_plan Audit Automation Plan ~47
Score an existing automation plan for shell-risk, missing inputs, missing validation, missing tool route, and missing recovery path.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | yes | Automation plan or prompt to audit. |
No output schema declared.
No examples provided.
build_customer_intake Build Customer Intake ~35
Generate a 10-minute intake questionnaire for a non-developer who wants one workflow automated.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | – |
No output schema declared.
No examples provided.
build_m2m_package_contract Build M2M Package Contract ~186
Create a machine-readable package contract for agencies, SaaS builders, or other agents that want to integrate the No-Shell operating pack through MCP/API plus human-readable delivery artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerType | string | – | Agency, freelancer, SaaS builder, solo operator, internal ops team, etc. |
| currentTools | array | – | Tools/plugins/MCPs already available to the user. |
| domain | string | – | Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding. |
| goal | string | yes | Plain-language automation goal. |
| language | string | – | – |
| packageMode | string | – | mcp_api, starter_pack, agency_workbench, connector_pack, or a custom packaging mode. |
| risk | string | – | – |
| userType | string | – | Non-developer, solo operator, small team, developer, agency, etc. |
No output schema declared.
No examples provided.
build_validation_pack Build Validation Pack ~46
Return dry-run, QA, audit, and PASS criteria for one automation workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| goal | string | yes | – |
| risk | string | – | – |
No output schema declared.
No examples provided.
design_automation_stack Design Automation Stack ~129
Turn a vague automation request into a tool/MCP/plugin/skill stack, permissioned account route, workflow phases, validation pack, and live-action boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| currentTools | array | – | Tools/plugins/MCPs already available to the user. |
| domain | string | – | Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding. |
| goal | string | yes | Plain-language automation goal. |
| language | string | – | – |
| risk | string | – | – |
| userType | string | – | Non-developer, solo operator, small team, developer, agency, etc. |
No output schema declared.
No examples provided.
generate_no_shell_prompt Generate No-Shell Prompt ~121
Create a copy-paste natural-language command that tells an agent how to execute the workflow without producing an empty shell.
| Name | Type | Req | Description |
|---|---|---|---|
| currentTools | array | – | Tools/plugins/MCPs already available to the user. |
| domain | string | – | Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding. |
| goal | string | yes | Plain-language automation goal. |
| language | string | – | – |
| risk | string | – | – |
| userType | string | – | Non-developer, solo operator, small team, developer, agency, etc. |
No output schema declared.
No examples provided.
recommend_agent_tools Recommend Agent Tools ~121
Recommend MCP servers, Codex plugins, skills, permissioned account routes, and live-action boundaries for a requested automation.
| Name | Type | Req | Description |
|---|---|---|---|
| currentTools | array | – | Tools/plugins/MCPs already available to the user. |
| domain | string | – | Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding. |
| goal | string | yes | Plain-language automation goal. |
| language | string | – | – |
| risk | string | – | – |
| userType | string | – | Non-developer, solo operator, small team, developer, agency, etc. |
No output schema declared.
No examples provided.
What is the No-Shell Agent Architect MCP server?
No-Shell Agent Architect MCP is listed in the public MCP registry as io.github.loved0543-dotcom/no-shell-agent-architect-mcp. Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries. This page covers its hosted endpoint (https://ai-automation-operating-pack.vercel.app/api/mcp).
Is the No-Shell Agent Architect MCP server safe to use?
No-Shell Agent Architect MCP scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the No-Shell Agent Architect MCP server expose?
No-Shell Agent Architect MCP exposes 7 tools: design_automation_stack, generate_no_shell_prompt, recommend_agent_tools, audit_automation_plan, build_validation_pack, and 2 more. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.
Does the No-Shell Agent Architect MCP server require authentication?
No. We connected to No-Shell Agent Architect MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the No-Shell Agent Architect MCP server still maintained?
No-Shell Agent Architect MCP is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.