Antideploy
NPM · ANTIDEPLOY-MCP · SCANNED SEP 26
Deploy an app to Antideploy from a coding agent. No Dockerfile, no YAML, no cloud console.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 370 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Antideploy MCP server?
Antideploy runs locally as an npm package, launched with npx -y antideploy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · antideploy-mcp
claude mcp add com-antideploy-antideploy-mcp -- npx -y antideploy-mcp
{
"mcpServers": {
"com-antideploy-antideploy-mcp": {
"command": "npx",
"args": [
"-y",
"antideploy-mcp"
]
}
}
} {
"servers": {
"com-antideploy-antideploy-mcp": {
"command": "npx",
"args": [
"-y",
"antideploy-mcp"
]
}
}
} codex mcp add com-antideploy-antideploy-mcp -- npx -y antideploy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-antideploy-antideploy-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"antideploy-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-antideploy-antideploy-mcp --command npx --arg -y --arg antideploy-mcp
mcp_servers:
com-antideploy-antideploy-mcp:
command: "npx"
args: ["-y", "antideploy-mcp"] {
"McpServers": {
"com-antideploy-antideploy-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"antideploy-mcp"
]
}
}
} assistant mcp add com-antideploy-antideploy-mcp -t stdio -c npx -a -y antideploy-mcp
{
"mcpServers": {
"com-antideploy-antideploy-mcp": {
"command": "npx",
"args": [
"-y",
"antideploy-mcp"
]
}
}
} 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.
- 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
- 20 Sept 26 69
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 26 Sept 2026 · Analysed npm/antideploy-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
api_info Read the API's own manual ~34
The platform's self-description: endpoints, limits and current behaviour. Worth reading whenever something here disagrees with what the server does.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deploy Deploy the project ~155
Package a project directory and deploy it. Sends the whole directory, not just an entry point — a deploy containing one file builds successfully and then serves a page whose assets all 404. Returns a taskId to poll with `deployment_status`. A `.env` in the directory is uploaded on purpose: the values go into the encrypted secret store and the file itself is dropped from the build. Say so if the user may not expect it.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Project directory. Defaults to the working directory of this server. |
| env | object | – | Variables to store with this deploy. Write-only; never readable back. |
| force | boolean | – | Rebuild even when the content is byte-for-byte identical to the last deploy. |
No output schema declared.
No examples provided.
deployment_status Check a deployment ~51
Progress for one deployment: status, per-step detail, the analyzed spec, warnings and hazards. Poll until the status is succeeded or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | The taskId returned by `deploy`. |
No output schema declared.
No examples provided.
list_env List environment variable names ~20
Names only. The platform never returns values, by design.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_env Set environment variables ~35
Store or replace environment variables for this application. Write-only.
| Name | Type | Req | Description |
|---|---|---|---|
| env | object | yes | Variables to store, as name/value pairs. |
No output schema declared.
No examples provided.
What is the Antideploy MCP server?
Antideploy is an MCP server listed in the public MCP registry as com.antideploy/antideploy-mcp. Deploy an app to Antideploy from a coding agent. No Dockerfile, no YAML, no cloud console. This page covers its npm package (antideploy-mcp).
Is the Antideploy MCP server safe to use?
Antideploy scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 Antideploy MCP server expose?
Antideploy exposes 5 tools: deploy, deployment_status, list_env, set_env, api_info. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Is the Antideploy MCP server still maintained?
Antideploy is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Antideploy MCP server under?
Antideploy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.