Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    mcp oauth runtime test harness

    1

    Run bounded OAuth authorization and token-rejection tests for MCP resource servers to generate runtime evidence.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    mcp oauth runtime test harness

    mcp oauth runtime test harness

    Example session with this skill installed

    Run the OAuth test suite against our staging MCP resource server at https://staging.api.mcp-dev.local/tools using the provided synthetic fixtures in examples/input.json.

    • Read your context and instructions
    • Compiled the mcp oauth runtime

    I have completed the runtime authorization test suite against the staging MCP resource server. The suite executed 1 positive control and 5 negative rejection cases using the scripts/probe.py harness.

    MCP Authorization Evidence Report

    Test Case IDRequirementInput ProvenanceExpected ResultActual ResultStatus
    TC-001Valid Token AccessFixture: valid_scoped_jwt200 OK200 OKPASS
    TC-002Expired Token RejectionFixture: expired_jwt_2024401 Unauthorized401 UnauthorizedPASS
    TC-003Insufficient ScopeFixture: read_only_jwt403 Forbidden403 ForbiddenPASS
    TC-004Mismatched AudienceFixture: cross_env_jwt401/403200 OKFAIL
    TC-005Missing Auth HeaderFixture: null_header401 Unauthorized401 UnauthorizedPASS
    TC-006Cross-Tenant AttemptFixture: tenant_b_jwt403 Forbidden403 ForbiddenPASS

    Observation Summary

    Critical Failure in TC-004: The server accepted a token intended for a different audience (audience claim mismatch). This indicates the JWT validation logic is not strictly checking the aud field.

    • Positive Control: TC-001 confirmed the endpoint is functional and reachable under normal conditions.
    • Credential Safety: All Authorization header values were scrubbed from the probe.py output.

    Next steps

    1. Update the JWT validation middleware on the resource server to enforce strict aud (audience) verification.
    2. Re-run the harness using a new synthetic token for TC-004 to confirm the fix.
    3. Review the server logs for TC-004 to see why the validation provider did not trigger a rejection.

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

    About this skill

    The problem

    Manual testing of OAuth implementations in Model Context Protocol (MCP) servers is error-prone and often lacks negative control evidence. Developers frequently struggle to prove that resource servers correctly reject malformed, expired, or scoped-out tokens without accidentally exposing credentials in logs.

    What it does

    • Executes a suite of bounded HTTP tests against staging MCP resource servers using provided test fixtures.
    • Runs mandatory positive controls alongside negative test cases including expired, wrong-audience, and insufficient-scope tokens.
    • Generates repeatable authorization evidence using specialized probing scripts while strictly masking sensitive header values.
    • Identifies discrepancies between expected rejection codes and actual server responses to verify authorization logic.

    Frameworks & tools

    Model Context Protocol (MCP), Python (probe scripts), JWT, and OAuth 2.0 staging environments.

    Why this beats prompting it yourself

    A standard LLM lacks the discipline to enforce strict negative controls and will often hallucinate authorization success. This skill follows a rigid evidence protocol that prevents "false pass" results and ensures no credentials leak into your persistent reports or logs.

    Use cases

    • Verify an MCP server correctly enforces scopes for specific tool executions.
    • Generate runtime authorization evidence for internal security audits.
    • Test cross-tenant isolation by attempting resource access with valid but mismatched tokens.

    Known limitations

    Requires pre-supplied test tokens with verified provenance; it cannot bypass JWT signatures or automate initial OAuth login flows. Only targets staging environments.

    Does not perform OAuth login flows or JWT signing. Requires pre-verified test tokens and restricted staging environments. Focuses on runtime rejection, not static code analysis.

    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

    Python

    Permissions

    Environment Variables
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This harness automates the execution of both positive and negative authorization tests, generating verifiable evidence that your MCP server correctly rejects unauthorized requests without leaking sensitive credentials into logs.

    The skill is designed for any MCP-compatible environment and requires a Python runtime to execute the specialized probing scripts against your staging resource servers.

    No, for security and integrity, the skill requires you to provide pre-generated test tokens; it focuses on testing the server's enforcement logic rather than automating the initial login flow.

    Each purchase includes the core testing scripts, a suite of standardized test fixtures for negative controls (expired/wrong-scope), and documentation on interpreting the generated evidence reports.

    The harness targets standard OAuth 2.0 implementations used in MCP resource servers, focusing on JWT validation and scope enforcement, making it compatible with most modern identity providers in a staging context.

    This skill is strictly intended for staging or development environments to safely generate audit evidence without risking production data or stability.

    New in LLM Ops