io.github.rafaelcg/stripekit
NPM · STRIPEKIT · SCANNED SEP 20
Reconcile a declarative Stripe catalog and inspect your account — plan, push, pull, check.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 349 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.rafaelcg/stripekit MCP server?
io.github.rafaelcg/stripekit runs locally as an npm package, launched with npx -y stripekit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · stripekit
claude mcp add rafaelcg-stripekit -- npx -y stripekit
{
"mcpServers": {
"rafaelcg-stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
} {
"servers": {
"rafaelcg-stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
} codex mcp add rafaelcg-stripekit -- npx -y stripekit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rafaelcg-stripekit": {
"type": "local",
"command": [
"npx",
"-y",
"stripekit"
],
"enabled": true
}
}
} openclaw mcp add rafaelcg-stripekit --command npx --arg -y --arg stripekit
mcp_servers:
rafaelcg-stripekit:
command: "npx"
args: ["-y", "stripekit"] {
"McpServers": {
"rafaelcg-stripekit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"stripekit"
]
}
}
} assistant mcp add rafaelcg-stripekit -t stdio -c npx -a -y stripekit
{
"mcpServers": {
"rafaelcg-stripekit": {
"command": "npx",
"args": [
"-y",
"stripekit"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −2
- Stability: pass → 0.80 functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/stripekit@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
stripekit_check stripekit check ~67
Verify the Stripe key, config validity, config-vs-account drift, and webhook/portal wiring. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory containing stripe.config.ts (defaults to the server working directory). |
| url | string | – | Base URL used when resolving the webhook endpoint. |
No output schema declared.
No examples provided.
stripekit_plan stripekit plan ~81
Preview the changes that reconciling the Stripe account to stripe.config.ts would make (create/update/replace/archive products, prices, webhook, portal). Read-only — mutates nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory containing stripe.config.ts (defaults to the server working directory). |
| url | string | – | Base URL used when resolving the webhook endpoint. |
No output schema declared.
No examples provided.
stripekit_pull stripekit pull ~48
Generate stripe.config.ts source from the existing Stripe catalog, to adopt an account. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory containing stripe.config.ts (defaults to the server working directory). |
No output schema declared.
No examples provided.
stripekit_push stripekit push ~153
Reconcile the Stripe account to stripe.config.ts. DRY-RUN by default (returns the plan and changes nothing). Set apply:true to actually create/update products, prices, the webhook, and the portal. A live-mode key additionally requires live:true. Prices are replaced (not mutated) and removed items are archived (not deleted); existing subscriptions are never disrupted.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | Actually apply the changes. Default false (dry run). |
| cwd | string | – | Project directory containing stripe.config.ts (defaults to the server working directory). |
| live | boolean | – | Required together with apply:true to modify a LIVE-mode Stripe account. |
| url | string | – | Base URL used when resolving the webhook endpoint. |
No output schema declared.
No examples provided.
What is the io.github.rafaelcg/stripekit MCP server?
io.github.rafaelcg/stripekit is an MCP server listed in the public MCP registry as io.github.rafaelcg/stripekit. Reconcile a declarative Stripe catalog and inspect your account, plan, push, pull, check. This page covers its npm package (stripekit).
Is the io.github.rafaelcg/stripekit MCP server safe to use?
io.github.rafaelcg/stripekit scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.rafaelcg/stripekit MCP server expose?
io.github.rafaelcg/stripekit exposes 4 tools: stripekit_plan, stripekit_check, stripekit_pull, stripekit_push. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.
Is the io.github.rafaelcg/stripekit MCP server still maintained?
io.github.rafaelcg/stripekit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rafaelcg/stripekit MCP server under?
io.github.rafaelcg/stripekit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.