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.
Available components
Last scanned (14 hours ago)
Scores higher than 49% of npm servers
Category Security
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 60 of 155 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 97 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 420 tokens (~84/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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 →
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- CVE-2026-118764 affects this package: high ▼ security
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
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 5 Nov 2026 · Analysed npm/@assurly/mcp-server@1.2.2
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 →
Vulnerabilities 9 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 155 packages
| Packages resolved | 155 |
|---|---|
| Stale | 60 |
| 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 →
assurly_explain_rule Explain an Assurly rule ~51
Return a human-readable explanation and remediation steps for an Assurly Ship Gate rule id (e.g. supabase-rls).
| Name | Type | Req | Description |
|---|---|---|---|
| ruleId | string | yes | Assurly rule identifier |
No output schema declared.
No examples provided.
assurly_scan_agent Scan the agent stack ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the project root to scan |
No output schema declared.
No examples provided.
assurly_scan_files Scan provided files ~44
Run the Assurly Ship Gate scan on in-memory file contents (for agents that already have project files in context).
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to analyze |
No output schema declared.
No examples provided.
assurly_scan_path Scan project directory ~52
Run the full Assurly Ship Gate scan on a local project directory (same rules as `assurly scan`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the project root to scan |
No output schema declared.
No examples provided.
assurly_verdict Get the hosted Assurly ship verdict ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
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.
npm · @assurly/mcp-server
claude mcp add dev-assurly-mcp-server -- npx -y @assurly/mcp-server
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.