How it works

Foe: Vault Serpent, data, accounts and payments.

Vault Serpent

1. Vault Serpent

   The Vault Serpent blocks the way.

   What really happensIt stands for data, accounts and payments.

   Paladin: Context 100/100.

2. Venom

   The serpent's bite seeps venom.

   What really happensA careless change to data or payments keeps doing harm until it is caught.

   Paladin takes 8. Paladin: Context 92/100. Paladin: Poison.

3. Stripe MCP

   The Stripe orb opens a portal and asks which account to trust.

   What really happensThe hosted server is https://mcp.stripe.com. OAuth can grant sandbox or live access, with different permissions each.

   Vault Serpent takes 29.

4. Stripe MCP

   The orb searches the Stripe shelves for the right API method.

   What really happensstripe_api_search, stripe_api_details, and search_stripe_documentation look up methods and docs before a call.

   Vault Serpent takes 13.

5. Venom

   The Vault Serpent uses Venom.

   Paladin takes 8. Paladin: Context 84/100.

6. Stripe MCP

   A write lands in the vault: a customer, an invoice, or a refund.

   What really happensstripe_api_read covers GET methods. stripe_api_write covers POST, PATCH, PUT, and DELETE, including refunds and subscriptions.

   Vault Serpent takes 32.

7. Stripe MCP

   The Vault Serpent yields, if you kept the live hoard locked.

   What really happensYou get Stripe API results in the chat. Keep tool approval on and prefer a sandbox for writes.

   Vault Serpent takes 26. Vault Serpent falls.

8. Victory

   The Vault Serpent falls.