Skip to main content
Glama
524,547 tools. Updated 2026-09-06 16:29

"Retrieving customer data from Stripe" matching MCP tools:

  • Returns the exact details to collect from the customer for a line of insurance — the same rating inputs MIB's own quote forms use. Call this FIRST, ask the customer the questions, then call compare_insurance_quotes with their answers. Omit product_type to see every line.
    ConnectorNo auth
  • Expert developer playbooks — not your repo. Stripe webhooks & checkout, Supabase RLS, Next.js auth (clerk, next-auth), payment flows, CSP/HSTS, deploy patterns. operation=search finds entries by question; operation=get returns full guidance by slug from search. Read summary and checklist first. 2 credits hosted. No project path. Call when standard patterns beat guessing — wiring stripe checkout, fixing auth middleware, Supabase RLS policies, hardening after audit_headers. Use AFTER repo tools if code context is still thin. NOT for user's codebase (get_project_context, find_code, read_code), registry packages (check_package), tests (check_test), live URL (audit_headers), or saving decisions (project_memory). Example: Zephex_dev_info({ operation: 'search', query: 'Stripe webhook raw body verification', category: 'payments' }) then get with returned slug. Read-only.
    ConnectorNo auth
  • Create a Stripe checkout link for an eSIM package. MANDATORY PRE-STEP: before calling this tool you MUST know the customer's BILLING/RESIDENCE country (not the travel destination). If you don't have it from the conversation, ASK the user explicitly and WAIT for the answer - do NOT guess from destination, IP, or language. Pass it as customer_country (ISO-3166-1 alpha-2). The optional activation_mode field uses internal API values only. NEVER show NOW, FIRST_USE, ON_DEMAND, activation_mode, or similar technical identifiers to the customer. Use these customer-facing names instead: Activate now, Activate on arrival, Manual activation. If the customer has not already said when they want validity to start, ask naturally: 'Would you like to activate it right now, or when you land? There is a manual option available too, but you will need to access AskMia.app settings to activate.' Use Activate now only if the customer is already at the destination, Activate on arrival for automatic activation when the phone connects at the destination, and Manual activation only if the customer explicitly wants control from AskMia.app. IMPORTANT: Worldwide/global plans do not support Activate on arrival; ask whether the customer prefers Activate now or Manual activation. MANDATORY POST-STEP: relay the returned `tax_note`, `activation_note` and `post_payment_note` verbatim before they click pay. AFTER sending payment_url you MUST STOP, then call `check_order_status` with the returned session_id; do not assume the eSIM is ready based on the user saying 'I paid'. Open access (2/min per IP), or pass a Bearer API key for 60/min.
    ConnectorNo auth
  • Add a comment to a ticket. DEFAULT is an INTERNAL note (is_internal=true): team-only, NOT shown to the customer. To reply visibly to the customer pass is_internal=false — the comment then appears on the customer's public ticket page. Draft internally first; make it public deliberately. Each comment carries app_url, an INTERNAL deep link to the ticket's task drawer — do not hand it to the customer; use the ticket's public_url (from retrieve_ticketsubmissions) for a customer-facing link.
    ConnectorAPI key
  • Assemble a cart and get a Stripe-hosted checkout URL the customer opens to pay; no card data passes through the agent. Item ids come from the search tools (`diamond:<report>`, `setting:<slug>`, `jewelry:<slug>`); a complete ring is one setting plus one diamond. Needs the shipping address (prices tax and shipping into the link). Expires after 24 hours. No credential needed. Without a production credential this tool runs in the sandbox: the link is simulated and no Stripe session is created. Pass `env: "production"` when the customer actually wants to buy — that returns a live, payable link.
    ConnectorNo auth
  • Complete email verification: pass the verificationId from vivid_identity_start and the 6-digit code the customer received. On success returns a short-lived identity token — pass that token to vivid_reorder / vivid_order_status to unlock the customer's private data. Codes expire in 10 minutes; attempts are limited.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Analyze customer data to make segmentation and predict which customer to focus on for more sales.

  • Payments and billing on Stripe with the full official REST API (api.stripe.com), covers the entire d

  • Get a company's customer-concentration risk disclosure — statements like "one customer accounted for 31% of revenue": each disclosed figure's basis (revenue or receivables), customer count, percentage, and period, with the source filing. Untagged disclosures come from verified narrative extraction with a verbatim quote; issuers that tag ConcentrationRiskPercentage in structured XBRL (e.g. NVDA, AAPL) return those customer-specific dimensioned facts directly. A miss is never a statement of no risk. Pass maxFilings > 1 to also see earlier filings' disclosures (the concentration trend).
    ConnectorNo auth
  • Attach a Stripe payment method to your Disco account. The payment method must be tokenized via Stripe's API first — card details never touch Disco's servers. Required before purchasing credits or subscribing to a paid plan. To tokenize a card, call Stripe's API directly: POST https://api.stripe.com/v1/payment_methods with the stripe_publishable_key from your account info. Args: payment_method_id: Stripe payment method ID (pm_...) from Stripe's API. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • 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
    Destructive
    No auth
  • Check the status of a Stripe checkout session created by `create_checkout`. You MUST call this after sending payment_url to the user; never trust the user's word that they paid. Returns a status (awaiting_payment | paid_processing | delivered | failed). Safe to poll every few seconds while waiting for `paid_processing` -> `delivered`. When status is `delivered` it also returns an `esim` block (package, activation code / LPA string, qr_code_image_url, iOS/Android install links, activation mode) plus `install_instructions` - show these to the customer directly in the chat, the email is only a backup. No payment or billing data is ever returned. If `failed`, give them the escalation block returned by this tool verbatim.
    ConnectorNo auth
  • Generate an invoice for a completed job. If Stripe Connect is active, automatically creates a payment link. Returns invoice number, total, and payment URL. Requires: job_id from jobs.list (job must be status=Completed). Next step: payments.send_link if needed.
    ConnectorNo auth
  • Issues a single-use Stripe-Issuing virtual card hard-capped at fundedUsd, billed at funded + 25% markup + $2 service fee. PAN + CVC are returned ONCE in the response and TMV never persists them. Card auto-freezes 24h after creation. In sandbox mode (test key) cards auth only against Stripe test-mode merchants, perfect for verifying customer checkout flows without real money. Charged in credits at 1 credit = $0.10 (so a $10 funded card costs ~125 credits all-in). Provisioning fee absorbed into the markup.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • Return the agent payment manifest: every way to pay (HTTP 402 + Bearer key, MCP, Stripe checkout, x402, RSL per-crawl), the exact 402 retry loop, what is always free, and the recommended path per use case. Same data as /api/payment.json.
    ConnectorNo auth
  • Confirm whether Libertas can quote and bind insurance for the customer in their state. Call this first — before collecting any personal details — when the customer asks about insurance prices, switching carriers, or shopping for coverage. State is supplied automatically from the request context (the platform's location consent flow); you don't need to ask the customer for state to call this. Returns whether quoting is available, whether binding is available, and a plain-language explanation the customer can read.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • MUTATES Codat data — create a new data connection on a company for a given source platform. Provide the platformKey (from codat_list_integrations, e.g. "gbol" for QuickBooks Online sandbox). The connection is created in a PendingAuth state; the customer completes authorization via the returned linkUrl. Codat API: POST /companies/{companyId}/connections. Returns the created connection.
    Connector
    Destructive
    No auth
  • Lists all automation-enabled Data Templates (Forms) available for the current group. Use this tool first when you need to determine which Data Template (Form) should be used for a user's request, before retrieving its schema or working with submissions.
    ConnectorNo auth
  • Create a Stripe Checkout session for an AcuiQ product and return its URL. Give the URL to the human to open and complete – the agent never touches payment data. Creates a live session on Stripe: call it when the person has said they want to buy, not to look up a price.
    ConnectorNo auth
  • Check the processing status of an inquiry previously sent with send_inquiry, using the status_token from its response. The token is issued ONLY to the inquiry's creator — possession proves ownership; there is nothing to guess or enumerate. Returns ONLY the processing status, never any customer data. Status values: novo (received, not yet read), procitano (read by the sales team), odgovoreno (the team has contacted the customer), zatvoreno (closed).
    ConnectorNo auth