security MCP Server
MCP server for AI agent governance - quantum-safe audit trails, policy enforcement, threat detection. Works with Claude Desktop, Cursor, Claude Code.
Discovered via unknown and last synced 2mo ago.
Install instructions not detected yet
Check the source repository for the latest setup steps.
Create a signed, replayable audit record for an agent action
Create or update a local enforcement policy for a tool (risk level, rate limits, approval, blocking, tool endpoint)
Setup
Scan every registered tool policy for threats
Verify a created signature
List all active tool enforcement policies
List all registered AI agents
Get details for a specific agent
Scan an MCP tool definition for security threats before trusting it
Check if an action is allowed by your organization's policies
Report the outcome of a gate-approved action. Signs the result, hashes the output, and binds it to the original approval. Returns a bilateral receipt with an `output_hash` that can be verified later via `verify_output`.
Combined agent status and policy check in a single call. Returns CLEARED or NOT CLEARED with reasons.
Strong enforcement proxy. Checks policy, rate limits, and approval requirements. If a `tool_endpoint` is configured, forwards the call and signs request + response together as a bilateral receipt.
What it does
Verify a signed output matches expected content by comparing the stored output_hash against a fresh hash
Remove a tool enforcement policy
What it does
Pre-execution enforcement gate. Checks policy, signs the approval or denial, returns verdict. Call `complete_action` after the action to close the bilateral receipt.
above)\\b'", "prompt injection pattern in description: '\\byou\\s+(must
shall)\\b'", "suspicious schema field: 'command'", "possible typosquat of 'bash'" ] } ``` ## Setup ### Install ```bash pip install asqav-mcp ``` Set your API key (get one free at [asqav.com](https://asqav.com)): ```bash export ASQAV_API_KEY="sk_live_..." ``` ### Claude Desktop Add to your `claude_desktop_config.json`: ```json { "mcpServers": { "asqav": { "command": "asqav-mcp", "env": { "ASQAV_API_KEY": "sk_live_..." } } } } ``` ### Claude Code ```bash claude mcp add asqav -- asqav-mcp ``` ### Governed Claude Code session For project-local Claude Code setup, create a `.mcp.json` file in the repository root. Keep the API key in your environment instead of committing it: ```json { "mcpServers": { "asqav": { "command": "asqav-mcp", "env": { "ASQAV_API_KEY": "${ASQAV_API_KEY}" } } } } ``` Then start Claude Code from the same repository: ```bash export ASQAV_API_KEY="***" claude ``` A bounded governance flow for a high-risk tool call looks like this: ```text User: Before changing production config, use asqav to gate and audit the action. Claude Code -> asqav.gate_action( action_type="config_update", agent_id="claude-code", risk_context="Update production config timeout" ) asqav -> APPROVED, gate_id="gate_123", approval_signature_id="sig_approval_123" Claude Code -> edits config and runs the requested verifier Claude Code -> asqav.complete_action( gate_id="gate_123", result="Updated timeout and verifier passed" ) asqav -> receipt_signature_id="sig_receipt_456", output_hash="sha256:..." ``` To verify the audit trail after the session, ask Claude Code to call the verification tools with the signature IDs returned during the run: ```text Claude Code -> asqav.verify_signature(signature_id="sig_approval_123") Claude Code -> asqav.verify_signature(signature_id="sig_receipt_456") Claude Code -> asqav.verify_output( signature_id="sig_receipt_456", expected_output="Updated timeout and verifier passed" ) ``` The approval signature proves the action was gated before execution. The receipt signature and `verify_output` result prove the reported outcome was signed and has not been modified. ### Cursor Add to your Cursor MCP settings: ```json { "mcpServers": { "asqav": { "command": "asqav-mcp", "env": { "ASQAV_API_KEY": "sk_live_..." } } } } ``` ### Docker ```bash docker build -t asqav-mcp . docker run -e ASQAV_API_KEY="sk_live_..." asqav-mcp ``` ## Why
真实性验证技能。分析用户提供的信息、消息、图片或内容，判断其真实性和可信度，识别虚假信息、AI生成内容或伪造内容。
Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators
Pod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PS
Implements eBPF-based security monitoring using Cilium Tetragon for real-time process execution tracking, network connection observability, file access auditing, and runtime enforcement. Covers TracingPolicy CRD authoring with kprobe/tracepoint hooks, in-kernel filtering via matchArgs/matchBinaries selectors, JSON event export, and integration with SIEM pipelines. Use when building kernel-level runtime security observability for Linux hosts or Kubernetes clusters.
AI Agent Governance Toolkit — Policy enforcement, zero-trust identity, execution sandboxing, and reliability engineering for autonomous AI agents. Covers 10/10 OWASP Agentic Top 10.
Open-source sandboxed agent harness for teams. Giving every employee a secured personal agent.
AI agent security scanner. Detect vulnerabilities in agent configurations, MCP servers, and tool permissions. Available as CLI, GitHub Action, ECC plugin, and GitHub App integration. 🛡️
A secure* runtime for autonomous AI agents. Policy from plain-English constitutions. (*https://ironcurtain.dev)
Learn how to use the absolute-audit Claude skill. Complete guide with installation instructions and examples.
Learn how to use the token-scam-analysis Claude skill. Complete guide with installation instructions and examples.
Learn how to use the absolute-upgrade Claude skill. Complete guide with installation instructions and examples.