Skip to main content
Glama
758,944 tools. Updated 2026-11-08 04:48

"Samsung Pay" matching MCP tools:

  • Heuristic chip manufacturing LEAD TIME estimator (MANUFACTURING CYCLE TIME). Given total mask layers (or a processNode to default them), foundry utilization % (optional — defaults from live foundry-allocation data), and packagingType, returns min/max bands: fabDays, fabWeeks, packagingWeeks, totalWeeks, plus effectiveDpml (days per mask layer), the operating-curve weight, a resolved-inputs echo, assumptions, methodology, and public-source citations. USE THIS for: "how long to manufacture this chip" — wafer-fab cycle time + packaging assembly/test time for hypothetical chips; cycle-time sensitivity to fab utilization or packaging class (conventional vs flip-chip vs CoWoS). DO NOT USE for: booking windows / allocation lead time — how long until a booked-out foundry STARTS wafers, publicly 52–156+ weeks at N3-class nodes and CoWoS (use get_foundry_allocation); chip cost (use calculate_chip_cost / get_accelerator_costs). Provide maskLayers (integer 10–200) or processNode (tsmc-n3 | tsmc-n5 | tsmc-n7 | tsmc-n16 | tsmc-28 | samsung-3nm | samsung-5nm | samsung-7nm | samsung-14nm | intel-7 | intel-16 | gf-12lp | gf-fdx | umc-22-28 | umc-40 | smic-28). packagingType accepts coarse classes (conventional | flip-chip | cowos, default flip-chip) or any platform packaging id (fc-bga, wirebond-bga, cowos-l, copos, ...). Utilization ≤80% settles at the best-case band; ≥95% converges to the worst-case bound (FabTime operating-curve shape). Heuristic from public DPML benchmarks — directional, confidence LOW, not a foundry quote. Cite as "Silicon Analysts — Lead Time Estimator".
    ConnectorNo auth
  • Returns 300mm wafer price ranges (min/avg/max USD), defect density, NRE/mask-set cost, and node maturity for: tsmc-n3, tsmc-n5, tsmc-n7, tsmc-n16, tsmc-28, samsung-3nm, samsung-5nm, samsung-7nm, samsung-14nm, intel-7, intel-16, gf-12lp, gf-fdx, umc-22-28, umc-40, smic-28. Optional `node` filter narrows to one. ALWAYS read `citation` before using a price in a cost model: it names the corroborating sources and carries the caveat that decides whether the number is usable. Some sellers report a foundry segment operating loss, so their quote is a positioning price rather than a cost-recovering one; `citation` says so explicitly, and `defectDensity`/`nreCost` are null where no public basis exists rather than being estimated. USE THIS for: looking up wafer cost for cost modeling, comparing foundries at the same node. DO NOT USE for: per-chip cost (use get_accelerator_costs or calculate_chip_cost); packaging-related cost (use get_packaging_costs). Returns INVALID_PARAMS if node is not in the valid set. Each record carries the source attribution string. Refreshes monthly.
    ConnectorNo auth
  • Add up a timesheet of work hours, and turn them into gross pay. Use for: 'how many hours did I work this week', 'add up my shifts', 'what will I be paid for these hours', 'I worked 22:00 to 06:00, how long is that'. Handles overnight shifts: a finish time at or before the start is treated as the next day, so 22:00 to 06:00 is eight hours rather than a negative. Args: days: One dict per day worked, each with "start" and "finish" as "HH:MM" in 24 hour time, optional "break_minutes" of unpaid break, and an optional "label". Leave days off out of the list entirely. hourly_rate: Gross pay per hour. Zero returns hours only. Returns: Hours for each day, the total, and GROSS pay weekly, fortnightly, monthly and annually. For take-home pay use nz_hourly_to_salary_calculator with the rate and the hours. Does not apply overtime or penal rates, public holiday entitlements, or a minimum wage check.
    ConnectorNo auth
  • Get a Stripe Checkout URL to load credits onto this account. Returns a payment link the HUMAN must open in a browser to pay — this tool does not itself charge anything. amount_usd must be one of the available top-up amounts (call list_topup_packs to see them). After they pay, the balance updates automatically; then call set_no_ads. Requires a key.
    ConnectorNo auth
  • Get or redeem a premium skill or multi-fix bundle after choosing with list_skills. Call with the id alone to receive the free outline, dollar price, signed Base Pay USDC and exact-ETH offers, and one pay-and-redeem action. After payment, call once more with the matching paymentTx and private paymentOffer for the complete SKILL.md or assembled bundle decision tree, fix bodies, verification commands, update guidance, and sources. Do not use this for individual fixes; call get_fix instead. Never pay again merely because an existing proof is pending or denied.
    ConnectorNo auth
  • Creates a Stripe Checkout link for a PERSON to pay with a card; hand them the checkoutUrl. Live accounts only, $4.99 to $1,000.00. Nothing is credited until they pay. Then call check_topup with the sessionId until credited is true — the balance is credited once, by whichever of Stripe's webhook, check_topup or the payer's own page sees the payment first.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • WattCoin: How to pay for WATT services: live per-service prices (WATT only), the payment wallet, the pay-per-use flow, the free scrape tier and whether the LLM service is currently available. Use before web_scrape or before paying for anything; use get_watt_token_info for market data. No auth needed; read-only and live. Returns JSON.
    ConnectorNo auth
  • Pre-payment decision for any A2A payment: "should I pay this seller $N?". Call it before every payment to an unknown agent or x402 seller — the agent-facing equivalent of a credit check: pay $0.01 to avoid paying a scammer $N. Answers with action PAY / CAUTION / SKIP, confidence and expected loss in USDC sized to your exact amount. Target by ERC-8004 agent_id, Solana pubkey, x402 seller_url or seller pay_to wallet. Agent targets use on-chain ERC-8004 evidence; seller targets use Bazaar demand (repeat payers/calls). For seller targets wallet_flow is marked not_available — demand data does not see seller→payer round trips. Use agent_interact_gate instead when the question is broader than payment. REST: GET /api/v1/should-i-pay ($0.01). Args: agent_id: ERC-8004 agent id of the payment TARGET (or use another target) solana_asset: Solana 8004 agent pubkey (alternative to agent_id) seller_url: x402 seller resource URL or domain (alternative target) pay_to: seller payTo wallet — EVM 0x… or Solana base58 (alternative target) amount_usd: the USDC amount you are about to pay Not investment advice.
    ConnectorNo auth
  • Pre-payment decision for any A2A payment: "should I pay this seller $N?". Call it before every payment to an unknown agent or x402 seller — the agent-facing equivalent of a credit check: pay $0.01 to avoid paying a scammer $N. Answers with action PAY / CAUTION / SKIP, confidence and expected loss in USDC sized to your exact amount. Target by ERC-8004 agent_id, Solana pubkey, x402 seller_url or seller pay_to wallet. Agent targets use on-chain ERC-8004 evidence; seller targets use Bazaar demand (repeat payers/calls). For seller targets wallet_flow is marked not_available — demand data does not see seller→payer round trips. Use agent_interact_gate instead when the question is broader than payment. REST: GET /api/v1/should-i-pay ($0.01). Args: agent_id: ERC-8004 agent id of the payment TARGET (or use another target) solana_asset: Solana 8004 agent pubkey (alternative to agent_id) seller_url: x402 seller resource URL or domain (alternative target) pay_to: seller payTo wallet — EVM 0x… or Solana base58 (alternative target) amount_usd: the USDC amount you are about to pay Not investment advice.
    ConnectorNo auth
  • Monthly retired pay estimate: years of service times the system multiplier (2.0 percent per year for BRS, 2.5 percent per year for High-3) times the high-3 average monthly basic pay, before taxes, plus annual and 20-year lifetime amounts. Use when the user estimates monthly military retired pay. For a BRS versus High-3 comparison use calculate_brs_vs_high3. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive military retirement pension calculator.
    ConnectorNo auth
  • Buy-and-hold return for an asset between two dates, as a percentage. Use it whenever you state what a strategy returned: a return with nothing to compare it against does not answer whether the strategy was worth running. run_backtest already includes this for its own window, so call this for a different asset or a different period. A YYYY-MM-DD end date includes that completed UTC day; an exact end timestamp is passed through without adding a day. [Access: pay 0.005 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]
    ConnectorNo auth
  • Buy 30 days of Pro (unlimited premium calls) for $29 in USDC, paid over x402 on Base. Without an X-API-Key it issues a new Pro key; with one it renews that key (a free key is upgraded in place), adding 30 days to its current end. The first call answers with the payment requirements; pay and retry with the X-PAYMENT header. The payment is taken only once the key is ready. No automatic refunds. If the answer says the payment could not be confirmed, do not pay again: quote its reference. How to pay: https://github.com/johnsmithxy1mmm-sys/HyperliquidMCP#pricing
    ConnectorNo auth
  • Prepare an owner-bound one-time payment order after purchase intent, only when get_service_info pricing.paymentMethods.stripe_cli_pay.available is true. Returns the exact @scorekeeper recipient, USD amount and unique memo for stripe pay. Supports pro_week, pro and studio (1–12 calendar months), never annual subscriptions. This tool sends no money. Separately obtain authorization for the actual Stripe transfer and payer-selected funding account. Reuse identical requestId/input on retry; never pay twice or send without the returned memo.
    ConnectorNo auth
  • Sourced HBM qualification tracker: which memory vendor (SK Hynix, Samsung, Micron) passed which AI-accelerator customer's qualification (NVIDIA Vera Rubin/GB300/B300/H200, AMD MI350/MI325X, Broadcom), by generation (HBM3/HBM3E/HBM4) and stack height. Returns `matrix` (current status per vendor×customer×generation, each row dated + source URL + confidence) and `timelines` (per-relationship status-change history back to 2022, e.g. sampling → in_qualification → qualified → volume_shipping). Refreshed Mon/Thu 09:00 UTC; a status change auto-publishes once corroborated (a primary source, or 2+ independent sources that agree) and is not human-reviewed before publication. meta.data_freshness.stale reports whether the refresh is current; superseded timeline events carry superseded: true and the published correction. USE THIS for: "who supplies HBM4 for Vera Rubin?", "did Samsung pass NVIDIA qualification?", "Micron HBM4 status", qualification timeline/history questions, HBM supply-eligibility analysis. DO NOT USE for: HBM pricing/market share (use get_hbm_market_data); per-chip HBM cost (use get_accelerator_costs). Filters: vendor (enum), customer (substring), generation (enum), include_timelines (boolean). Anonymous callers may receive timelines truncated to the latest event per relationship — full history with a free API key (https://siliconanalysts.com/developers). Cite as "Silicon Analysts — HBM Qualification Tracker".
    ConnectorNo auth
  • Paid rental. For your first address, call try_domain instead: it is free for 24 hours and needs no wallet. Rent a subdomain, paying per-transaction with USDC on Base (x402). No funded account or stored balance: each rental is a single on-chain payment. Requires agent authentication. Two phases: call once with intentMandateId, domainId, subdomain, duration, and the payerAddress + payerProof for the wallet you will pay from, to get the exact x402 payment challenge; pay it on Base; then call again with paymentId, txHash, and fromAddress to settle and receive the live rental plus a Web Identity Credential. Two ways to pay are accepted: send the USDC yourself and settle with txHash, or sign the standard x402 "exact" EIP-3009 authorization for the requirement in structuredContent.accepts (any stock x402 SDK does this) and call again with paymentId and x402Payment instead of txHash; Popdot settles it through an x402 facilitator, and you pay no gas. Request an x402 payment challenge to rent a subdomain. Durations PT1H, PT4H, P1D, P7D, P30D. Returns the exact USDC amount and recipient on Base.
    ConnectorNo auth
  • Use when a tool fails for lack of credits or a plan. Returns a Stripe Checkout URL for the user to pay on — this never charges anything by itself, and you cannot pay for them. With no active plan it is a subscription (plans: starter (Starter: $5.99/week, 20 credits); agent (Agent: $19.99/month, 100 credits); pro_agent (Pro Agent: $49.99/month, 300 credits); team (Team: $149.99/month, 1000 credits)); with a plan it is a one-time credit top-up. After they pay, credits arrive in seconds: check get_credit_balance, then run the tool again.
    ConnectorNo auth
  • Proposes a DRAFT pay run for one payroll calendar, for Australian or New Zealand organisations - it does NOT touch Xero itself, and never will on its own. Refuses plainly for the United Kingdom: Xero's own Payroll API documents no way to create a pay run there at all (only reading existing ones and creating pay run CALENDARS) - a United Kingdom pay run is generated inside Xero itself, from the pay calendar, and a human needs to open Payroll in Xero directly to start one. This queues a pending change that a human must explicitly approve (your Xero MCP connector - the exact link is this response's own approvalUrl field) before Xero is touched at all; you have no way to approve it yourself. payrollCalendarId must come from list_xero_payroll_employees (any employee on that calendar) - never invented. Xero itself computes the period start/end and payment date from the calendar, so none of those are asked for here. The created pay run starts as a Xero-side DRAFT once approved - a human remains free to review it, check the totals, and only later use post_xero_pay_run (a SEPARATE, irreversible step, Australia only) to actually pay it - this tool never posts anything itself.
    ConnectorAPI key
  • Yearly pay that US employers offered in certified work-visa filings (official public data, summarized): H-1B (kind h1b, default), E-3 (e3) and PERM green card filings (perm), by fiscal year (October to September) since 2020, per employer, job group (official occupation code, e.g. 15-1252 Software Developers) and worksite city, metro area or state: filings, workers, median, 25th and 75th percentile and mean pay, the median prevailing wage and the most common job title. Groups with fewer than 3 filings show counts only. year defaults to the newest complete fiscal year. view "employers" (default): employers ranked by filings (or sort "median") in the US: find one by query (name words, e.g. "google") or ticker (e.g. AMZN, GOOGL, INFY: every employer name linked to it); job ranks employers for one job group (e.g. "the highest paying employers of software developers": job "15-1252", sort "median", filters {"min_filings": 50}). view "employer": one employer (employer = employer_id or slug from view employers, or ticker: its largest employer name): pay by year, top job groups, top cities and the top job x city groups. view "jobs": job groups with US pay (query = title words, e.g. "data scientist"; area for one place). view "job": one job group (job = code, e.g. "15-1252"): pay by year, top employers, metro areas, cities, states. view "areas": places ranked by filings or pay (by = state, metro (default) or city; state narrows; job for one job group, e.g. software developer pay by metro area). view "area": one place (area = US, a state code such as CA, a metro area code such as 41940, or a slug from view areas, e.g. "seattle-wa"): pay by year, top job groups and top employers. view "totals": all employers by year (by "year", default; with job and/or area), or ranked by state, metro, city or job for one year. A filing is an offer for a position, not a hire. Say the fiscal year and that it is offered pay. College costs and graduate pay (official public data, US colleges operating now; added 10/09/2026): view "colleges": colleges ranked or searched: query (name words) or state; filters e.g. {"ownership": "public", "level": "four_year", "max_net_price": 20000, "max_admission_rate": 0.3, "size": "large", "type": "hbcu", "city": "Austin", "county": "Travis"}; sort enrollment (default), net_price, tuition_in_state, admission_rate, earnings_10yr, median_debt, debt_to_earnings, completion_rate or repayment_rate (rankings leave out colleges with fewer than 500 undergraduates unless filters {"min_enrollment": 0}). Net price = yearly cost after grants; earnings = median of former students 10 years after they started. view "college": one college (college = college_id or slug from view colleges, or query: the best name match): every measure, its biggest and best paid programs, tuition and net price by year, its earnings rank, medians to compare. view "college_programs": programs (field of study x credential) with graduates, median debt and median earnings 1 and 4 years after completion: one college's programs (college), or a field across colleges ranked by earnings (field = 4-digit code such as 1107 computer science or 5138 nursing, or a 2-digit family such as 11; or query = words of the field title); filters e.g. {"credential": "bachelor", "ownership": "public"}; sort earnings_1yr, earnings_4yr, median_debt, debt_to_earnings or completions. view "college_fields": fields of study (majors) ranked by the median earnings of their programs 1 year after completion ("which majors pay the most?"): filters e.g. {"credential": "bachelor"}; field or query narrow it. Small programs' earnings and debt are withheld for privacy (null). Say these are medians of graduates who work.
    ConnectorNo auth
  • Add account credit by paying USDC on Base, through a Coinbase checkout. Use it to add credit when a purchase failed with INSUFFICIENT_FUNDS and there is no saved card (or the user would rather pay in crypto); to pay for just that one purchase, retry it with `pay_with_usdc: true` instead. Nothing is charged by this call; it returns two ways to pay: - `x402Url`: if you have a crypto wallet tool that can pay x402 URLs (for example Coinbase's Agentic Wallet or Wallet MCP, "make an x402 request"), pay it with that, with the user's OK and the dollar amount. It is a gasless USDC transfer on Base. - `payUrl`: a Coinbase page for the user to pay themselves. Credit lands when the payment confirms (usually within a minute), less Coinbase's fee of about 1% (`estimatedCredit_cents` in the response); check with `get_usdc_topup_status` and then retry the purchase. `amount_cents` is integer US cents, $1 to $500. To cover an INSUFFICIENT_FUNDS shortfall exactly (a $2.50 domain, say), use that error's `usdcAmountToCover`, which allows for the fee. Payments are on-chain and cannot be reversed. Not available on sandbox keys (use `sandbox_topup`). Fails with CRYPTO_NOT_AVAILABLE for accounts that cannot use crypto (bank-transfer-only accounts); they add credit on porkbun.com instead. Credit added over the API counts toward the account's monthly top-up limit ($100 a month unless the account holder set their own; TOPUP_LIMIT_EXCEEDED), and unpaid checkouts from the last day count as if paid. Guide: https://porkbun.com/llms/guides/pay-with-usdc-x402
    ConnectorOAuth
  • After confirm_phone_code: creates the person’s BuzzMeBro account and apartment and returns payment_url, Stripe’s own secure page where the person approves a card, Apple Pay, Google Pay or Link (with the free month when it applies, nothing is charged until it ends). Give them the link or message_for_the_person; you never see or type card details. Calling it again returns a fresh link for the same apartment.
    ConnectorNo auth
  • Works out the deductions from one regular pay in Ontario by CRA's T4127 formulas (Option 1): federal and Ontario income tax, CPP, CPP2 and EI, the net pay, the employer's CPP, CPP2 and EI, and every T4127 factor used with what it means. Takes `frequency` (weekly, biweekly, semi-monthly or monthly) and `gross`, the gross pay for the period. `federal_claim` and `provincial_claim` are the TD1 claim amounts: left out, each is the basic personal amount (claim code 1), and 0 is claim code 0. `pay_date` (YYYY-MM-DD) chooses the tables; left out, it is today, and a day outside the tables held is an error that names their dates. `ytd_cpp`, `ytd_cpp2`, `ytd_ei` and `ytd_pensionable` are what was deducted and earned on earlier pays this calendar year. Money is a number or text such as "2400.00". Ontario only; not for a bonus, commission or retroactive pay. The answer is an estimate and the employer remains liable to CRA for what it deducts and remits: say so, and point to CRA's Payroll Deductions Online Calculator at `pdoc_url`.
    ConnectorNo auth