Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

No-Shell Agent Architect MCP

REMOTE · AI-AUTOMATION-OPERATING-PACK.VERCEL.APP

Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.

0 this week 78 Trust /100

Last scanned (13 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Workflow Automation

Trust breakdown (7 categories)

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
Transport & Reachability100
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Sept 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
  • 25 Sept 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 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
Diagnostics

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 21 Nov 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 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
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. DS published 23684 8 Verified
vercel.app. No DS 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
MCP tools · 7 exposed · ~685 tokens

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 →

Tool Tokens
audit_automation_plan ~47

Score an existing automation plan for shell-risk, missing inputs, missing validation, missing tool route, and missing recovery path.

NameTypeReqDescription
planstringyesAutomation plan or prompt to audit.

No output schema declared.

No examples provided.

build_customer_intake ~35

Generate a 10-minute intake questionnaire for a non-developer who wants one workflow automated.

NameTypeReqDescription
goalstring––

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
buyerTypestring–Agency, freelancer, SaaS builder, solo operator, internal ops team, etc.
currentToolsarray–Tools/plugins/MCPs already available to the user.
domainstring–Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding.
goalstringyesPlain-language automation goal.
languagestring––
packageModestring–mcp_api, starter_pack, agency_workbench, connector_pack, or a custom packaging mode.
riskstring––
userTypestring–Non-developer, solo operator, small team, developer, agency, etc.

No output schema declared.

No examples provided.

build_validation_pack ~46

Return dry-run, QA, audit, and PASS criteria for one automation workflow.

NameTypeReqDescription
domainstring––
goalstringyes–
riskstring––

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
currentToolsarray–Tools/plugins/MCPs already available to the user.
domainstring–Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding.
goalstringyesPlain-language automation goal.
languagestring––
riskstring––
userTypestring–Non-developer, solo operator, small team, developer, agency, etc.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
currentToolsarray–Tools/plugins/MCPs already available to the user.
domainstring–Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding.
goalstringyesPlain-language automation goal.
languagestring––
riskstring––
userTypestring–Non-developer, solo operator, small team, developer, agency, etc.

No output schema declared.

No examples provided.

recommend_agent_tools ~121

Recommend MCP servers, Codex plugins, skills, permissioned account routes, and live-action boundaries for a requested automation.

NameTypeReqDescription
currentToolsarray–Tools/plugins/MCPs already available to the user.
domainstring–Optional domain hint such as email_docs, ecommerce_data, knowledge_base, coding.
goalstringyesPlain-language automation goal.
languagestring––
riskstring––
userTypestring–Non-developer, solo operator, small team, developer, agency, etc.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http loved0543-dotcom-no-shell-agent-architect-mcp 'https://ai-automation-operating-pack.vercel.app/api/mcp'
Common questions

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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the No-Shell Agent Architect MCP server?

VerifyMCP ran 12 checks on No-Shell Agent Architect MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about No-Shell Agent Architect MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.