DeployStackBLOCK
Open source MCP hosting - deploy MCP servers to HTTP endpoints for n8n, Dify, Voiceflow, and any MCP client.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
🚀 Try it out · 🌐 Website · 📚 Documentation · Roadmap · Discord
Deploy MCP servers from GitHub to HTTP endpoints in 30 seconds. Works with n8n, Dify, Voiceflow, Langflow, Claude Code, Cursor, and any MCP client.
The Problem
Most MCP servers are stdio-only. But workflow automation platforms need HTTP endpoints.
Current workarounds are painful:
mcp-remoterequires local Node.js setup- Docker containers need DevOps expertise
- DIY hosting (Fly.io, Railway) takes hours
23b5e5727cd6OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add satellite --env COOKIE_SECRET=${COOKIE_SECRET} --env DEPLOYSTACK_ENCRYPTION_SECRET=${DEPLOYSTACK_ENCRYPTION_SECRET} --env DEPLOYSTACK_REGISTRATION_TOKEN=${DEPLOYSTACK_REGISTRATION_TOKEN} --env JWT_SECRET=${JWT_SECRET} -- npx -y @deploystack/[email protected]{
"mcpServers": {
"satellite": {
"command": "npx",
"args": [
"-y",
"@deploystack/[email protected]"
],
"env": {
"COOKIE_SECRET": "${COOKIE_SECRET}",
"DEPLOYSTACK_ENCRYPTION_SECRET": "${DEPLOYSTACK_ENCRYPTION_SECRET}",
"DEPLOYSTACK_REGISTRATION_TOKEN": "${DEPLOYSTACK_REGISTRATION_TOKEN}",
"JWT_SECRET": "${JWT_SECRET}"
}
}
}
}Exposed tools (14)
10 read · 4 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
Name | read | Description |
TEST_VAR | read | Test variable |
create_issue | write | Create GitHub issue |
discover_mcp_tools | read | Search for MCP tools using 1-3 keywords only. Examples: |
example_tool | read | Example tool |
execute_mcp_tool | write | Execute a discovered MCP tool by its path. Use after discovering tools with discover_mcp_tools. The tool_path format is |
list_mcp_resources | read | List all available MCP resources across all connected servers. Resources are server-provided data like files, UI components, or configuration that can be read with read_mcp_resource. |
prompt1 | read | First prompt |
query | write | Execute database query |
read_file | read | Read contents of a file |
read_mcp_resource | read | Read the content of an MCP resource by its URI. Use list_mcp_resources first to discover available resources and their URIs. |
test-prompt | read | A test prompt |
test-repo | read | Test repository |
write_file | write | Write content to a file |
Trust audit
BLOCKgrade F · trust 45/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (9 observation(s))
- Network
- declared (14 observation(s))
- Shell
- declared (10 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (25)
{ pattern: /\bnode\s+--eval\b/i, reason: 'node --eval (code execution from string)' },{ pattern: /\beval\s*\(/, reason: 'eval() call (code execution from string)' },{ pattern: /\bexec\s*\(/, reason: 'exec() (code execution from string)' },{ pattern: /\bnode\s+--eval\b/i, reason: 'node --eval (code execution from string)' },{ pattern: /\beval\s*\(/, reason: 'eval() call (code execution from string)' },ssl: process.env.POSTGRES_SSL === 'true' ? { rejectUnauthorized: false } : falsessl: config.ssl ? { rejectUnauthorized: false } : false,// Check if admin is trying to reset their own password
logger.info({ operation: 'registration_token_validated', tokenType }, `Registration token validated: ${tokenType} satellite token`);key: 'github.oauth.callback_url',
GlobalSettingsService.get('github.oauth.callback_url'),{ pattern: /\bcurl\b/i, reason: 'curl command (network exfiltration risk)' },{ pattern: /\bwget\b/i, reason: 'wget command (network exfiltration risk)' },{ pattern: /\bnc\b/, reason: 'netcat (network exfiltration risk)' },ALTER TABLE "satellites" ALTER COLUMN "satellite_url" SET DEFAULT 'http://127.0.0.1:3001';--> statement-breakpoint
satellite_url: text('satellite_url').notNull().default('http://127.0.0.1:3001'), // Publicly accessible satellite URLif (uri === 'http://127.0.0.1:33418' || uri === 'https://vscode.dev/redirect') {if (uri.startsWith('http://127.0.0.1:') || uri.startsWith('http://localhost:')) {description: 'Satellite URL (e.g., http://127.0.0.1:3001)'
password: 'complex_password_123',
token: 'valid-reset-token-123',
token: 'different-token-format-456',
token: 'valid-verification-token-123',
token: 'different-token-format-456',
service_account_key: '{\n "type": "service_account",\n "project_id": "test-project-123",\n "private_key_id": "test-key-id-123456",\n "private_key": "-----BEGIN PRIVATE KEY-----\\nMIIEvQIBADANBgkqhGates applied: no_behavioural_pass.
23b5e5727cd6full audit observations/trust-audit/mcp-server/deploystackio__deploystack.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 23b5e5727cd6 | BLOCK | F | 45 | first audit |
Questions
What is the DeployStack MCP server?
Open source MCP hosting - deploy MCP servers to HTTP endpoints for n8n, Dify, Voiceflow, and any MCP client.
What tools does DeployStack expose?
14 in total: 10 read-only, 4 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is DeployStack safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (45/100) and found 7 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does DeployStack need?
It reads COOKIE_SECRET, DEPLOYSTACK_ENCRYPTION_SECRET, DEPLOYSTACK_REGISTRATION_TOKEN, JWT_SECRET and POSTGRES_PASSWORD from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does DeployStack run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @deploystack/satellite at 0.22.3.
How current is this page?
The grade is for one exact copy of the source (23b5e5727cd6), read on 2026-10-07. The repository is watched and re-audited when it changes.