Stripecheckup

app.vercel.stripecheckupPublished by stripecheckup.vercel.appOfficial publisherv1.0.0Updated Oct 25, 2026

Scan pasted Stripe webhook/checkout code for common integration bugs.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that scans pasted Stripe webhook and checkout code for common integration bugs and returns pattern-based findings.

What you can do
Analyze pasted Stripe integration source code, such as a webhook handler, a checkout-session-creation route, or both concatenated together, and return pattern-based findings for common integration bugs. Findings cover issues such as missing webhook signature verification and missing customer.subscription.updated handling.
When to use it
Useful when reviewing or debugging a Stripe integration and you want a quick pattern-based check of webhook and checkout code before shipping or troubleshooting missed events.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared.
Before you install
You paste your Stripe integration source code into the service, so it leaves your machine and is sent to a third party; review the code for secrets or sensitive values before pasting. Findings are pattern-based and may be incomplete or produce false positives.

Installation

In SourceWeft

  1. Open Stripecheckup in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.vercel.stripecheckup%2Fstripecheckup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stripecheckup": {
      "type": "http",
      "url": "https://stripecheckup.vercel.app/api/mcp"
    }
  }
}

Tools

1

check_stripe_code

Paste Stripe integration source code (a webhook handler, a checkout-session-creation route, or both concatenated) and get back pattern-based findings for the most common integration bugs: missing webhook signature verification, missing customer.subscription.updated handling (the single most common bug -- dunning marks a subscription past_due/unpaid, not canceled, so a handler that only reacts to .deleted leaves non-paying customers with access forever), missing checkout metadata/client_reference_id, and premature customer creation. This is regex pattern matching over text, not a real parser -- treat a clean result as 'didn't find a problem', not a guarantee. Nothing pasted is stored.

Parameterscoderequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.