Stripecheckup MCP Server

by vercel-stripecheckup Your server? Claim it

answering

Stripecheckup is answering right now. Last checked 15 min ago. It exposes 1 tools.

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

Uptime history 51 days of history · worst day 61%

51 days agonow

89.0%

Uptime 24h

81 of 91 checks

Tools

read from the server

254 ms

Response time

average over 24h

open, no key

Access

streamable-http

Stripecheckup does not always answer

Over the last week it answered 93.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add stripecheckup --transport http https://stripecheckup.vercel.app/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://stripecheckup.vercel.app/api/mcp

~/.codex/config.toml

[mcp_servers.stripecheckup]
url = "https://stripecheckup.vercel.app/api/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

stripe

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.

Endpoints

URL	Transport	State	Latency	Checked
https://stripecheckup.vercel.app/api/mcp	streamable-http	answering	230 ms	15 min ago

Alternatives to Stripecheckup

same job, measured the same way

AI Code Scanner

by guardbee

Scans code for insecure LLM/AI integration: exposed keys, unsafe output, prompt injection

298 installs/wk local only

AI Code Scanner

by 4hmetuyar

Scans code for insecure LLM/AI integration: exposed keys, unsafe output, prompt injection

local only

MCP Stripe Acp

by codespar

Stripe ACP — AI agent checkout, payment delegation, products, invoices

74 installs/wk local only

MCP Stripe

by codespar

MCP server for Stripe — global payments API (PaymentIntents, Checkout, Billing, Refunds)

50 installs/wk local only

Secretguard MCP

by vladimirbakalov

Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.

local only

Infracost

by downatthebottomofthemolehole

MCP server for Infracost CLI integration - cloud cost estimates for Infrastructure as Code

74 installs/wk local only

TraceTail

by tracetail

Browser fingerprinting for web apps: integration code for any framework, docs search and pricing.

6 tools answering

CodeDiag

by sabahattink

Find Node.js API routes with no auth check or input validation, and scan project health.

110 installs/wk local only

Stripecheckup — questions

Answers built from our own checks of this server.

What can Stripecheckup do?

It exposes 1 tools, read directly from the server on our last check. Among them: check_stripe_code. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Stripecheckup working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 81 of 91 checks got a reply (89.0%), average response time 254 ms. The bar chart above shows every period we have measured.

How do I connect Stripecheckup?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Stripecheckup need an API key?

No. Stripecheckup completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Stripecheckup?

It answers our handshake in 254 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.