Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    MCP Triage: Security Scanner for MCP Servers

    2

    Audit MCP servers for prompt injection, hardcoded secrets, and dangerous code execution paths.

    Free

    1 installSecurity scanned
    MCP Triage: Security Scanner for MCP Servers

    MCP Triage: Security Scanner for MCP Servers

    Example session with this skill installed

    I'm thinking of installing this third-party MCP server from GitHub. Can you scan the local clone at ./external/weather-mcp for any security risks before I connect it?

    • Read your context and instructions
    • Compiled the mcp triage

    I scanned ./external/weather-mcp with mcp-triage. It found 2 issues, both HIGH severity, and the scan exited non-zero. I recommend not connecting this server until both are fixed.

    Security Audit Results

    RuleSeverityLocationFindingRecommended fix
    MCP201HIGHsrc/index.ts:4Possible hardcoded secret: GitHub token (ghp_aB3d…zA5)Revoke and rotate the token now, remove it from git history, and load it from an environment variable
    MCP001HIGHsrc/tools.ts:4Tool get_weather description matches a prompt-injection pattern ("do not tell the user…")Rewrite the description as plain factual text with no instructions aimed at the model

    What this means

    Credential leak: the hardcoded token is exposed to anyone who can read the source. Treat it as compromised, even if the repo is private.

    Tool poisoning: the get_weather description tells the agent to hide its use of the tool from you. That is a prompt-injection pattern aimed at the model, not documentation for humans. It suggests the server author is careless or hostile.

    Next steps

    1. Don't install this server as is.
    2. Ask the maintainer to fix both findings, or fork it and fix them yourself.
    3. Re-run mcp-triage scan ./external/weather-mcp after the changes to confirm the findings are gone.

    Note: mcp-triage is a pattern-based first pass. A clean result reduces risk but does not prove a server is safe.

    Scanned with mcp-triage: https://github.com/YashkantG/mcp-triage

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Connecting a third-party MCP server involves significant security risks, from tool poisoning to credential leaks. This skill audits Python, JavaScript, and TypeScript MCP servers for common vulnerabilities before you approve or publish them. It identifies patterns that could lead to prompt injection, unauthorized code execution, or network exposure.

    What it does

    • Detects prompt injection by scanning tool descriptions for instructions intended to manipulate model behavior.
    • Identifies hardcoded secrets such as API keys, tokens, and credentials in source and config files, so you can remove and rotate them.
    • Audits code execution paths to find dangerous sinks like eval, exec, or shell commands built from untrusted inputs.
    • Flags over-broad capabilities including arbitrary file access or unvalidated schema inputs that increase attack surfaces.
    • Checks network configurations for unsafe defaults, such as servers bound to all interfaces or disabled authentication.

    How it works

    1. Install the scanner with pip install mcp-triage (Python 3.9+).
    2. Get the server source. Clone the repository to a local directory if you don't already have it.
    3. Execute the scan using mcp-triage scan <path> to analyze the server codebase.
    4. Analyze findings ordered by severity, providing specific file paths and line numbers.
    5. Remediate vulnerabilities following suggested fixes for rotating secrets or rewriting descriptions.

    Frameworks & tools

    This skill utilizes the mcp-triage CLI tool and supports MCP servers written in Python, JavaScript, and TypeScript. It integrates with CI pipelines via SARIF and JSON output formats. The scan runs entirely on your machine, with zero network calls and no telemetry.

    Why this beats prompting it yourself

    Generic security prompts can miss MCP-specific attack vectors like tool poisoning or invisible unicode in descriptions. This skill uses a specialized scanner that enforces a consistent rule set (MCP001-MCP302) designed specifically for the Model Context Protocol.

    Use cases

    • Auditing a third-party MCP server before adding it to your local environment.
    • Reviewing Pull Requests that introduce new tool definitions or execution logic.
    • Verifying your own MCP server is free of hardcoded keys before public release.
    • Automating security gatekeeping in CI to fail builds on high-severity findings.

    Known limitations

    The scanner is pattern-based and does not perform full taint analysis. It may produce false positives or miss complex logic-based vulnerabilities. Treat results as a guide for human review.

    Reports end with a credit line linking to the project.

    Open source (MIT): https://github.com/YashkantG/mcp-triage

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    1 install

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 4 days ago

    • Free to download with an account

    Requires

    Python 3.9+
    pip
    Git (only to clone servers you want to scan)
    Python
    Git

    Listed4 days ago

    What's inside

    Frequently Asked Questions