Skip to main content
Glama
772,735 tools. Updated 2026-11-12 18:05

"PowerBI and Databricks Genie Code Integration" matching MCP tools:

  • Wait for an SMS verification code / OTP to arrive on a Palmyr phone number you own, and return the parsed code. Blocks up to timeout_s (default 60, max 90) checking every ~2s — one call replaces hand-rolled polling of phone_read_messages during account signups and 2FA flows. Messages that arrived up to lookback_s seconds (default 10) BEFORE the call also match, so a code that landed early is not missed — pass lookback_s=0 when reusing a number across signups so a stale code can't be re-served. Default extraction handles standalone 4-8 digit codes, 'code is/code:' tokens, and Google-style G-XXXXXX; pass pattern to override (max 256 chars; a pattern that blows its per-match budget is dropped mid-wait and pattern_timeout: true is reported). Returns { found: true, code, message_text } on a hit or { found: false, waited_s } on timeout (not an error — just call again). Costs 0.02 USDC, paid per-action via x402.
    ConnectorNo auth
  • Send the account holder a code to link the card issuer Starts the one-time card issuer link: the card issuer sends a one-time code to the account holder. Then call `POST /verify-card-issuer-link` with the code they enter. **The account holder, never the agent, receives and enters the code.** Send your human to their own inbox (or phone) and have them type the code into your interface. Never try to read the account holder's email or messages yourself, and never ask for their email password or access. **Where the code goes.** An account with an email on file always gets the code at that email; `email` and `phone` are ignored for it. An account with no email (a wallet-only sign-in) must send exactly one of `email` or `phone` (E.164). The response names the destination masked, never in full. **Limits.** Codes last 10 minutes. At most 5 codes can be sent per account in any rolling hour (`429`, with `Retry-After`). Sending a new code replaces the previous one, which then stops working. **Prerequisite:** Laso identity verification (`403 kyc_required` otherwise, with a `kyc_url`). If the account is already linked, this answers `200` with `status: linked` and sends nothing, so calling it twice is safe. **This route is free.**
    ConnectorOAuth
  • Run the enforced Axint Apple build loop outside the Xcode UI. Use: use for the complete proof loop; use swift.validate, cloud.check, or fix-packet when only one stage is needed. Inputs: integration=minimal enforces local advisory no-fix behavior; background returns a job id; outputDir controls artifacts. Effects: starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.
    ConnectorNo auth
  • Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.
    ConnectorNo auth
  • Use this after `create_invoice` or `get_invoice` returns `verification_required`. Arguments: `{ challenge_id, code }`. On success returns a `verification_token`. Retry the same call with the same arguments plus that `verification_token` passed in its `verification_token` field. The token is reusable for ~30 min, so thread the same one into every subsequent `create_invoice` for the same sender email until it expires. Only ever call this with a code the user gave you: attempts are capped and the fifth wrong code revokes the challenge, after which (or once it expires after 15 minutes) no code works. `verification_revoked` means exactly that, so call the tool that sent the code (`create_invoice` or `get_invoice`) again to send the user a new code, never retry this one; on the hosted endpoint such a challenge reports `verification_invalid` instead, so after five failed codes do the same. A `rate_limited` error means stop and tell them to wait, not retry.
    ConnectorNo auth
  • Drop the promo code from the cart, so totals go back to full price (a bundle price, if any, still applies). Use it when the human no longer wants the code; it isn't needed before apply_promo, which replaces the code anyway. Safe to repeat: with no code applied or an empty cart it does nothing and still returns applied=false.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Read-only access to Genie accounts, transactions, investments, and financial summaries.

  • Your Databricks Lakehouse in natural language: run SQL on your SQL warehouses, track long-running qu

  • Redeem the emailed 6-digit code for a reveal-once workspace API key. UNAUTHENTICATED. `email` + `code` must match a code issued by signup(email) within the last 15 minutes (5 attempts max). The returned `api_key` is shown exactly ONCE — store it ONLY in the MCP client config ("Authorization: Bearer <api_key>"), NEVER in a repo or a file you might commit. Reconnecting this server with the header set and calling get_onboarding_status() continues setup. An invalid/expired/consumed code returns a uniform error; a fresh code comes from signup(email).
    Connector
    Destructive
    No auth
  • Real-time operational state of the public Lunium services, measured by an internal probe every 5 minutes: overall state plus per-component state (api, pix_charge = cash-in rail, crypto_sale = cash-out rail, webhooks, contract_docs) with latencies in ms, mapped to operational | degraded | unavailable | unknown. Missing, unknown or stale observations are not proof of an outage. Call it BEFORE debugging your own integration: if a rail is degraded, the right move is to wait or inform your user - not to rewrite working code. Also call it right after a call failed with erro=provedor_indisponivel or tempo_esgotado, to distinguish a Lunium-side incident from a mistake in your payload. Free, no key, safe to call often (new data at most every 5 minutes).
    ConnectorNo auth
  • Pick the correct New Zealand tax code for an IR330, and explain why. Use for: 'what tax code should I use', 'M or ME tax code', 'secondary tax code NZ', 'SB S SH ST SA which one', 'tax code for second job', 'am I on the wrong tax code'. THE WRONG CODE IS ONE OF THE FEW PAYROLL MISTAKES THAT COSTS MONEY QUIETLY ALL YEAR, and there are two ways to get it wrong. A SECONDARY CODE IS CHOSEN ON TOTAL INCOME ACROSS ALL JOBS, NOT ON WHAT THE SECOND JOB PAYS. Someone earning $60,000 in a main job and $8,000 in a second is SH, not SB. Choosing on the smaller figure under-taxes and produces a bill at year end. ALWAYS ASK FOR TOTAL INCOME before answering a secondary code question. If total_income_all_jobs is omitted this falls back to this job's income and returns a warning saying the band is very likely wrong; pass that warning on rather than reporting the code as settled. ME IS NOT SIMPLY "M PLUS A CREDIT". The Independent Earner Tax Credit, worth up to $520 a year, is withdrawn by receiving Working for Families, a main benefit or NZ Super, so someone inside the $24,000 to $70,000 band can still correctly be an M. Add SL when a student loan is being repaid. On a SECONDARY job the repayment is 12% of the gross with no threshold at all, because the repayment threshold belongs to the main job. That catches people who expect the threshold twice. Special tax codes, non-resident status and multiple secondary jobs are out of scope here; those need Inland Revenue. Args: annual_income: Income from THIS job, before tax. job_type: primary for the main job, secondary for any other. total_income_all_jobs: Total across every job. Needed for secondary. has_student_loan: Whether a student loan is being repaid. receives_wff_benefit_or_super: Working for Families, a main benefit or NZ Super. Any of these removes IETC eligibility. Returns: The code, what it means, why it applies rather than the alternative, the flat rate for a secondary code, and any warning about the inputs.
    ConnectorNo auth
  • One COMPLETE quarterly card, free — the identical payload the paid route returns for that card, not a trimmed preview. Two company-quarters (AMD fy2026-q2, MRVL fy2027-q2) are published free in both the quantitative and qualitative families, in the exact schema and field names every paid card uses, so a parser written against a sample works unchanged against any card you buy. Use it as a zero-cost integration test before paying for coverage. Any other ticker returns not_a_sample.
    ConnectorNo auth
  • One COMPLETE quarterly card, free — the identical payload the paid route returns for that card, not a trimmed preview. Two company-quarters (AMD fy2026-q2, MRVL fy2027-q2) are published free in both the quantitative and qualitative families, in the exact schema and field names every paid card uses, so a parser written against a sample works unchanged against any card you buy. Use it as a zero-cost integration test before paying for coverage. Any other ticker returns not_a_sample.
    ConnectorNo auth
  • List the postcoordination axes WHO allows for one ICD-11 stem code (MMS linearization, pinned release). Postcoordination means attaching extra detail to a stem code — severity, laterality, anatomy, causing agent, etc. — to build a composite (cluster) code. Use this tool to: - See which axes a stem code accepts before building a composite code - Check which axes are REQUIRED vs optional - See whether an axis takes one or several values, and how many values it offers Provide an ICD-11 `code` (e.g., "BA00"). Returns one entry per axis with `axis_name`, `required`, `allow_multiple` and `value_count` — the count of allowed values, not the values themselves. A code with no postcoordination, or one WHO does not know, returns an empty `axes` list (not an error), so check the code with icd11_lookup if the list is unexpectedly empty. When NOT to use: this does not build or validate a composite code, and it does not list the allowed values; to get a code from a disease name, use icd11_search.
    ConnectorNo auth
  • Ranked unified search for equivalent terms across multiple medical terminologies. Use this tool to: - Find the same concept in different coding systems - Compare how terminologies represent a concept - Support terminology mapping and data integration Searches across: ICD-11, LOINC, RxNorm, and MeSH. Set `target_terminologies` to limit which are searched, or set `source_terminology` to exclude one (e.g. when you already have a code from that terminology and want equivalents elsewhere). The two combine: source is subtracted from targets. `limit` caps candidates per terminology (default 5, max 10). Every candidate carries `match_score` (lexical similarity to the search term, 0-1) and `rank` (global position across all searched terminologies) — both computed by this server, since upstreams don't expose comparable relevance scores. Candidates from different terminologies whose titles are lexically identical are clustered in `groups` — a strong same-concept signal (absence of a group is NOT evidence of non-equivalence). Searches upstreams in English. For official pt-BR content, use the dedicated tools: `icd11_search`/`mesh_search` accept `language: "pt"`, and `cid10_search` is natively Portuguese.
    ConnectorNo auth
  • Read an existing booking by its ATA confirmation code returned by a successful booking or supplied by the traveler. Never invent a code. Requires a current signed ATA traveler assertion, a verified legacy MCP session, or an approved BOOKING_READ handoff with matching booking email and code. For stateless third-party clients, use start_traveler_handoff with action BOOKING_READ and confirmationCode, then poll get_traveler_handoff_status. Returns booked stay, prices, payments and cancellation terms. Cannot modify, cancel, pay, or create inventory holds. Never use a confirmation code as holdId in get_reservation_status.
    ConnectorNo auth
  • Check the selected service's current runtime readiness, input limits, pricing and retention before use. Returns service and details; ready=false means the underlying service is unavailable. Free cached runtime read; no external probe, payment, analysis or historical document retrieval. Use get_utility_example for a fixed integration sample instead.
    ConnectorNo auth
  • Fetch content stored by handoff_put using its 8-character code. The code is case-insensitive and hyphens are ignored, so 'kvmtrhxp' and 'KVMT-RHXP' are the same; the person may give it as a link like handover.tools/kvmtrhxp, and passing that is fine too. Return the content to the person verbatim and complete: it can be fetched only once. If the code is unknown, already fetched, or expired, content is null with a reason — these cases are deliberately indistinguishable. A channel link (handover.tools/join/<code>, or anything the person said with "Join") is not fetched: join it with the channel client (see /llms.txt). Passed here, it returns reason channel_code with the steps.
    ConnectorNo auth
  • Confirm the email with the 6-digit code, or check whether the email link was clicked. Preferred: confirm_signup(account_id, code, signup_token). The first confirmation returns api_key; store it, it is shown once. Link clicked instead: call confirm_signup(account_id, signup_token) every 5 seconds, up to 10 minutes, until email_verified is true, then call create_api_key. A code allows 5 attempts and lasts 24 hours. For a new code, call resend_code(email).
    ConnectorAPI key
  • Email a verification code to the email address on the user's Porkbun account, to clear VERIFICATION_REQUIRED (purchases and top-ups need a verified email and phone). It is the usual verification email: a link plus a code. Then ask the user for the code in that email (or read it, if you have access to that inbox) and call `confirm_email_verification`; the user clicking the link works too. The address on the account is used (or a new address waiting for verification); it cannot be chosen or changed here, and the code is never returned to you: it only proves the address because it arrives there. A second request within 10 minutes returns `codeAlreadySent`; the earlier code stays valid for 3 days. Guide: https://porkbun.com/llms/guides/verify-the-account
    ConnectorOAuth
  • Use this when the user wants to change a QR code already in their account: where a dynamic code points, its text or content, or its look (colours, shapes, logo, frame, size). Call `get_qr_code_by_id` first and send the full merged settings; this overwrites the saved settings. A static code that is already printed cannot change what it encodes. Do not use it to make a new code (use `generate_qr_code`).
    Connector
    Destructive
    OAuth
  • Consume the 6-digit code the founder received and start the research pipeline. **When:** after `create_application`, and ideally after the deck has been uploaded over plain HTTP (see the `curl` printed by `create_application`). Founder has read the code from their inbox. **Before you call:** - CONFIRM you have the right code from the founder (not guessing, not stale). Once this succeeds, research starts and is irreversible. - If deck parsing is still pending, that's fine — research auto-defers and dispatches when the deck resolves. Don't wait, don't re-verify. **Returns:** `status: researching` + whether research was dispatched now or deferred on the deck. **On error:** - `wrong code` — response includes attempts-remaining. Ask the founder to check their inbox again. If the error says the code is invalidated, call `resend_verification` for a new one. - `no active code` — they never received one, or it expired. Call `resend_verification`. - Already verified — idempotent success; returns current status. Don't retry in a loop.
    ConnectorNo auth
  • Delete a teammate by UUID (a soft delete; their emails are removed from signature deployment). Only available when the workspace manages its own team list — if a directory integration (Google, Microsoft or Zoho Mail) drives teammates, this returns a 409 conflict.
    Connector
    Destructive
    OAuth