Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ashlr Stack

NPM · ASHLR-STACK-MCP

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

Available components

+4 this week 88 Trust /100

Last scanned (16 hours ago)

Scores higher than 82% of npm servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
  • 32 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ashlrai/ashlr-stack). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1406 tokens (~74/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
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; "stack_remove" implies "remove" 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 19 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 10 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −4
    • Provenance: pass → unverified ▼ security
Diagnostics

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 21 Nov 2026 · Analysed npm/ashlr-stack-mcp@0.3.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ashlrai/ashlr-stack
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ashlrai/ashlr-stack/.github/workflows/release.yml@refs/tags/v0.3.1
Rekor log index 3620260261
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4e2663714fa03aff895eaeffdc91aeef66ba74ffab462c5909a1a49d8820c500e213670cc8baa3e79c5460e2beb4e42825305eea278f75d71dbdb179a

Background: How many MCP packages publish verified provenance →

Dependencies 101 packages
Packages resolved 101
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~1,406 tokens

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 →

Tool Tokens
stack_add ~88

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.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
servicestringyesService name (e.g. supabase, neon, vercel).
usestring–Existing resource id to attach to.

No output schema declared.

No examples provided.

stack_apply ~129

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.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
no_wireboolean–Skip the Phantom vault check and webhook stubs.
recipe_idstringyesRecipe id (filename stem in .stack/recipes/, letters, numbers, underscores or hyphens).

No output schema declared.

No examples provided.

stack_deps ~52

Show the service dependency graph for the current stack.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
jsonboolean–JSON: ashlr.stack.deps/v1.

No output schema declared.

No examples provided.

stack_doctor ~88

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.

NameTypeReqDescription
allboolean–Run across every registered project.
cwdstring–Existing absolute project directory; defaults to server cwd.
fixboolean–Attempt auto-remediation.
jsonboolean–JSON output.

No output schema declared.

No examples provided.

stack_env_diff ~65

Report which declared secrets are missing from the Phantom vault.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
jsonboolean–JSON: ashlr.stack.env-diff/v1; names and service only. Missing secrets remain an error.

No output schema declared.

No examples provided.

stack_env_show ~57

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

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
jsonboolean–JSON: ashlr.stack.env/v1; names only.

No output schema declared.

No examples provided.

stack_import ~104

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).

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
dryRunboolean–Preview without writing.
fromstring–Path to the .env file inside the project (default: .env).

No output schema declared.

No examples provided.

stack_info ~71

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

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
jsonboolean–JSON: ashlr.stack.info/v1.
servicestringyes–

No output schema declared.

No examples provided.

stack_init ~68

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

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
forceboolean–Overwrite an existing .stack.toml.
templatestring–Starter template name.

No output schema declared.

No examples provided.

stack_list ~47

List services configured in this stack.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
jsonboolean–JSON: ashlr.stack.list/v1.

No output schema declared.

No examples provided.

stack_projects_list ~43

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

NameTypeReqDescription
jsonboolean–JSON: ashlr.stack.projects/v1.

No output schema declared.

No examples provided.

stack_providers ~66

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

NameTypeReqDescription
categorystring–Only this category, any case (e.g. ai, database, payments).
jsonboolean–JSON: ashlr.stack.providers/v1.

No output schema declared.

No examples provided.

stack_recommend ~150

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

NameTypeReqDescription
categorystring–Category (case-insensitive): Database, Deploy, Cloud, AI, Analytics, Observability, Errors, Payments, Code, Tickets, Email, Auth, FeatureFlags. Unknown values error.
cwdstring–Existing absolute project directory; defaults to server cwd.
knumber–Max top-level hits to return (default 6).
querystringyesNatural-language description of the project / stack need.
saveboolean–Save .stack/recipes/<id>.toml for stack_apply; returns recipe id.

No output schema declared.

No examples provided.

stack_remove ~104

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.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
keepRemoteboolean––
servicestringyes–

No output schema declared.

No examples provided.

stack_scan ~77

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

NameTypeReqDescription
confidencestring–Minimum confidence: low, medium, or high (default: medium).
cwdstring–Existing absolute project directory; defaults to server cwd.
pathstring–Directory to scan inside the project (default: cwd).

No output schema declared.

No examples provided.

stack_status ~50

Show Phantom + services + config at a glance.

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
jsonboolean–JSON: ashlr.stack.status/v1.

No output schema declared.

No examples provided.

stack_sync ~60

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

NameTypeReqDescription
cwdstring–Existing absolute project directory; defaults to server cwd.
platformstringyesOne of: vercel, railway, fly.

No output schema declared.

No examples provided.

stack_templates_list ~44

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

NameTypeReqDescription
jsonboolean–JSON: ashlr.stack.templates/v1; services, providers and secret names.

No output schema declared.

No examples provided.

stack_upgrade ~43

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

npm · ashlr-stack-mcp

# add to Claude Code
claude mcp add ashlrai-ashlr-stack -- npx -y ashlr-stack-mcp
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.