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.

AppSec Toolbox MCP

OCI · GHCR.IO/AI-RONIN-SYSTEMS/APPSEC-TOOLBOX-MCP

Passive AppSec scanners as eight parameterless MCP tools; the audited repository is data.

+3 this week 49 Trust /100

Last scanned (21 hours ago)

Scores higher than 74% of OCI servers

Category Security

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ai-ronin-systems/appsec-toolbox-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability49
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 231 tokens (~28/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 25 Oct 26 45

    First indexed and scored.

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 4 Nov 2026 · Analysed oci/ghcr.io/ai-ronin-systems/appsec-toolbox-mcp@0.3.0

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 oci
Reason Verified
Discovered via OCI referrers API
Source repo ai-ronin-systems/appsec-toolbox-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ai-ronin-systems/appsec-toolbox-mcp/.github/workflows/release.yml@refs/tags/v0.3.0
Rekor log index 3461800764
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:494453e25721c45972dd14695b1e600ce5ab1fbd4d6b9d09d6a1bef2836734fc

Background: How many MCP packages publish verified provenance →

MCP tools · 8 exposed · ~231 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
make_appsec-full ~26

Run the complete passive AppSec evidence bundle

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_security-checkov ~28

Scan IaC and CI/CD configuration with Checkov

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_security-gitleaks ~30

Scan the mounted working tree for secrets with Gitleaks

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_security-language ~25

Run applicable language-specific passive SAST profiles

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_security-osv ~29

Scan dependency metadata with OSV-Scanner without dependency resolution

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_security-semgrep ~31

Run Semgrep SAST and inventory suppression markers in the mounted target

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_security-trivy ~32

Scan vulnerabilities, misconfigurations, secrets, and licenses with Trivy

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

make_supply-chain-sbom ~30

Generate a CycloneDX JSON SBOM with Syft

NameTypeReqDescription
previewboolean––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the AppSec Toolbox MCP server?

AppSec Toolbox MCP runs locally as a container image, launched with docker run --rm -i -e APPSEC_LANGS ghcr.io/ai-ronin-systems/appsec-toolbox-mcp:0.3.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/ai-ronin-systems/appsec-toolbox-mcp

# add to Claude Code
claude mcp add ai-ronin-systems-appsec-toolbox-mcp -- docker run --rm -i -e APPSEC_LANGS ghcr.io/ai-ronin-systems/appsec-toolbox-mcp:0.3.0

This image reads APPSEC_LANGS. Set it in your client's env block for this server; docker run -e passes it through to the container.

Common questions

What is the AppSec Toolbox MCP server?

AppSec Toolbox MCP is listed in the public MCP registry as io.github.ai-ronin-systems/appsec-toolbox-mcp. Passive AppSec scanners as eight parameterless MCP tools; the audited repository is data. This page covers its container image (ghcr.io/ai-ronin-systems/appsec-toolbox-mcp).

Is the AppSec Toolbox MCP server safe to use?

AppSec Toolbox MCP scores 49 out of 100 on VerifyMCP. 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 AppSec Toolbox MCP server expose?

AppSec Toolbox MCP exposes 8 tools: make_appsec-full, make_security-checkov, make_security-gitleaks, make_security-language, make_security-osv, and 3 more. Their descriptions and schemas cost roughly 231 tokens of context every time the server is loaded.

Is the AppSec Toolbox MCP server still maintained?

AppSec Toolbox MCP is still listed as active in the MCP registry. We last reached this channel on 4 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 AppSec Toolbox MCP server under?

AppSec Toolbox MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.