stripecheckup
Server Details
Scan pasted Stripe webhook/checkout code for common integration bugs.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
With only one tool, there is no possibility of overlap or confusion between tools. An agent will always know which tool to call for this purpose.
The single tool follows a clear verb_noun convention (check_stripe_code). Consistency is trivially perfect since there is only one name to evaluate.
One tool is thin for most servers, but here the scope is intentionally narrow (a single regex-based linter), so it is borderline rather than clearly wrong. The tool earns its place, but the server could plausibly offer a few more focused checks.
The tool explicitly covers several high-value Stripe integration bugs (webhook signature verification, subscription.updated handling, checkout metadata, premature customer creation). It is not a full Stripe audit surface, but for its stated pattern-matching purpose the coverage is solid, with only minor gaps like idempotency or other edge-case checks.
Available Tools
1 toolcheck_stripe_codeAInspect
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.
Inputs: code (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Checks HTTP response headers you paste: 7 security checks with copy-paste fixes. No fetching.
Scan a public GitHub repo for known Vercel Python-runtime deploy footguns.
Code security scanner for founders and small teams: leaked secrets, missing RLS, injection, CVEs
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceStatic analysis for vibe-coded apps. Flags security, reliability, performance, and AI quality issues in code generated by Cursor, v0, Bolt, and Copilot.858 npm15MIT
- AlicenseAqualityBmaintenanceScans your workspace for hard-coded secrets, insecure code patterns mapped to CWE and taint flows in 14 languages, and gives your AI assistant fix guidance for each finding. Deterministic and local, with no account or API key.81MIT

Skarnofficial
AlicenseNot gradedqualityBmaintenanceScans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted36MIT- AlicenseAqualityBmaintenanceA free, read-only server that lets users diagnose production AI-agent risks: it flags over-privileged API keys from permission descriptions, scans code snippets for the signals that prevent duplicate execution, and explains guard patterns such as idempotency keys, approval gates, outboxes, and circuit breakers. It makes no network calls or writes, and rejects inputs that look like real secrets.328 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.