AI AppSec

Name: AI AppSec
Author: subodhkc

by subodhkcversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.subodhkc/ai-appsec

Install

Overview

Description from the maker (original English)

Evidence-backed AppSec for AI applications and agents. Powered by HAIEC.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ai-appsec": {
      "command": "npx",
      "args": [
        "-y",
        "ai-appsec"
      ]
    }
  }
}

Run this in your terminal

claude mcp add ai-appsec -- npx -y ai-appsec

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ai-appsec": {
      "command": "npx",
      "args": [
        "-y",
        "ai-appsec"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ai-appsec": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ai-appsec"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account subodhkc, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32709 servers in this category
Published to the registry more recently than 29% of the other 32709 servers in this category
Basic checks equal to or better than 100% of the other 32709 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AI AppSec safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SwarmMemo

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

SwarmMemo

by Hugo0

Talk with agent swarms: rooms, private messages and paid tasks for AI agents

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AI AppSec

Evidence-backed AppSec for AI applications and agents.

Audit AI code for security risks before you commit, push, merge, or deploy.

What AI AppSec Does

AI AppSec produces deterministic, reproducible static security evidence for AI-agent and AI-application source code. It uses Semgrep 1.173.0 as its execution engine with a bundled Public Core rulepack (122 detectors, 79 security checks).

Key properties:

Static analysis only — does not execute target code
No network required for normal scans (Semgrep setup may require network)
No HAIEC account or API key required
Deterministic evidence — Scan Receipts with SHA-256 digests
Fail-closed digests — rulepack/manifest verified at runtime
Proof-of-fix — rescan comparison with check-evaluation safety

Quick Start

# Install

npm install -g ai-appsec

Check Semgrep status

ai-appsec doctor

Install Semgrep engine (requires network)

ai-appsec setup

Start MCP server (stdio transport)

ai-appsec

Or use via npx without global install:

npx ai-appsec doctor

npx ai-appsec setup

Prerelease channel: @next tracks upcoming prereleases (e.g. ai-appsec@next).

When to Use It

Use scan_ai_security when a developer asks to:

"check this for security issues"
"audit this task before I push"
"review this change for security problems"
"scan this AI agent" or "scan this AI app"
"check my LLM application"
"security review this PR"
"is this safe to merge"
"check this before deployment"
"audit this code for vulnerabilities"
"run a security scan"
"check for security risks before commit"

scan_ai_security

The MCP tool scan_ai_security is the only tool implemented in v0.1.

It scans AI/LLM/agent application source code for security risks including:

Unsafe AI-output execution
Secrets exposure
RAG/model integration risks
Insecure AI API usage
Control gaps
Prompt/input-related risk signals

What scan_ai_security Does NOT Do

Does not provide complete AI system assurance
Does not provide runtime behavioral assurance
Does not provide compliance certification
Does not guarantee zero false positives
Does not prove root causes for concern families
Does not execute target code, install dependencies, or run package managers
Does not perform compliance assessment (compliance requires additional HAIEC evidence)

Findings

Findings are classified by:

Finding kind: PRESENCE, RISK_SIGNAL, CONTROL_GAP, VULNERABILITY
Severity: CRITICAL, HIGH, MEDIUM, LOW, INFO
Disposition: INFORMATIONAL, REVIEW, BLOCK

Security Concern Families

Security Concern Families summarize semantically compatible finding instances for decision-quality presentation. A concern family is a deterministic grouping view — it is NOT necessarily one vulnerability, one material issue, or one root cause. Underlying finding instances remain auditable.

Concern family count is not a vulnerability count. Top 20 / Top 50 are presentation limits, not evidence limits.

COMPLETE / PARTIAL / ERROR

COMPLETE: All supported files in scope were successfully analyzed.
PARTIAL: Some supported files could not be analyzed (e.g., parser failures). PARTIAL scans cannot prove absence of findings. Missing evidence is never interpreted as PASS.
ERROR: The scan could not complete due to an engine error.

Coverage

AI AppSec provides explicit coverage accounting:

DISCOVERED: all files found beneath the target
INTENTIONALLY_EXCLUDED: files excluded by scope policy
UNSUPPORTED: files outside supported extensions (.py, .js, .jsx, .ts, .tsx)
TARGETED: supported files intended for analysis
ENGINE_REPORTED_SCANNED: files Semgrep reports as scanned
PARSE_FAILED: files with parse errors
SUCCESSFULLY_ANALYZED: scanned minus parse failures

Scan Receipt

Every scan produces a tamper-evident Scan Receipt with SHA-256 digests for:

Finding set
Concern family set
Coverage file sets
Evaluated security checks and detectors
Semantic receipt identity

COMPLETE scans produce reproducible receipts across processes and operating systems. PARTIAL scans preserve run-specific coverage differences.

Evidence Envelope

Each scan produces an Evidence Envelope that binds the receipt to the scan execution context, including:

Producer identity
Target identity (scan input digest, git commit, dirty state)
Execution status and completeness
Semantic receipt digest
Envelope digest

Proof-of-fix

Rescan a target after a fix to compare receipts. The proof-of-fix comparison is safe: it verifies that a specific security check's findings were resolved without requiring the entire scan to be identical.

Offline / Local Operation

Normal scanning operates fully offline after prerequisites are installed:

No HAIEC cloud access required
No account or API key required
No rule download during scanning
No telemetry emitted (Semgrep invoked with --metrics off)

Semgrep setup (ai-appsec setup) may require network access to install the engine. Once installed, all scanning is local.

Semgrep Prerequisite

scan_ai_security requires Semgrep 1.173.0 (exact version match).

# Check Semgrep status

ai-appsec doctor

Install managed Semgrep (requires network)

ai-appsec setup

Semgrep is NOT bundled with this package. It is an external engine installed separately. See THIRD_PARTY_NOTICES.md for details.

Limitations

Only scan_ai_security is implemented in v0.1
Static analysis only — no runtime behavioral evidence
No compliance certification or assessment
No tenant isolation checking (roadmap)
No LLM content verification (roadmap)
No deploy security gating (roadmap)

License

MIT License

See LICENSE for the full license text.

Security Reporting

If you believe you have found a security vulnerability:

Do not disclose it publicly before review.
Report via GitHub private vulnerability reporting.
For non-sensitive bugs, use GitHub Issues.

No bug bounty program exists at this time. This project is maintained by a small team. We appreciate responsible disclosure and patience.

Roadmap

Future HAIEC capabilities (not yet implemented in this package):

Tenant isolation checking (scan_tenant_isolation)
LLM/runtime content verification (verify_llm_content)
Deploy security gating (check_deploy_security)
Native deterministic dataflow analysis
Runtime evidence
Inventory evidence
Regulatory evidence
Compliance/assurance integration
Compliance Twin

These will remain independent products/engines. See the HAIEC architecture principle: one workflow, four independent checks.

HAIEC

AI AppSec is powered by HAIEC. HAIEC is the broader assurance platform that may combine ai-appsec evidence with runtime, inventory, regulatory, and external evidence for broader compliance and assurance in the future.

Founder-led development with HAIEC acting as the release gatekeeper for provenance, licensing, and publication.

Related Projects

LLMVerify — LLM content verification (independent product, separate repository)
Tenant Isolation — Cross-tenant boundary checks (independent product, separate repository)

Built by Subodh Kc — a HAIEC (Human AI Evidence Company) product.

AI AppSec

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SwarmMemo

README from the maker

AI AppSec

What AI AppSec Does

Quick Start

Check Semgrep status

Install Semgrep engine (requires network)

Start MCP server (stdio transport)

When to Use It

scan_ai_security

What scan_ai_security Does NOT Do

Findings

Security Concern Families

COMPLETE / PARTIAL / ERROR

Coverage

Scan Receipt

Evidence Envelope

Proof-of-fix

Offline / Local Operation

Semgrep Prerequisite

Install managed Semgrep (requires network)

Limitations

License

Security Reporting

Roadmap

HAIEC

Related Projects