Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.
MCPpedia last refreshed this data
io.github.loved0543-dotcom/no-shell-agent-architect-mcp is an MCP server that turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries. Its tool list has not been published yet over http, requires no API key, and scores 79/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"no-shell-agent-architect": {
"url": "https://ai-automation-operating-pack.vercel.app/api/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
System 1 decision models (Jev, Laya, Cua-S1) as brain for agents: Browser use, computer use, games and robotics
MCP Security Weekly
Get CVE alerts and security updates for io.github.loved0543-dotcom/no-shell-agent-architect-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An open-source operating pack for people who already use AI agents but keep getting "empty-shell automation": files, buttons, or dashboards that look finished but do not actually run a real workflow.
This is not a prompt-pack that promises magic. It is a plain-language operating system for delegating work to ChatGPT, Claude, Codex, Gemini, Hermes, and similar agents with a real objective, inputs, tool choice, permissioned account route, validation, recovery, and live-action boundary.
This repository now also ships a remote MCP/API product: No-Shell Agent Architect MCP.
Current launch mode: free public beta. There is no payment flow, usage gate, paid API call, or private customer data collection in this version. The goal is to observe GitHub stars, issues, workflow feedback, and real usage before deciding whether a paid version should exist later.
It takes a plain-language automation goal and returns:
Local API preview:
npm install
npm run dev
Then open:
http://localhost:3000
Canonical remote MCP endpoint:
https://ai-automation-operating-pack.vercel.app/api/mcp
Live demo:
https://ai-automation-operating-pack.vercel.app
Launch kit:
https://ai-automation-operating-pack.vercel.app/launch
Public beta feedback:
https://github.com/loved0543-dotcom/no-shell-agent-operating-pack/issues/1
Machine-readable M2M package contract:
https://ai-automation-operating-pack.vercel.app/api/m2m-package
Official MCP Registry:
https://registry.modelcontextprotocol.io/v0/servers?search=no-shell-agent-architect-mcp
Compatibility URL:
https://no-shell-agent-architect-mcp.vercel.app
The compatibility URL is kept for old shared links only. New docs, client config, and registry metadata should use https://ai-automation-operating-pack.vercel.app.
Client config:
{
"mcpServers": {
"no-shell-agent-architect": {
"url": "https://ai-automation-operating-pack.vercel.app/api/mcp"
}
}
}
free/ai_automation_failure_diagnostic_card.md.demo/before_after_email_document_demo.md.delivery/01_customer_intake.md to d