# dev.assurly/mcp-server (npm · @assurly/mcp-server)

Pre-deploy ship gate AI agents call before shipping. Also audits the agent's own MCP config.

- Trust score: 74/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@assurly/mcp-server`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server.md), [page](https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@assurly/mcp-server`
- Version: `1.2.2`
- 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-05.

- **Supply Chain Security**: 80/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 60 of 155 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 97 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 420 tokens (~84/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 dev.assurly/mcp-server server?

dev.assurly/mcp-server runs locally as an npm package, launched with npx -y @assurly/mcp-server. 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 dev-assurly-mcp-server -- npx -y @assurly/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "dev-assurly-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@assurly/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-assurly-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@assurly/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-assurly-mcp-server -- npx -y @assurly/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-assurly-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@assurly/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-assurly-mcp-server --command npx --arg -y --arg @assurly/mcp-server
```

### Hermes

```yaml
mcp_servers:
  dev-assurly-mcp-server:
    command: "npx"
    args: ["-y", "@assurly/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-assurly-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@assurly/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-assurly-mcp-server -t stdio -c npx -a -y @assurly/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "dev-assurly-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@assurly/mcp-server"
      ]
    }
  }
}
```

## 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-03 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 73, −1)

- [functional] Stability: pass → 0.93

### 2026-10-31 (score 74, 0)

- [security regression] CVE-2026-118764 affects this package: high

### 2026-10-29 (score 74, 0)

- [security regression] CVE-2026-118663 affects this package: high

### 2026-10-28 (score 74, 0)

- [security regression] GHSA-f897-62hf-6gxq affects this package: high

### 2026-10-26 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-10-25 (score 73, −1)

- [functional] Stability: pass → 0.97

### 2026-10-24 (score 74, 0)

- [security regression] CVE-2023-54404 affects this package: high

## MCP tools (5)

### `assurly_scan_path` (~52 tokens)

Scan project directory

Run the full Assurly Ship Gate scan on a local project directory (same rules as `assurly scan`).

Input parameters:

- `path` (string, required): Absolute or relative path to the project root to scan

### `assurly_scan_files` (~44 tokens)

Scan provided files

Run the Assurly Ship Gate scan on in-memory file contents (for agents that already have project files in context).

Input parameters:

- `files` (array, required): Files to analyze

### `assurly_explain_rule` (~51 tokens)

Explain an Assurly rule

Return a human-readable explanation and remediation steps for an Assurly Ship Gate rule id (e.g. supabase-rls).

Input parameters:

- `ruleId` (string, required): Assurly rule identifier

### `assurly_verdict` (~157 tokens)

Get the hosted Assurly ship verdict

Pre-deploy ship gate: read the hosted Assurly verdict (Ready/Review/Blocked + ship score + top issue + one-line fix + per-rule fix outcomes with observation times) for a deployed URL or a repo. Fix outcomes reflect the last re-probe only — after claiming a fix, deploy and re-probe before treating it as done. Reads the hosted Assurly API — it does not scan locally and never triggers an active probe. Requires ASSURLY_API_KEY in the environment.

Input parameters:

- `repo` (string): Repository in owner/name form to look up (exactly one of url/repo)
- `url` (string): Deployed app URL to look up (exactly one of url/repo)

### `assurly_scan_agent` (~86 tokens)

Scan the agent stack

Advisory audit of the AI agent setup only — MCP client configs (.cursor/mcp.json, etc.) and instruction files (README, CLAUDE.md, AGENTS.md, .cursorrules). Does not scan application source. Never blocks ship; isError stays false under all outcomes.

Input parameters:

- `path` (string, required): Absolute or relative path to the project root to scan

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 74
- 2026-10-11: 73
- 2026-10-09: 72
- 2026-10-04: 79
- 2026-10-03: 78
- 2026-10-02: 78

## Common questions

### What is the dev.assurly/mcp-server server?

dev.assurly/mcp-server is listed in the public MCP registry as dev.assurly/mcp-server. Pre-deploy ship gate AI agents call before shipping. Also audits the agent's own MCP config. This page covers its npm package (@assurly/mcp-server).

### Is the dev.assurly/mcp-server server safe to use?

dev.assurly/mcp-server scores 74 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 5 November 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 dev.assurly/mcp-server server expose?

dev.assurly/mcp-server exposes 5 tools: assurly_scan_path, assurly_scan_files, assurly_explain_rule, assurly_verdict, assurly_scan_agent. Their descriptions and schemas cost roughly 390 tokens of context every time the server is loaded.

### Is the dev.assurly/mcp-server server still maintained?

dev.assurly/mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 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 dev.assurly/mcp-server server under?

dev.assurly/mcp-server 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 dev.assurly/mcp-server server?

VerifyMCP ran 16 checks on dev.assurly/mcp-server, 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/@assurly/mcp-server
- Socket report: https://socket.dev/npm/package/@assurly/mcp-server
- Website: https://assurly.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/dev-assurly-mcp-server/assurly-mcp-server