Skip to content
TrustedSkillsbeta
Back to all skills

Stripe Mcp Integration

Listed
wrsmith108·vlatest·agents·MIT

Helps with Stripe, MCP tools, integration as part of orchestrating AI agents and multi-step workflows workflows.

Repository

Install on your platform

This skill no longer installs under the name stripe-mcp-integration. wrsmith108/stripe-mcp-skill has no skill named "stripe-mcp-integration" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-09-28. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

wrsmith108

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: packages.stripe.dev.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    packages.stripe.devundeclared

    What it found

    • docs/testing.md:17contacts packages.stripe.dev
      curl -s https://packages.stripe.dev/api/security/keypair/stripe-cli-gpg/public | gpg --dearmor | sudo tee /usr/share/keyrings/stripe.gpg
    • docs/testing.md:361contacts packages.stripe.dev
      curl -s https://packages.stripe.dev/api/security/keypair/stripe-cli-gpg/public | gpg --dearmor | sudo tee /usr/share/keyrings/stripe.gpg

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wrsmith108/stripe-mcp-skill at ce7bf732ee.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
ce7bf732ee
Manifest
SKILL.md
Scanned
6 files, 930 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill integrates with Stripe's Merchant Configuration Platform (MCP) to allow AI agents to manage and retrieve merchant configuration data. It can fetch configurations based on merchant ID, update existing configurations, and create new ones according to specified parameters. This enables automated management of Stripe merchant settings directly from an agent workflow.

When to use it

  • Automated Merchant Onboarding: Automatically configure a new Stripe merchant's settings based on data received from an application form.
  • Dynamic Configuration Updates: Update a merchant’s configuration in response to changes detected by another system (e.g., regulatory updates).
  • Bulk Configuration Management: Modify configurations for multiple merchants simultaneously, such as updating display names or supported currencies.
  • Troubleshooting Merchant Issues: Retrieve and inspect a merchant's current configuration to diagnose problems with payments or account settings.

Key capabilities

  • Fetch merchant configurations by ID
  • Update existing merchant configurations
  • Create new merchant configurations

Example prompts

  • "Get the configuration for merchant ID 'acme_corp'."
  • "Update the display name of merchant 'example_store' to 'Example Store - New Name'."
  • "Create a new merchant with ID 'new_merchant' and supported currencies set to USD,EUR."

Tips & gotchas

  • Requires appropriate Stripe API credentials configured for the AI agent.
  • Be mindful of rate limits when performing bulk operations on merchant configurations.