Security Audit Tool

Created By
qianniuspacea year ago
A powerful MCP (Model Context Protocol) Server that audits npm package dependencies for security vulnerabilities. Built with remote npm registry integration for real-time security checks.
Overview

What is Mcp Security Audit?

Mcp Security Audit is a powerful tool designed to audit npm package dependencies for security vulnerabilities, integrating with remote npm registries for real-time checks.

How to use Mcp Security Audit?

To use the Mcp Security Audit tool, you can install it via Smithery or clone the repository and configure it manually. Follow the installation instructions provided in the documentation.

Key features of Mcp Security Audit?

  • Real-time security vulnerability scanning
  • Remote npm registry integration
  • Detailed vulnerability reports with severity levels
  • Support for multiple severity levels (critical, high, moderate, low)
  • Compatibility with npm, pnpm, and yarn package managers
  • Automatic fix recommendations
  • CVSS scoring and CVE references

Use cases of Mcp Security Audit?

  1. Scanning npm packages for known vulnerabilities before deployment.
  2. Generating detailed reports for security audits.
  3. Providing recommendations for fixing vulnerabilities in dependencies.

FAQ from Mcp Security Audit?

  • Can Mcp Security Audit scan all npm packages?

Yes! It can audit any npm package dependencies for vulnerabilities.

  • Is Mcp Security Audit free to use?

Yes! The tool is open-source and free to use.

  • How accurate are the vulnerability reports?

The accuracy depends on the npm registry data and the tool's integration with it.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qianniuspace
Star
27
Language
TypeScript
License
MIT license
Category
security

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago