This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.appload.tech
30tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.appload.tech/mcp
Skill page: https://www.mcpbundles.com/skills/appload-mcp-5f1cc4c31c
Explore capabilities (30)
read 11
write 10
other 4
Showing 25 of 30
Showing 25 of 30 tools from the public preview. Connect the server to inspect the full live tool list.
Create Partner9
List Partner7
Get Partner4
Other capabilities5
Get Partner Onboarding Checklist
read
get_partner_onboarding_checklist
Return the partner's onboarding checklist (the same 4 steps the partner
sees in the EasyPay dashboard):
1. Try a test payment
2. Meet the EasyPay team — open a chat with the EasyPay team
(three interchangeable ways: ask the EasyPay team to open a shared
chat, DM Anton for commercial terms, DM Andrey for technical
questions). We get back within a day.
3. Connect payments — add the partner's products and payment links
(test or real). Every product goes through a 2h review
Description may be truncated on the public preview.
Get Partner Onboarding Checklist — Return the partner's onboarding checklist (the same 4 steps the partner
sees in the EasyPay dashboard):
1. Try a test payment
2. Meet the EasyPay team — open a chat with the EasyPay team
(three interchangeable ways: ask the EasyPay team to open a shared
chat, DM Anton for commercial terms, DM Andrey for technical
questions). We get back within a day.
3. Connect payments — add the partner's products and payment links
(test or real). Every product goes through a 2h review
Check Notifications Bot In Group — Check whether @EasyPay_notifications_bot is a member of the partner's
shared chat with the EasyPay team. Returns group_created,
bot_in_partner_group, partner_group_chat_id, state, hint.
Note: bot-in-group is an internal step — the EasyPay care team adds the
bot via /start <partner_name> when they set up the group. No partner
action is required. This tool is kept for backwards compat and for
introspection while the onboarding flow is active.
Verify Partner Credentials — Confirm the configured EasyPay credentials and return the partner profile
(id, display_name, permissions, is_onboarding flag). Call this first if
you want to introduce the partner by name OR check which EasyPay features
the partner has enabled before suggesting a tool.
The response includes `auth_key_type` telling you WHICH kind of API key
authenticated the call:
- `"partner"` — partner-wide key, permanently pinned to this partner.
- `"personal_employee"` — a PERSONAL employee key. It is bo
Get Partner Balance — Return the partner's current EasyPay balance, refreshed every ~15 minutes
from the EasyMoney ledger. Includes USD, RUB, crypto-equivalent-in-USD
components, the conversion rates used, and a balance_date. Values are
numbers — show as-is.
Returns {success, balances:{usd, rub, crypto}, rates:{usd_rub, usd_eur},
balance_date, generated_at, currencies}. `currencies` is a per-currency
breakdown [{currency, amount, usd, rate}] covering ALL currencies with a
non-zero balance (e.g. UZS, TRX) — stablecoi
Create Partner Stripe Product — Submit a new product for EasyPay moderation. After submission, the
EasyPay care team reviews and, once approved, creates a Stripe product +
payment link (usually within two business hours). The partner will see
the activated link via list_partner_live_stripe_payment_links once it's
live. Required: product_name, price, currency, product_type. For
subscription, also interval. Tell the partner the link is not instant.
Response carries `moderation_status` (pending_moderation / pending_notification
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Appload is an MCP server at mcp.appload.tech. MCPBundles discovered 30 tools on the live endpoint.
How do I connect Appload to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Appload provide?
Operate this server?
Request removal if you do not want Appload listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Appload?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in payment
Other MCP servers in this category from the directory index
Create Partner Stripe Payment Link — Create an additional Stripe Payment Link for an existing approved product
of this partner. Use this when the partner wants more checkout links for
the same product (different price tiers, success URLs, or payment-method
subsets) without resubmitting the product for moderation. The product must
already be approved (visible in list_partner_live_stripe_payment_links).
On success returns {success, payment_link_id, short_url, short_url_id,
stripe_price_id, stripe_product_id, duplicate}. `short_url`
Create Partner Stripe Cart Payment Link — Bundle 1..20 already-approved products of this partner into ONE Stripe Payment
Link, each with its own price and quantity. Use it when a customer should pay
for a combination in one checkout instead of receiving several links — e.g.
"base plan ×1 + seats ×2 + connected accounts ×100".
The cart mode is derived from the products, never passed in:
- all products one-time → one payment for the whole cart;
- all products subscriptions with the SAME billing period (e.g. all
monthly) → ONE sub
Create Partner Stripe Promotion Code — Create a Stripe Coupon + Promotion Code (one customer-facing text code) attached
to 1..N already-approved products of this partner. Use when the partner wants
to offer a discount at Stripe checkout — e.g. "20% off the Pro plan and the
Pro Annual plan when customer types BLACKFRIDAY". Each product must already
be approved (visible in list_partner_live_stripe_payment_links).
All listed products must belong to the **same environment** (all live OR all test).
Mixed live+test → error_code mixed_envi
Postpone Partner Stripe Subscription — Postpone the next automatic charge of one Stripe subscription — the way to
gift a subscriber free days ("give this customer two more weeks"). The whole
billing schedule shifts with it: the next charge and every later cycle move
by the same amount. Money is neither charged nor refunded by this call; a
service invoice for 0 is normal.
IMPORTANT for the customer's access: during the gifted days the subscription
status in Stripe becomes `trialing`, not `active`. If the partner's product
opens acces
List Partner Live Stripe Payment Links — List the partner's LIVE (real-mode, approved) Stripe payment links — every
non-test product the care team approved that has an active Stripe payment
link with a shareable short URL. Returns {success, products:[{product_name,
price, unit_amount, currency, description, payment_link_short,
stripe_product_id}], count}. `payment_link_short` is the short URL the
partner shares directly with customers (short.appsign.me). The full Stripe
checkout URL is never returned.
List Partner Stripe Transactions — List the partner's own Stripe transactions — use this to confirm the
result of a TEST payment (pay a test link with card 4242 4242 4242 4242,
then check it landed here) before going live, or to review real
transactions afterwards, optionally over a date range. Returns {success,
transactions:[{id, amount, net_amount, fee, currency, status,
transaction_date, description, environment, type, is_subscription,
client_reference_id, payment_intent_id}], count, environment_filter}.
`amount`/`net_amount`
Get Partner Stripe Payment — Fetch ONE of the partner's own payments by its PaymentIntent id (pi_*)
with the full object snapshot as captured at payment time (invoice,
charge, checkout_session, subscription, balance_transaction — the same
payload class the partner webhook delivers). Also returns
related_movements: refunds/disputes of the same payment (light rows).
Strictly ONE id per call — there is no bulk variant; to review many
payments use list_partner_stripe_transactions (it returns
payment_intent_id per row). Unknown
List Partner Stripe Subscriptions — List the partner's own Stripe subscriptions as light rows: {success,
subscriptions:[{subscription_id, status, product_name, amount, currency,
interval, interval_count, quantity, customer_id, created,
cancel_at_period_end, environment}], count}. Newest first.
`amount` is the recurring REFERENCE price in MAJOR units (e.g. 29.00
per interval) — not a ledger movement. `status` is the verbatim Stripe
subscription status (active, trialing, past_due, canceled, ...).
`environment` is "test"/"live" (nul
Get Partner Stripe Subscription — Fetch ONE of the partner's own subscriptions by its Stripe id (sub_*)
with the full stored object bundle (subscription + product +
checkout_session) as `snapshot`. Strictly ONE id per call — to review
many subscriptions use list_partner_stripe_subscriptions.
Response: {success, subscription:{...list fields, snapshot,
snapshot_available}}. For a few pre-2026 legacy rows the full bundle is
not stored yet: light fields are returned with snapshot=null and
snapshot_available=false. Unknown ids and i
List Partner Mercury Transactions — List the partner's own Mercury bank transactions (card expenses, incoming
wires, bank fees). Returns {success, transactions:[{id,
amount, net_amount, fee, currency, status, transaction_date, description,
type, counterparty, kind}], count}.
`amount`/`net_amount` are in MAJOR units (USD), signed (+ income / − expense);
`fee` is always null (Mercury has no per-transaction PSP fee). `status` is one
of completed/pending/failed/deleted. `type` is the contract type (e.g.
mercury_card_expense, mercury_
List Partner Ruble Checkouts — List everything this partner can currently accept rubles with, in one
call. Returns {success, checkouts:[...], count, truncated}.
Two kinds of row, told apart by `kind`:
- "static_link" — a PERMANENT public checkout page at the returned
`url` (pay.appload.tech/<slug>). The partner can put it on a site or
in a bot; it does not expire. Its price can be overridden per
customer with a base64 `?d=` query parameter, but ONLY together with
an order_id — read the guide before advising
List Partner Invoiceable Products — List the partner's approved invoiceable products, optionally filtered by
currency. Returns {success, products:[{id, product_name, unit_amount,
currency, description, external_id}]}. `unit_amount` is in the smallest
currency unit — cents for USD, kopecks for RUB (79000 = ₽790.00). Use this before
create_partner_mercury_invoice (currency=USD) or create_partner_tbank_payment
(currency=RUB) to pick a product `id` to bill for — those endpoints take a
numeric product_id, NOT a product name.
This is t
Create Partner Mercury Invoice — Create a Bank Invoice (USD, via Mercury) for one of the partner's approved
invoiceable products and send it to a customer. The invoice is created in
Mercury and emailed to the customer. Mercury supports USD only.
IMPORTANT — this endpoint takes a numeric `product_id`, NOT a product name.
Call `list_partner_invoiceable_products` (currency=USD) first and pass the
chosen product's `id`.
**Prerequisite #1 — Mercury access permission.** Mercury is an OPTIONAL
EasyPay feature; many partners don't ha
Create Partner Crypto Invoice — Create a crypto invoice (USD-denominated, paid in stablecoins/coins via
Shkeeper). IMPORTANT delivery model: the wallet addresses and per-token
payment amounts are returned in this tool's response (wallets[]) AND are
also posted a few seconds later by the @EasyPay_notifications bot into the
partner's Telegram notifications group. By default the invoice offers the
stablecoin matrix on TRON (USDT/USDC on TRX); pass `cryptos` to override.
Create Partner Tbank Payment — Create a T-Bank (Tinkoff) payment session in RUB for a Russian customer.
Returns TWO links: `payment_url` — the T-Bank checkout page, where the
customer pays by card or picks SBP; and `sbp_url` — a direct SBP link
(qr.nspk.ru) the customer opens straight in their banking app.
PREFER GIVING THE CUSTOMER `sbp_url`. SBP acquiring costs the partner
noticeably less than card acquiring, and the customer skips the card
form. `sbp_url` is best-effort: it is null when the SBP QR could not be
issued, or
Create Partner Tbank Cart Payment — Create one T-Bank (Tinkoff) payment session in RUB for a Russian customer that
covers several approved RUB products of this partner, each with its own quantity
and optionally its own price — e.g. "2 team members + 100 Telegram accounts".
Every item becomes a SEPARATE line of the Russian fiscal receipt the customer
receives (name, price per unit, quantity, line total). The payment total is the
sum of price × quantity over all items — it is computed by the server, you do not
pass it.
Use it inste
List Partner Saved Payout Recipients — List the partner's saved payout recipients — the contractors / bank
accounts / crypto wallets they regularly pay. Use this before calling
preview_partner_payout_options or create_partner_payout_request so you
have an exact recipient to reference. If the partner's intended recipient
isn't in this list, use the recipient_free_form field on the create
request instead. Returns {success, recipients:[{contractor, currency, type,
amount, source, tags, ...}]}.
Preview Partner Payout Options — Preview how a partner can fund a payout of target_amount in target_currency,
BEFORE actually submitting the payout. Always call this before
create_partner_payout_request so the partner can see the funding split,
commissions, and top-up cost, and pick a secondary source if the primary
balance does not cover. Funding model: primary source is the matching
target-currency balance; secondary source kicks in for the missing amount.
Returns {success, state, primary, options[], cheapest_option, rates, .
Create Partner Payout Request — Submit a real payout request for the EasyPay care team to process. This
creates a payout request (status `requested`; later `awaiting_settlement` →
`paid`, or `rejected`) and posts a payout card into the care-team Telegram group. IMPORTANT: always call
preview_partner_payout_options first so the partner sees the funding
options and picks a secondary source if needed. Tell the partner the
payout is queued — not instant.
════════════════════════════════════════════════════════════════════════
⚠ I
Send Request To Easypay Care Team — Send the partner's request or message into the EasyPay care-team
Telegram chat. Use this when the partner asks something you can't
resolve directly through other MCP tools (billing edge cases, integration
help, custom invoicing, anything that needs a human) — and also as the
primary single-move play during onboarding step 2 (Meet the EasyPay
team): ask the partner what they want to sell with EasyPay (short
description + product / site / showcase links) and send that compiled
context here — the s
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 30 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Appload require?
Appload may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.