# Ashlr Stack (npm · ashlr-stack-mcp)

Provision and connect third-party dev services (Supabase, Vercel, and more) from your coding agent.

- Trust score: 88/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `ashlr-stack-mcp`: 88/100 (this document), [markdown](https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp.md), [page](https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp)

## Channel facts

- Registry: `npm`
- Package: `ashlr-stack-mcp`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 101 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ashlrai/ashlr-stack).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1406 tokens (~74/item across 19 items; 19 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "stack_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Ashlr Stack MCP server?

Ashlr Stack runs locally as an npm package, launched with npx -y ashlr-stack-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ashlrai-ashlr-stack -- npx -y ashlr-stack-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ashlrai-ashlr-stack": {
      "command": "npx",
      "args": [
        "-y",
        "ashlr-stack-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ashlrai-ashlr-stack": {
      "command": "npx",
      "args": [
        "-y",
        "ashlr-stack-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ashlrai-ashlr-stack -- npx -y ashlr-stack-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ashlrai-ashlr-stack": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ashlr-stack-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ashlrai-ashlr-stack --command npx --arg -y --arg ashlr-stack-mcp
```

### Hermes

```yaml
mcp_servers:
  ashlrai-ashlr-stack:
    command: "npx"
    args: ["-y", "ashlr-stack-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ashlrai-ashlr-stack": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "ashlr-stack-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ashlrai-ashlr-stack -t stdio -c npx -a -y ashlr-stack-mcp
```

### Other

```json
{
  "mcpServers": {
    "ashlrai-ashlr-stack": {
      "command": "npx",
      "args": [
        "-y",
        "ashlr-stack-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 82, +5)

- [security improvement] Source repository: unverified → pass

### 2026-11-09 (score 77, −4)

- [security regression] Provenance: pass → unverified

## MCP tools (19)

### `stack_init` (~68 tokens)

Scaffold .stack.toml in the current directory; a selected template may also run provider setup.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `force` (boolean): Overwrite an existing .stack.toml.
- `template` (string): Starter template name.

### `stack_import` (~104 tokens)

Import nonempty new variables from an .env file into Phantom and record detected services; existing vault names are left unchanged. Returns ashlr.stack.import/v1 JSON naming what was stored, skipped and wired (names only, never values).

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `dryRun` (boolean): Preview without writing.
- `from` (string): Path to the .env file inside the project (default: .env).

### `stack_scan` (~77 tokens)

Detect providers this repo uses by reading package.json / requirements.txt / config files.

Input parameters:

- `confidence` (string): Minimum confidence: low, medium, or high (default: medium).
- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `path` (string): Directory to scan inside the project (default: cwd).

### `stack_add` (~88 tokens)

Run provider-specific service setup or attach an existing resource, then record returned secret slots and optional MCP configuration. Credentials and client/provider acceptance must be checked separately.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `service` (string, required): Service name (e.g. supabase, neon, vercel).
- `use` (string): Existing resource id to attach to.

### `stack_remove` (~104 tokens)

Remove local service configuration and its MCP entry, and attempt Phantom secret cleanup. Returns JSON (ashlr.stack.remove/v1); `secrets_kept` lists names Phantom left stored, which headless runs always do, for the user to remove with `phantom remove` in a terminal. Upstream resources are kept.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `keepRemote` (boolean)
- `service` (string, required)

### `stack_list` (~47 tokens)

List services configured in this stack.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `json` (boolean): JSON: ashlr.stack.list/v1.

### `stack_info` (~71 tokens)

Inspect configured resource, auth kind, secret-name inventory and MCP metadata; attempt a healthcheck when the provider supports one.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `json` (boolean): JSON: ashlr.stack.info/v1.
- `service` (string, required)

### `stack_status` (~50 tokens)

Show Phantom + services + config at a glance.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `json` (boolean): JSON: ashlr.stack.status/v1.

### `stack_env_show` (~57 tokens)

Show which declared secrets are present in the Phantom vault (masked).

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `json` (boolean): JSON: ashlr.stack.env/v1; names only.

### `stack_env_diff` (~65 tokens)

Report which declared secrets are missing from the Phantom vault.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `json` (boolean): JSON: ashlr.stack.env-diff/v1; names and service only. Missing secrets remain an error.

### `stack_doctor` (~88 tokens)

Inspect the configured-service health report. --fix attempts supported remediation; stored vault names can cause repairs to be skipped, and name presence is not credential validity.

Input parameters:

- `all` (boolean): Run across every registered project.
- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `fix` (boolean): Attempt auto-remediation.
- `json` (boolean): JSON output.

### `stack_sync` (~60 tokens)

Forward a deployment-platform sync request to phantom sync; inspect the installed Phantom command support and result separately.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `platform` (string, required): One of: vercel, railway, fly.

### `stack_providers` (~66 tokens)

List the curated source provider catalog by category; inclusion does not attest complete provisioning or active credentials.

Input parameters:

- `category` (string): Only this category, any case (e.g. ai, database, payments).
- `json` (boolean): JSON: ashlr.stack.providers/v1.

### `stack_projects_list` (~43 tokens)

List projects recorded in the local Stack registry; this is not a filesystem-wide discovery scan.

Input parameters:

- `json` (boolean): JSON: ashlr.stack.projects/v1.

### `stack_deps` (~52 tokens)

Show the service dependency graph for the current stack.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `json` (boolean): JSON: ashlr.stack.deps/v1.

### `stack_templates_list` (~44 tokens)

List available starter stack templates and the services each one adds.

Input parameters:

- `json` (boolean): JSON: ashlr.stack.templates/v1; services, providers and secret names.

### `stack_upgrade` (~43 tokens)

Check npm for a newer @ashlr/stack release. Returns ashlr.stack.upgrade/v1 JSON (current, latest, status, install command); installs nothing.

### `stack_recommend` (~150 tokens)

Rank curated providers by query, returning JSON as text without LLM inference. save:true writes a Recipe for stack_apply.

Input parameters:

- `category` (string): Category (case-insensitive): Database, Deploy, Cloud, AI, Analytics, Observability, Errors, Payments, Code, Tickets, Email, Auth, FeatureFlags. Unknown values error.
- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `k` (number): Max top-level hits to return (default 6).
- `query` (string, required): Natural-language description of the project / stack need.
- `save` (boolean): Save .stack/recipes/<id>.toml for stack_apply; returns recipe id.

### `stack_apply` (~129 tokens)

Apply a saved Recipe through provider setup, then report which declared secrets are in the Phantom vault and which are missing (names only; it never writes to the vault) and write webhook stubs. Inspect failures and skips. no_wire:true skips the vault check and stubs, not provider credential writes.

Input parameters:

- `cwd` (string): Existing absolute project directory; defaults to server cwd.
- `no_wire` (boolean): Skip the Phantom vault check and webhook stubs.
- `recipe_id` (string, required): Recipe id (filename stem in .stack/recipes/, letters, numbers, underscores or hyphens).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp#diagnostics

## Score history

- 2026-11-21: 88
- 2026-11-20: 87
- 2026-11-19: 87
- 2026-11-18: 86
- 2026-11-17: 86
- 2026-11-16: 85
- 2026-11-15: 85
- 2026-11-14: 84
- 2026-11-13: 84
- 2026-11-12: 83
- 2026-11-11: 83
- 2026-11-10: 82
- 2026-11-09: 77
- 2026-11-08: 81
- 2026-11-07: 81
- 2026-11-06: 81
- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 68

## Common questions

### What is the Ashlr Stack MCP server?

Ashlr Stack is an MCP server listed in the public MCP registry as io.github.ashlrai/ashlr-stack. Provision and connect third-party dev services (Supabase, Vercel, and more) from your coding agent. This page covers its npm package (ashlr-stack-mcp).

### Is the Ashlr Stack MCP server safe to use?

Ashlr Stack scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Ashlr Stack MCP server expose?

Ashlr Stack exposes 19 tools: stack_init, stack_import, stack_scan, stack_add, stack_remove, and 14 more. Their descriptions and schemas cost roughly 1,406 tokens of context every time the server is loaded.

### Is the Ashlr Stack MCP server still maintained?

Ashlr Stack 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 licence is the Ashlr Stack MCP server under?

Ashlr Stack declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Ashlr Stack MCP server?

VerifyMCP ran 16 checks on Ashlr Stack, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/ashlr-stack-mcp
- Socket report: https://socket.dev/npm/package/ashlr-stack-mcp
- Repository: https://github.com/ashlrai/ashlr-stack
- Website: https://stack.ashlr.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ashlrai-ashlr-stack/ashlr-stack-mcp
