basicdeploy-mcp

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

basicdeploy-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

.claude-plugin/plugin.json · 24 lines

What it actually says

{
  "name": "basicdeploy-mcp",
  "displayName": "BasicDeploy",
  "version": "1.0.7",
  "description": "Deploy and manage BasicDeploy containers from your agent — Postgres, S3-compatible storage, env vars, and a public HTTPS URL, all in one MCP call.",
  "author": {
    "name": "Akacia",
    "url": "https://basicdeploy.com"
  },
  "homepage": "https://basicdeploy.com/docs",
  "repository": "https://github.com/AkaciaNL/basicdeploy-mcp",
  "license": "MIT",
  "keywords": [
    "mcp",
    "deploy",
    "hosting",
    "containers",
    "postgres",
    "s3",
    "agent"
  ],
  "mcpServers": "./.claude-plugin/mcp.json"
}

Files

What ships with it

2 files beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other plugins, from other repositories