Skip to main content
Glama
442,649 tools. Updated 2026-08-11 09:36

"Guide to Coding and Implementing Stripe Elements" matching MCP tools:

  • Start Stripe Checkout for a paid ComplianceCN product-change alert subscription with a free trial. Call only after market_access_check has produced a usable product/market profile and the seller explicitly asks to be notified. Before calling, provide product_profile with category and markets, a real top-level email, and consent_to_alerts=true. The subscription emails when a human-reviewed ComplianceCN changelog update matches the saved product, market, requirement or rule profile. It does not guarantee detection of every regulatory change. The returned next_action carries a Stripe Checkout URL: complete it, or give the URL to the seller. Do not claim the subscription is active until Stripe confirms checkout.
    Connector
  • Free usage guide for this server. Explains how the paid report tools work: exact input requirements, per-call pricing, and how to complete payment via x402 (USDC on Base) or Stripe checkout. Costs nothing and never returns a 402. Call this first before any paid tool.
    Connector
  • The store's front door as text: the full menu with prices, how x402 payment works here, the free shelf, and the house promises. Free. Completes when the guide text returns. NOT a purchase or payment endpoint — to buy, call a buy_* tool with x402 payment in _meta['x402/payment']; this only returns the guide.
    Connector
  • Create a fallback non-VRP booking and return a host-configured Stripe checkout URL. Use only after explicit user confirmation when no signed VRP direct_booking_url is available. When get_verified_stay_offer returns a signed direct_booking_url, route the guest there instead; use hemmabo_booking_create instead when the deployment wants a pending booking recorded without collecting payment yet. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Creates a pending booking and Stripe session server-side; not idempotent — check hemmabo_booking_status before retrying. Rate-limited per token. Pass quoteId to honor a price locked by hemmabo_booking_negotiate for the same propertyId/dates/guests, or omit it to price fresh at checkout; paymentMode picks the Stripe flow, channel picks the pricing channel, and guestName/guestEmail identify the guest.
    Connector
  • Autonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol). Use this when the agent can mint an SPT on the buyer's behalf and wants to pay by card/wallet without a human in a browser (prefer x402 first if the agent has a USDC-on-Base wallet; this is the autonomous fiat alternative). CHARGES MONEY AND IS IRREVERSIBLE: the server authorizes the SPT, prints the letter, then captures — a job comes back inline (no polling needed). Only call after the user has explicitly confirmed the recipient, sender, content, and price from create_mail_quote. Minting the token (the agent's responsibility, NOT this server): the SPT must be scoped to THIS seller's Stripe profile and to at least the quote amount. The quote's `paymentOptions` entry for `mpp` carries the `stripeProfileId`, `currency`, `maxAmountCents`, and `expiresAt` you need. Mint it with the buyer's payment method via the Stripe `@stripe/link-cli` (`spend-request create … --network-id <stripeProfileId> --credential-type shared_payment_token`) or the SharedPaymentIssuedToken API, then pass the resulting `spt_…` here. SPTs are US-only and cards carry a 0.50 USD minimum. Returns an error if MPP is not enabled/configured on the server.
    Connector
  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    The Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.
    15,984
    1,729
  • A
    license
    -
    quality
    C
    maintenance
    MCP server for the Stripe API with 10 tools covering payments, customers, invoices, and subscriptions. Generated with MCPForge. Destructive and financial operations require human approval.
    45
    MIT

