All MCP Servers
Commerce & RetailMCP Registryremote1 toolsD · 33

stripecheckup MCP server

app.vercel.stripecheckup · Updated

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

At a glance

stripecheckup is an MCP server in the Commerce & Retail category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 1 tool, including check_stripe_code. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install stripecheckup in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install stripecheckup in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add --transport http stripecheckup https://stripecheckup.vercel.app/api/mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. check_stripe_code). It discovers them automatically.

What tools does stripecheckup expose? (1)

Read from the live server. Click any tool for its input schema.

  • check_stripe_codePaste 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 .

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Third-party hosted service — Your requests and any data in them are sent to stripecheckup.vercel.app.
  • No local execution — Nothing is installed or run on your machine.
  • No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

D · 33

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%not measurable

    No commit history available.

  • Adoption20%not measurable

    No usage data available.

  • Transparency20%25%

    1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

  • Provenance15%0%

    No source repository to trace the code back to.

  • Packaging15%75%

    Remote endpoint; authentication requirements not declared.

Maintain stripecheckup? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![stripecheckup on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/app-vercel-stripecheckup-stripecheckup)](https://mcp-skills-hub.vercel.app/mcps/app-vercel-stripecheckup-stripecheckup)

Catalog data refreshed . Something wrong? Report it.