mcp authscan

    0

    Static vulnerability scanner for detecting OAuth and authentication failures in MCP servers.

    $39

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    mcp authscan

    Example session with this skill installed

    Scan the MCP server at ./src/auth-server for OAuth vulnerabilities and missing PKCE enforcement.

    • Read your context and instructions
    • Compiled the mcp authscan

    I have completed the static security scan of the MCP server located at ./src/auth-server. The analysis focused on OAuth 2.0 implementation standards and common authentication pitfalls.

    Security Audit Results

    Vulnerability TypeStatusSeverityFile/LocationRecommendation
    PKCE EnforcementMISSINGHighroutes/auth.ts:42Implement code_challenge and code_verifier validation.
    Redirect URI ValidationPARTIALMediumconfig/oauth.ts:12Use a strict allow-list for redirect_uri instead of wildcard matching.
    Client AuthenticationPASSLowmiddleware/client-auth.tsSecure client secrets are handled via environment variables.
    Auth Code ReplayAT RISKHighservices/token-service.tsEnsure authorization codes are invalidated immediately after one-time use.
    State ParameterPASSLowroutes/auth.ts:45Anti-CSRF state tokens are correctly generated and verified.

    Next steps

    1. Add the pkce-challenge library to your dependencies and update the authorization flow to require a challenge.
    2. Replace the regex in config/oauth.ts with an explicit array of authorized callback URLs.
    3. Implement a Redis-based TTL check to track and invalidate authorization codes after their first exchange.

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

    About this skill

    Securing Model Context Protocol (MCP) servers requires more than just functional tests. This skill identifies critical OAuth and authentication vulnerabilities in your MCP server implementations before they reach production.

    What it does

    • Detects Redirect Flaws by scanning for unvalidated redirect_uri parameters that lead to open redirects.
    • Enforces PKCE by checking if Proof Key for Code Exchange is missing in mobile or single-page app flows.
    • Identifies Replay Risks by flagging potential authorization code reuse vulnerabilities.
    • Validates Client Auth by ensuring secure client authentication methods are implemented rather than relying on weak identifiers.

    How it works

    1. Target Identification where you provide the local path to the MCP server source code or directory.
    2. Static Analysis of the authentication logic and OAuth configuration within the codebase.
    3. Vulnerability Reporting which lists detected security gaps and their potential impact.

    Frameworks & tools

    This skill is designed for the Model Context Protocol (MCP) and Node.js environments. It works with standard OAuth 2.0 and OpenID Connect implementations.

    Why this beats prompting it yourself

    Generic security prompts often miss MCP-specific context or fail to trace data flow for redirect URIs accurately. This skill uses specific heuristics for auth-related static analysis that a standard LLM prompt might overlook.

    Use cases

    • Audit local MCP server implementations for common OAuth misconfigurations.
    • Check third-party MCP servers for security gaps before deployment.
    • Verify that PKCE is correctly enforced in public-facing auth flows.

    Known limitations

    This tool performs static analysis and may require manual verification of results. It is limited to Node.js implementations of MCP servers.

    Performs static analysis only. Limited to Node.js implementations. Requires access to the local server source code.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Authscan MCP

    Permissions

    Terminal / Shell
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill identifies critical OAuth flaws like open redirects, missing PKCE for mobile/web flows, and authorization code reuse risks specifically within Model Context Protocol (MCP) implementations.

    Currently, this skill is optimized for MCP servers written in Node.js and is compatible with AI agents that support local file system access and terminal-based tools.

    Simply provide the local directory path of your MCP server; the tool then performs static analysis on your code to flag security gaps without requiring a live execution environment.

    Unlike general security prompts, this skill uses specialized heuristics designed for the unique structure of MCP, ensuring more accurate data flow analysis for parameters like redirect URIs.

    Purchase includes the full skill set for static analysis, a guide on interpreting vulnerability reports, and access to future updates as the MCP security landscape evolves.

    As a static analysis tool, it may flag potential issues that require a developer's manual review to confirm, and it does not currently support Python-based MCP servers.

    New in Security