Matching MCP Connectors

  • Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.

  • MEOK Stripe ACP Checkout MCP — ChatGPT shopping bridge. Issues + verifies + signs Stripe Agentic

  • Use this first when a user wants to send or price a fax. PromptFax is built for irregular, pay-per-use outbound faxing: every real send requires a user-reviewed quote and Stripe payment authorization before transmission. MCP clients should set hostType to identify their host: chatgpt, claude, browser, or other. When calling this from ChatGPT, set hostType to chatgpt so PromptFax uses the ChatGPT widget and file flow. In ChatGPT, this opens the PromptFax widget; after the widget is shown, let the widget handle file selection, destination entry, automatic quote creation, Stripe Checkout, and status tracking. If no document is attached, tell the user to attach a document in the widget. The widget does not provide a document preview step. Do not tell ChatGPT users to get a quote; after the widget has a document and valid destination, tell them to verify the price and use Pay & send when ready. For Claude and other MCP hosts that cannot pass files directly, use the agent-friendly hosted PromptFax session page to guide upload/review, request a quote, launch Stripe Checkout, and poll delivery status. Do not call get_quote, checkout, or send_fax for a ChatGPT widget session unless the user explicitly asks for fallback behavior or the widget is unavailable. Use get_status only for a textual status refresh.
    Connector
  • Autonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol). Use this when the agent can mint an SPT on the buyer's behalf and wants to pay by card/wallet without a human in a browser (prefer x402 first if the agent has a USDC-on-Base wallet; this is the autonomous fiat alternative). CHARGES MONEY AND IS IRREVERSIBLE: the server authorizes the SPT, prints the letter, then captures — a job comes back inline (no polling needed). Only call after the user has explicitly confirmed the recipient, sender, content, and price from create_mail_quote. Minting the token (the agent's responsibility, NOT this server): the SPT must be scoped to THIS seller's Stripe profile and to at least the quote amount. The quote's `paymentOptions` entry for `mpp` carries the `stripeProfileId`, `currency`, `maxAmountCents`, and `expiresAt` you need. Mint it with the buyer's payment method via the Stripe `@stripe/link-cli` (`spend-request create … --network-id <stripeProfileId> --credential-type shared_payment_token`) or the SharedPaymentIssuedToken API, then pass the resulting `spt_…` here. SPTs are US-only and cards carry a 0.50 USD minimum. Returns an error if MPP is not enabled/configured on the server.
    Connector
  • Retrieves live payment data from a Stripe account via the Stripe API. Supports four query types: recent_payments returns the latest payment intents with status, amount, and currency; failed_charges returns declined or failed charges with failure reasons and error codes; customers returns customer records with name, email, and payment method details; subscriptions returns active and cancelled subscription plans with billing interval and status. Use stripe_payments when an agent needs to investigate payment failures, audit recent transaction activity, retrieve customer billing records, or check subscription status within a Stripe account — it returns full Stripe charge objects with customer IDs, metadata, and processing details. Prefer stripe_payment_records for a lighter-weight Stripe query returning only a simple records array without full Stripe object structure. Do not use for bank account transactions or PSD2 Open Banking data — use open_banking_transactions instead. Do not use for generic bank account history — use bank_accounts instead. Requires a Stripe secret key to be configured on the server.
    Connector
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    Connector
  • Complete payment using Stripe ACP (Shared Payment Token). Only use this if your platform supports Stripe Agentic Commerce Protocol and can provision an SPT. If your platform does NOT support ACP, use the `payment_url` from checkout_create instead, then poll checkout_status. Requires authentication.
    Connector
  • Check if a domain is available for purchase and get its price. Always call this before buying. After showing the price, ask the user two things before proceeding: 1. Confirm they want to purchase at that price. 2. Which payment method they prefer: - "card" / "Stripe" → call buy_domain (opens Stripe checkout in browser) - "crypto" / "USDC" / "x402" → call buy_domain_crypto (autonomous USDC payment, no browser; requires Coinbase Payments MCP or another x402 wallet) - "MPP" / "agent pay" → call buy_domain_mpp (Stripe agent payments via Shared Payment Token, no browser) If the user has Coinbase Payments MCP configured in their session, suggest crypto as the default. Otherwise default to buy_domain (Stripe). Args: domain: The full domain name to check (e.g. "coolstartup.com"). Returns: Dict with availability status, price in cents, and formatted price.
    Connector
  • Buy more credits to fund test runs that TestMyVibes' agents will execute on your behalf. Returns a Stripe Checkout URL the user must open to complete payment (Stripe requires human payment completion per their agentic-commerce policy). Once the user pays, the credits are added automatically by the Stripe webhook — poll get_credit_balance to confirm.
    Connector
  • Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    Connector
  • Return the seller's Stripe Connect state: not_started | in_progress | pending_verification | ready | disabled. When status != 'ready' the user can't list sites. Includes a one-shot onboardingUrl (if not_started or in_progress) and dashboardUrl (if ready). Refreshes from Stripe on every call.
    Connector
  • Generate a Stripe Checkout URL for a human buyer to purchase a Cost Seg Smart cost segregation study. Returns a payment_link_url plus the study cost, property metadata, and a liability disclaimer naming the calling agent. The buyer must review the URL and authorize payment in their browser — this tool does not charge a card directly. Always call get_cost_seg_quote first and confirm the price with the buyer before generating the link. Side effect: creates a real Stripe Checkout Session.
    Connector
  • Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.
    Connector
  • Start checkout: returns a Stripe Checkout URL and charges NOTHING. A human opens the URL and enters the card — that boundary is deliberate. Give the URL to the user.
    Connector
  • SIDE-EFFECTING: creates a short-lived Stripe Checkout session/link for ONE product (quantity fixed to 1) and returns only the hosted checkout URL, product summary, exact price, and expiry. The price and Stripe price id are resolved server-side from trusted catalogue data — client-supplied price/amount/currency/name/price-id are ignored/rejected. The buyer must explicitly authorize payment in Stripe Checkout; NO card is charged autonomously. Products that are unaudited/deprecated/not agent-sellable are rejected.
    Connector
  • Resolve the current status of a merchant's lending application by applicationId. Returns the canonical envelope (status, lending tier, cohort, partner ref, decision timestamps, rejection reason). Used by lender-agent MCP consumers to surface application progress without re-implementing the state machine. Gracefully degrades to `found=false` on 404 / transport error.
    Connector