stripecheckup
Scan pasted Stripe webhook/checkout code for common integration bugs.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"stripecheckup": {
"url": "https://stripecheckup.vercel.app/api/mcp"
}
}
}Remote endpoints
https://stripecheckup.vercel.app/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢check_stripe_code(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.
Input Schema
{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Stripe webhook handler and/or checkout-session-creation source code"
}
},
"required": [
"code"
]
}Community
Evidence