Terms of Service

Who this is between

1.1These terms are a contract between you and mcprush.com, the operator of the marketplace at mcprush.com. “We”, “us” and “mcprush” mean the operator of mcprush.com; “you” means whoever is using the site or the account. Most accounts are a buyer and a publisher at some point, and the clauses that bind you are the ones describing what you are doing at the time.

1.2We are the merchant of record for every sale on this marketplace. You buy from us. We buy from the publisher under a separate agreement, of which sections 6 and 9 are the substance. There is no contract of sale between a buyer and a publisher.

1.3That is why a refund is ours to give without asking the publisher first (7.6), why VAT, GST and US sales tax, where they are due on a sale, are ours to collect and remit (7.5), why a chargeback is ours to answer, and why nobody is ever invoiced by a publisher.

1.4It is not why the software works. The publisher writes it, licenses it and answers for it. We are the counterparty for the money and for what happens at the gateway. We are not the author of the software in the catalogue, and we do not take on responsibility for it by listing it or by selling access to it, except for the responsibility the law places on us as the seller towards a consumer (13.11, 14.10).

1.5Four roles appear here. A buyer installs or pays for a listing. A publisher lists software from an account that has accepted these terms, including by claiming an indexed entry (5.4). A visitor reads the site without an account. The author of an indexed entry is whoever published the software at its source; being its author does not by itself make them a party to these terms (5.12).

1.6You must be at least 18 and able to enter into a binding contract. If you use the marketplace for an organisation, you confirm that you may bind it, and “you” includes it. You may not use the marketplace if you are, or act for, a person named on a sanctions list of the United States, the European Union or the United Kingdom, or from a country or region under comprehensive sanctions. The marketplace is built for developers and businesses. A “consumer” here means an individual acting for purposes outside their trade, business, craft or profession; if you use the marketplace as one, the protections the law of your country gives consumers still apply to you (7.20, 13.11, 14.10, 15.2).

1.7You accept these terms when you create an account — including by continuing with Google or GitHub — claim an entry, publish, buy, install, or use a key, the CLI or the API. Reading the site without an account is subject to sections 12, 13, 14 and 17 as far as the law allows. If you do not accept these terms, do not use the marketplace.

1.8The prices and plan limits shown on the pricing page and on a listing when you buy are part of these terms. The software itself is licensed under the licence on its listing (3.1, 3.5). An Enterprise contract signed with an account governs that account where it differs from this page (7.13). How we handle personal data is described in the privacy notice; it is a notice, not part of this contract, and it may be updated as that notice describes.

Accounts, seats and keys

2.1An account is free, and reading the catalogue needs no account at all. A seat is a person who can install, approve or hold credentials; a service account, a CI key or a bot is not a seat and is never counted as one.

2.2Anything called with a key issued to your account is your call, and it is billed to you. Keep keys where you would keep a password. Revoking one stops it at the gateway immediately. Rotating one issues a new secret and revokes the old one in the same step, so anything still using the old secret stops until it is given the new one.

2.3Removing a person from a team revokes every key they hold in the same action and ends their sessions. There is no grace period, because the point of removing access is that it stops now.

2.4The owner of an account can ask for it to be closed — a buying account from the dashboard once nothing paid is still running on it and no one else holds a seat on it, a publishing account through support. Within 30 days after a 30-day grace period we delete or anonymise what we hold about it, except what the law requires or allows us to keep: invoices and tax records for seven years, and records of payments, disputes, notices and decisions for as long as we may need them to meet a legal obligation or to establish or defend a claim. The privacy notice says how long each kind of record is kept.

2.5What the site shows you — your plan, your role on a team, what you may do — comes from your session on our server. Nothing changed in your own browser grants any access, and no clause here turns on it.

2.6Keep what you tell us about yourself accurate, keep your sign-in secure, and tell us through support as soon as you think someone else has used your account or one of its keys. Until you do, what happens under the account and its keys is yours to answer for, except where the law says otherwise.

What a buyer gets

3.1Installing a published listing buys a licence to use it on the publisher’s own terms. Those terms are printed on the listing and readable before you install, not after; where a listing states none, 6.13 sets the licence you get. An indexed entry is not offered for sale here: paid access is only to a published listing — one its publisher has listed here or claimed (5.4) — at the price that publisher set on it (3.2, 7.1). The right to use indexed software comes only from its author’s licence (5.10).

3.2We sell you access to a published listing as the seller and merchant of record (1.2), and we answer for the payment and the tax on it. The licence to the software itself is granted to you by its publisher, on the terms printed on the listing or, where none are stated, under 6.13; for an indexed entry it comes from its author’s licence (5.10). We grant no licence of our own to the software.

3.3The licence covers your account and its seats. It does not move to another account and it is not resellable.

3.4Whatever your agent produces with a listing is yours, as far as it belongs to anyone. We claim nothing over it, and no publisher gets a claim over it by way of these terms. Whether it is accurate, lawful or fit to use is for you to judge (13.7).

3.5An open-source listing is governed by its own licence. Where these terms and that licence disagree about the software, the licence wins; where they disagree about the money, this page wins.

3.6A buyer is charged the publisher’s listed price, at cost. We add nothing on top of it except tax where it is due (7.1, 7.5).

3.7You decide what to install and what it may reach. What you send to a listing — arguments, files, credentials — reaches software that a publisher or an author wrote and, for a listing on its own endpoint, runs; how they handle it is theirs to answer for, under their licence and any privacy statement of their own. Give a listing the least access it needs, and keep copies of anything you cannot afford to lose.

When a listing goes away

4.1Deprecated means hidden from the catalogue and still answering. Everyone who has it keeps it, the listing carries a notice that it is no longer maintained, and the publisher can undo it.

4.2Unpublished means no new installs within the hour, and it cannot be undone from the studio. The listing’s address is not given to another publisher for 12 months.

4.3A superseded release stays servable for 90 days after its replacement ships. A pinned install therefore has a quarter to move, not a morning.

4.4When a plan is cancelled, a seat is removed or an install ends, what stops is the gateway. Keys are revoked, so anything proxied or authenticated through us stops answering at the end of the period already paid for. Files on your own machine stay yours — we do not reach into a laptop to disable a copy of anything.

4.5Files already on your machine stay yours. Withdrawal from the catalogue does not reach into a disk to delete a skill or a local server, and neither does the end of a subscription — what stops is the gateway and anything authenticated through it. Whether you may keep using those files is a matter for their licence.

4.6A subscription does not move with a publisher who sets up elsewhere; buyers have to subscribe again wherever that is. When a publisher files a deprecation we tell their buyers they are leaving, rather than quietly cancelling them.

Listings we index rather than publish

Most of the catalogue is software nobody here published. This section says what we take, what we show, what we do not claim, and how whoever the software belongs to can have it changed or removed.

5.1Two kinds of entry sit in this catalogue. A published listing is one whose publisher opened an account here and accepted these terms. An indexed entry is assembled automatically from public sources — the official Model Context Protocol registry, npm, PyPI, container registries, public code repositories, and public directories and lists of MCP servers and agent skills — and nobody behind it has agreed to anything. An indexed entry is marked not claimed on its page.

5.2An indexed entry shows information made public at its source: the name, the author’s public handle, a description, the version, the source address, the licence as the source states it, and the tools and their descriptions as the manifest or registry declares them. Where an indexed server’s install command points at the author’s own package, repository or image, the software reaches you from the author’s source, under the author’s licence, on a request we are not party to. However an indexed entry reaches you, your right to use it comes from its author’s licence and not from us (5.10).

5.3An indexed entry is not an endorsement, a partnership or a claim of affiliation in either direction. Names, logos and marks belong to whoever owns them and are used here only to identify the software they name. A page at mcprush.com/handle gathers the indexed entries published under that public handle: it is an index of public work, not a page its owner runs or has approved.

5.4If it is yours, you have three options and you do not have to justify choosing any of them. Claim it — prove control of the source and accept these terms, and the entry becomes a published listing, with the account and its figures yours and 11.4 applying from then. Correct it — tell us what is wrong and we correct what we can verify. Remove it — we take it out of the catalogue. Claiming starts from the button on the entry. For a correction or a removal, write to support@mcprush.com with the address of the entry; we may ask for reasonable confirmation that it is yours, such as a reply from an address in its repository. We aim to act on a removal within 5 working days, and we do not ask for a reason.

5.5Anyone, whether or not an entry is theirs, can tell us that it infringes a copyright, a trade mark or another right, or is otherwise unlawful. Section 16 sets out how, and what happens next. Removing something on request is not an admission that listing it was unlawful, and we may show that an entry was removed, without naming who asked.

5.6A trust grade on an indexed entry is the output of an automated scan of public source code under a published methodology, as the code stood on the date of the scan. It is an opinion about a snapshot of code against stated rules — not a certification, and not a statement of fact about a person, a company or their competence — and it can be wrong about a moving target. Whoever the code belongs to may ask for a rescan or appeal the grade — from the studio once the entry is claimed, or by writing to support@mcprush.com — and the grade is replaced by whatever the rescan finds.

5.7We give no warranty of any kind on indexed software and we are not a party to its licence: what anyone installs is governed by the licence the author published with it, between the two of them. To the extent the law allows, we are not liable for indexed software or for anything that follows from installing or running it. Sections 13 and 14 apply to an indexed entry as they do to everything else on this site.

5.8An indexed entry is not offered for sale here, and nothing is earned or paid out on it in anybody’s name: the publisher account behind it has no owner and no connected account (9.1, 9.6). Once claimed, it is a published listing (5.4), and any price on it is the one its publisher sets (3.1, 7.1). The author of an indexed entry is not a party to anything bought here.

5.9Text on an indexed page is taken from the public sources in 5.1 or written by us. We may shorten, reformat or machine-translate it into English, and some of it — summaries, categories, the scan’s findings — is written or composed by us, sometimes with the help of AI tools. None of it is written in the author’s voice, and any of it may be incomplete, inaccurate or out of date: check the source before you rely on it.

5.10Your right to use indexed software comes only from its author’s licence, and complying with that licence is yours to do. The licence we show is what we found at the source; it may be missing, misread or out of date, and it is never a licence from us. Check the licence at the source before you install or use the software.

5.11No one is entitled to be indexed, and we have no duty to index anything, to keep an entry, or to check what sits behind it. We may hold back, change or remove any indexed entry at any time, with or without notice — including automatically, where the licence we found forbids redistribution or commercial use.

5.12Being the author of an indexed entry does not by itself make you a party to these terms. The routes in 5.4 and in section 16 are open to you without an account and without accepting anything, and they cost nothing. If you use the marketplace yourself beyond those routes, 1.7 applies to that use as it does to anyone’s.

What a publisher agrees to

6.1The manifest is the promise: every tool declared by name, description and input schema, and each one marked for whether calling it writes anything anywhere. The scan measures what the code can actually reach against what you declared.

6.2No undeclared writes. A tool that can write says so before install, not on first use. A tool declared read-only that writes anything is a policy breach rather than a bug, and it is ground (a) in 10.1.

6.3A change to the tools is a release. A tool added, a tool removed, or a tool whose reach widens — from reading to writing or to the network — is cut as a release in Studio, and the listing shows buyers which tools were added, removed or changed reach. A new tool that writes or reaches the network is refused to every buyer until that buyer accepts it under Dashboard → Changes, unless they chose to accept such changes automatically; holding the change keeps it refused. Tool descriptions are not compared between releases, which is why 6.4 applies to every word of them at every release.

6.4A tool description that instructs the model to do something the tool does not do — read an unrelated file, echo an environment variable, ignore a prior instruction — is refused. That refusal is not appealable, because the same text is what a prompt-injection attack looks like.

6.5A person reads every listing before it goes live. After that, every server whose source is an npm or PyPI package or a GitHub repository is scanned automatically, and again for new versions: injected instructions, hidden characters, hardcoded secrets, supply-chain risk, and what each tool can reach against what it declares. A remote address, a container image and a skill are not scanned. The scan does not hold a listing back, there is no fee for it, and its grade and findings are published on the listing either way.

6.6Every tool declares its reach: it reads, it writes, or it reaches the network — from its own MCP annotations, or from its name where it has none. The gateway refuses a write tool to a key that is read-only, and a buyer’s blast radius is counted from these declarations. There is no egress allowlist: the gateway sees the call and the answer, not what your code does inside its own process, so a reach the declaration does not name is a breach of 6.1 and ground (c) in 10.1, not something the gateway blocks for you.

6.7A support contact a person answers, and a stated response window. “Best effort” is a valid window. Silence is not.

6.8A price change applies to new subscriptions only. A subscription already running keeps the price it was bought at for as long as it runs: a rise never reaches it, and neither does a cut.

6.9Your endpoint’s health is measured on real calls, not on a schedule. Three failures in a row — no answer, an answer of 500 or above, or a refusal of our token — hold calls to it for 60 seconds, and the first answer below 500 after that clears it; failures that come only from one buyer’s own calls do not trip it. A call that fails, times out or is held is never billed and never counts against the buyer’s allowance (7.8). A subscription keeps billing unless you are down for more than 24 hours in a calendar month, in which case we may credit the month to the buyer and deduct the credit from your next payout (9.9).

6.10You warrant, for everything you publish here or ask us to host: that you own it or hold every right needed to publish, license and sell it here, including under the licences of its dependencies; that the licence you state is the one that applies to it; that it contains no malware and does nothing its manifest does not declare; that its name, mark or tagline does not read as an official integration you do not own; that where it handles personal data it does so lawfully, with you answering for that data in your own right; and that what you tell us and your buyers is true.

6.11A listing belongs to the publishing account, not to the person who typed it. When someone leaves a team, nothing is withdrawn from a buyer because the author left.

6.12You authorise us to present, distribute and deliver your listing through every channel the marketplace offers — this site, the CLI, the API, the catalogue served over MCP, feeds and structured data, search engines and the affiliate programme — and, where you publish files, to deliver them to the buyers who install them. 11.4 is the licence that makes this possible; section 18 covers code you ask us to host.

6.13Your licence to buyers is yours to write, and it must not contradict these terms. Where a listing states no licence of its own, you grant each buying account and its seats a non-exclusive, non-transferable licence to install and use it — for the period paid for on a subscription, and without end on a one-time licence — and nothing more.

6.14Our review before a listing goes live and the scan after it check the listing against these terms and for security. They are not an endorsement, a certification or an edit of what you publish, and they do not move any responsibility for it from you to us.

6.15Keep your publisher name and support contact current in the studio, and the details Stripe holds for your connected account current with Stripe. Where the law requires us to identify the maker or seller of software sold here — to a buyer, a court or an authority — we may give them the details we or Stripe hold.

Money

Two prices exist here: the publisher’s, which a buyer pays, and ours, which a publisher pays. Nothing is added to the first to fund the second.

7.1The price is the publisher’s, and a buyer pays it at cost. Each subscription is billed by Stripe on an invoice of its own on the account’s billing day: the first one carries the rest of the cycle it started in and the month ahead, and every later one the month ahead. A subscription that starts with a trial is first billed on the day the trial ends (7.15). A one-time purchase is charged when it is bought, and its document is Stripe’s: an invoice of its own, or Stripe’s receipt in the rare case it is charged as a single payment. A purchase paid from the balance (7.11) is a line on the balance, and the top-up that paid it carries Stripe’s receipt. Every invoice is raised by Stripe; none is drawn by us. A card and a billing address are entered on our own pages, into fields Stripe serves in its own frame: no page here has a card field of its own, and nothing sends you to a payment page somewhere else to finish.

7.2The platform fee is 12% of net revenue — gross less refunds and chargebacks. The publisher keeps 88%. There is no listing fee, and a free listing costs nothing at all.

7.3Card processing is Stripe’s 2.9% + 30¢ per charge, and it goes to Stripe rather than to us. Of a dollar billed, 88 cents is the publisher’s before processing and 85.1 cents lands. A one-time licence is its own charge, so it carries the 30¢ as well. Stripe charges $15 on a disputed charge, at the moment the buyer’s bank opens the case and whether it is later won or lost. The same fee falls on a debit from a US bank account, which is disputed at the account holder’s own bank rather than at a card scheme: the holder of a personal account has up to 60 calendar days from the statement to do it, so a bank debit stays reversible for considerably longer than a card payment. It is charged on the account the payment was taken on, which is ours, and passed to the publisher of the disputed listing on the next run; that sits on the same side of the ledger as the processing fee.

7.4Buyers pay $0 for the marketplace itself: the catalogue, the gateway, the automatic scan of every package and repository source (6.5) and the whole trust layer are funded by the 12%. Pro is $9 a month with three seats in it, then $3 for each seat past them, prorated to the day in both directions.

7.5Prices are in USD and exclude VAT, GST and US sales tax. Where we are registered for them, or the law otherwise requires us to charge them, we add them at checkout and remit them as merchant of record. A publisher’s payout is already net of them, and a publisher invoices nobody.

7.6A subscription is fully refundable within 14 days of a first charge, and prorated in both directions after that. The full refund is available once for each account and listing: a listing bought again after a refund is refunded for the unused part of the period only. A refund goes back the way the money came: to the original card, within five working days, or to the bank account a debit was taken from, which the banks take longer over than a card does. If you are a consumer, this is in addition to any right of withdrawal or refund the law gives you.

7.7We return our 12% on a refund, so a refund costs the publisher their 88% of the sale rather than all of it. That 88% is of gross: Stripe keeps its processing fee when a charge is reversed, and it was deducted from the publisher’s side when the charge was made (7.3), so it is not recovered by anybody. A refunded sale therefore costs the publisher the fee they had already paid on it, and costs us the 12% we had already earned.

7.8Failed calls, timeouts and anything the gateway rejects are never billed. A cached repeat inside 15 minutes is free.

7.9A cycle that owes less than $1 is not charged: the balance carries into the next invoice and appears on it as a separate line. Stripe’s 30¢ makes a charge under a dollar cost more to collect than it yields, and collecting it anyway would take the difference out of the publisher’s share. Nothing expires while it waits.

7.10An unpaid invoice is retried three times over 14 days. After that the account’s installs stop until it is settled. You hear from us before that happens, every time.

7.11A buying account may hold a balance: money paid to us in advance through Stripe, and any credit we add to it. It is spent at checkout: when the balance covers the whole amount a purchase charges that day, tax included, the buyer may pay it from the balance instead of the card. It is not applied to part of a purchase, and it is not applied to subscriptions — their first charge and every renewal are charged to the card or bank account on file. A balance is not a deposit and buys nothing by itself: it does not expire, is not forfeited on cancellation, and earns no interest. Money paid in as a top-up is refundable in full to the card or bank account it came from for as long as the account exists; credit we add — a referral share (7.12) or a credit from us — is spent the same way but is not refundable. It is money we hold and not revenue we have earned, and a top-up is charged at face value: no fee is taken from it on the way in.

7.12A referral pays a share of the platform fee we actually collect from the account introduced — 20% of our 12%, for twelve months from that account’s first settled payment — and pays nothing at any earlier moment. A sign-up, a click, a free install and a trial that never converts are all worth nothing. Each accrual is held for 30 days against the refund and chargeback window; money returned to the buyer takes the share with it. A referral is attached to an account only within one day of that account being opened. A referrer earns nothing on an account they control, on a listing that charges nothing, or where the account was reached by bidding on our name. We treat an account as the referrer’s own when the two share a mailbox, a card or bank account, a workspace, a publisher or a payout account, or have been used from the same network address; a shared company email domain counts only together with a shared network address. A share held against such an account is withdrawn; a share already paid is not reclaimed on this ground. A buyer’s cleared share is added to their balance as credit once their cleared shares together reach the minimum the referral panel shows, and is spent the way the balance is (7.11) but is not refundable; a publisher’s cleared share is recorded as owed to them and shown in their referral panel, and is paid out once the payout run can carry referral shares — until then nothing is transferred. We may close the programme to new referrals at any time; what has already been earned is still paid.

7.13Pro may be tried for seven days without a card, once per account. Nothing is charged during it and it ends by itself — the account returns to Free rather than to an invoice. Enterprise is not a published price: its limits, its terms and its billing are the contract signed with that account, and where that contract and this page disagree, the contract governs for that account alone.

7.14An order may be paid by US bank debit instead of a card. A debit is not instant: it takes about four business days to clear, nothing is installed until it does, and if it is returned — for want of funds, or an account that has been closed — the order says so and nothing is taken. It stays reversible longer than a card, too: the holder of a personal account has up to 60 calendar days from the statement to dispute one at their own bank (7.3, 9.2). A card is charged and installed in the same minute, and is the right choice for anything that cannot wait.

7.15A paid listing may carry a free trial of its own, and it is the publisher’s rather than ours: the number of days is set on the listing, and the listing, the checkout and the receipt each say when it ends. Taking one needs a payment method already on the account — an order carrying a trial is refused where there is none — and nothing is charged while it runs. On the day after the last free one the subscription begins, at the price the listing named. Cancel inside the trial and no invoice is ever raised. A trial is offered on subscription listings only, only where the listing is not already installed on the account, and once per account and listing: removing the install and taking it again does not start a second one. The trial in 7.13 is a different thing, and that one is ours.

7.16A subscription renews at the end of each period, at the price it was bought at (6.8), until it is cancelled. You can cancel it at any time from your account; it then stops at the end of the period already paid for, subject to 7.6.

7.17Our own prices — Pro, seats, the platform fee — can change. A new Pro or seat price applies to new subscriptions; one already running keeps its price unless we tell you at least 30 days before the billing period in which it changes. A change to the split in 7.2 is a material change under 15.4.

7.18Where a price shown is plainly wrong, we may cancel the order and refund what was paid rather than supply at that price. We may also refuse or cancel an order that looks fraudulent, that breaches these terms, or that sanctions or other law forbid, and refund whatever it took.

7.19If you dispute a charge with your bank, we may pause what that charge paid for until the dispute is resolved. A dispute decided in your favour is treated like a refund; one decided against you leaves the charge standing.

7.20If you are a consumer in the European Union or the United Kingdom, you may withdraw from a purchase within 14 days of it without giving a reason, by telling us at support@mcprush.com; any clear statement is enough. We then refund what you paid for it, by the means you paid, within 14 days of hearing from you, and what it paid for stops. This is in addition to 7.6.

The cap

8.1Every subscription plan carries a monthly call allowance and a rate limit, both stated on the listing before purchase. Exhausting the allowance refuses further calls for the period; it never produces a charge above the subscription.

8.2The cap is enforced at the gateway, before the publisher’s code runs. A call over the cap is refused and returns a normal MCP error the agent can reason about, rather than a silence or a bigger bill.

8.3A refused call is not billed. Not to the buyer, and not counted as revenue to the publisher. Nothing accrues above the cap to be collected later.

8.4Raising a cap takes effect on the next call and never retroactively. Calls refused while the cap was lower stay refused and stay unbilled.

8.5There is an alert at 80% of a cap. It is a courtesy. What stops the spend is the cap.

8.6Caps can be set per server, per stack or per team. Where two apply to one call, the lower one decides.

Payouts

9.1Payouts run through Stripe Connect. Every Friday we transfer a publisher’s share for every sale that has cleared by then — a charge clears seven days after it is taken into their own connected account, and Stripe pays it out from there to the bank account it holds for them. The account is opened on Stripe’s own onboarding pages, which the studio sends you to and brings you back from, and keeping it in good standing with Stripe is a condition of being paid — and of listing anything priced, since a publisher without one can publish free listings and nothing else.

9.2A refund, a chargeback or a bank debit returned after it settled is netted off the next run rather than clawed back out of a publisher’s bank account, which we could not reach in any case: we hold no bank details for anybody. What is netted is the 88% of gross, not the 85.1% that landed — Stripe keeps its processing fee on a reversed charge, and its $15 dispute fee (7.3) is netted whether the case is won or lost. Both sit on the same side of the ledger as the processing fee itself. A debit returned inside the 60 days a personal account has to dispute one is netted the same way, on the run after it comes back.

9.3A new publisher holds 10% of each payout for the first 60 days after their first sale, against refunds and chargebacks. It is released in full with the first payout after that.

9.4We may raise a self-billed invoice on the publisher’s behalf for each settlement, so the books carry one document per payout. Where the law requires an information return on a publisher’s sales — a 1099-K in the United States, or its equivalent elsewhere — we file it, or Stripe files it for us, and it is delivered to the connected account.

9.5Being paid needs a valid tax form — a W-9, a W-8BEN or a W-8BEN-E — collected by Stripe during Connect onboarding and held there with the bank details and the identity documents. No copy of any of the three reaches us: what we hold is the connected account id and its payout status. Where the law requires tax to be withheld — for example backup withholding when a TIN stops matching the records it is checked against — it is withheld for as long as that requirement lasts. Where Stripe suspends payouts on an account, we cannot pay it, and the balance is held rather than routed around them.

9.6A publisher account with no owner cannot be paid. Until ownership is transferred the balance is held rather than paid to a guess.

9.7Money owed on a listing frozen under section 10 is held for the length of the freeze and paid on the first run after it clears. A freeze is not a forfeiture, and we do not keep the 12% on a sale we later unwind.

9.8Payment processing services for publishers on mcprush are provided by Stripe and are subject to the Stripe Connected Account Agreement, which includes the Stripe Terms of Service (together, the “Stripe Services Agreement”). By agreeing to these terms or continuing to operate as a publisher on mcprush, you agree to be bound by the Stripe Services Agreement, as Stripe may modify it from time to time; it is between you and Stripe, and how Stripe handles your data is set out in the Stripe Privacy Policy. As a condition of mcprush enabling payment processing services through Stripe, you agree to provide us accurate and complete information about you and your business, and you authorise us to share it, and transaction information related to your use of the payment processing services provided by Stripe, with Stripe.

9.9We may deduct from what we owe a publisher anything the publisher owes us under these terms — refunds and disputes (9.2), a credit under 6.9, and amounts due under 14.4 — and may hold a listing’s balance while a freeze under section 10 or a notice under section 16 about that listing is open (9.7).

9.10Tax on a publisher’s own income from the marketplace is the publisher’s to report and pay. Nothing here, and nothing in the studio, is tax advice.

Freezing, suspension and removal

Section 4 is a publisher choosing to go. This one is us taking a listing or an account down, which is the harder half to write and the half worth reading.

10.1Grounds. We may freeze, limit or remove a listing for any of:

(a)a capability or a write the manifest does not declare;

(b)a tool description that instructs the model beyond what the tool does;

(c)network reach the tool’s declaration does not name (6.6);

(d)a live credential in the repository, until the key is rotated and the old one is dead;

(e)a name or mark that reads as an official integration the publisher does not own;

(f)a plan allowance so small that the listing cannot be used inside it;

(g)a skill that tries to override the client’s system prompt, disable a safety behaviour, or hide what the agent is doing;

(h)fraud, or manufacturing the downloads, readership or call volume that ranking is built on;

(i)a legal demand we are obliged to act on, which we tell the publisher about unless we are forbidden to;

(j)a notice under section 16 that we find credible, or a licence that does not permit what the listing does with the software;

(k)a security risk to buyers, to us or to anyone else;

(l)a breach of the warranties in 6.10 or of section 17;

(m)anything else that, in our reasonable judgement, would expose buyers, us or others to legal liability or serious harm if the listing stayed as it is.

10.2A report does not freeze a listing by itself. Where a report of a security issue or of an infringement looks credible, we may freeze the listing while it is read. The freeze is a holding action rather than a finding, and it is not published as one.

10.3Freezing or removing a published listing is decided by a person, not by the scanner. Two things happen automatically: the scan’s grade and findings (6.5), and holding back an indexed entry whose stated licence matches a rule against redistribution or commercial use (5.11); either can be put to a person under 5.4, 5.6 or 10.7. A decision is written to the publisher, says what it turns on — the file, the line, the call, the notice or the clause — and what would clear it, unless the law or a security risk forbids us to say.

10.4We aim to decide on a frozen listing within one working day of the freeze. A freeze does not lift by itself: if you have heard nothing, ask, and the question goes to the person deciding.

10.5A freeze stops new installs and holds every call to the listing and every download of its files, including for buyers who already have it. Their configuration is kept, and invoices for it are not collected while the freeze lasts. Every buyer who has it is told why as soon as we can, in plain words rather than on a status page.

10.6Removal ends new installs and ends the agreement for that listing. Buyers who paid for it are refunded the unused part of the period, and they are told that we removed it — not that the publisher left. Those are different events and we do not blur them.

10.7Appeal by replying to the decision. It is read again — where we can, by someone who did not make it — and we aim to answer within two working days. The refusal in 6.4 is the one thing that cannot be appealed. Where we were wrong we say so wherever the freeze was visible, and the listing’s ranking is put back where it stood. An appeal does not stop you going to court (15.2) or to arbitration under 15.3.

10.8An account, as opposed to a listing, is suspended only for non-payment (7.10), for fraud, for a breach of section 17, for repeated infringement (16.8), for a security risk the account presents to others, where the law, a court, an authority or sanctions require it, or for repeating a breach after a written decision. We do not suspend an account to win an argument about a clause.

10.9If we are the ones stopping: we may close the marketplace, or drop a whole category, on 90 days’ notice to everyone it affects. Payouts run to the end of that period, buyers are refunded the unused part of anything prepaid, and nobody has to sign anything to get either.

10.10We may end our agreement with a publisher on 30 days’ written notice with our reasons. We may end it at once where the law, an authority or sanctions require it, for fraud, for a repeated breach, or for a security risk, and we give our reasons unless the law forbids it.

10.11You may stop at any time: deprecate or unpublish a listing (section 4) and close the account (2.4). What we owe you is paid on the normal schedule, subject to 9.2, 9.3 and 9.9.

10.12Whatever ends, what was owed before it ended is still owed, and the clauses that by their nature outlast an agreement — 11.4 for what is already delivered, and sections 13, 14 and 15 — survive it.

Reviews, ranking and what you write

11.1The reviewer owns their words; the listing carries the score. A publisher cannot delete a review and cannot pay to have one removed. We remove one only for personal data, for abuse, where it is plainly about a different product, where it breaches section 17 or is not genuine, where we reasonably believe it is unlawful, or where the law or a valid notice under section 16 requires it.

11.2One public reply per review. Transfer a listing and the reviews go with it; delist it and they go dark with it.

11.3The catalogue’s default order is by the number of downloads a package had in the last day at the registry it is published on — npm, PyPI, Docker Hub or GitHub releases — where we have that figure; then by how many separate readers opened the listing page over the preceding 30 days, counted once per reader per day, with the publisher’s own team and any client identifying itself as a robot excluded, and with the current day left out so that the order does not move while somebody is reading it; then by address. Price does not move a listing up or down, and a reader can choose another order. Manufacturing downloads or readership, by any means, is ground (h) in 10.1.

11.4You keep the copyright in what you put here — a listing, its README and files, a review, a reply. You give us a worldwide, non-exclusive, royalty-free licence to host, store, copy, adapt (format, excerpt, summarise and translate), publish, display, distribute and transmit it, and to let our service providers do so for us: on this site, in the CLI and the API, in the catalogue served over MCP, in feeds, structured data and search results, in material for the affiliate programme, and — for a listing — to deliver what you publish to the buyers who install it. It lasts while the content is on the marketplace, and afterwards only as long as backups and records take to roll off; for a review, and for what buyers already received, it does not end. You confirm you have the rights to give it.

11.5A listing may be placed for payment at the head of the unfiltered catalogue or on the home page. It is labelled Promoted, appears once, and is not pinned once a reader filters or searches. Promotion changes where a listing is shown, never its grade or its reviews.

11.6Any signed-in account other than the listing’s publisher can write one review of a listing, and rewrite it until the publisher replies. Where the account has the listing installed, the review says so and shows how much it has been used; otherwise it does not. We do not check that a reviewer is who they say they are, or that what they write is true.

11.7What you write here is yours to answer for: it must be lawful and yours to publish, and it is not our view because it appears on our site. If you send us an idea or a suggestion, we may use it without owing you anything for it.

Data, and what may be taken from this site

12.1A publisher sees counts, versions, clients and failure codes for their own listing and, for each paid sale and each dispute, the name of the buying account — its organisation or person name, or its email address where it has neither — so that one sale can be told from another. They do not see the arguments a buyer sent or the content that came back.

12.2Taking the catalogue in bulk is a breach of these terms — scraping the pages, automating a browser against them, or collecting the listings, their prices or their publishers by any other means (section 17). A key reaches your own account, and if you want an agent to reach a listing, install it.

12.3We do not sell what the gateway sees, and we do not train anything on the content that passes through it.

12.4What we do with personal data, and on which lawful basis, is described in the privacy notice, which is written to be read rather than survived (1.8). One thing from it belongs here: the site uses Google Analytics, including at checkout and on pages behind a login, where it records the steps of a purchase. Whether we ask before it loads depends on where you are, as the privacy notice explains; either way it can be switched off from Cookies in the footer of every page. Refusing changes nothing about what the account can do.

12.5Where you are a controller in your own right — an organisation whose members use this platform — and need a data processing agreement with us, ask through support. The service providers we use are listed in the privacy notice.

12.6The site, the gateway, the CLI and the API, the scan’s results and grades, the texts we write, and the catalogue as a compilation are ours or our licensors’. You may use them for what the marketplace offers them for, and for nothing else; this right is personal, non-exclusive and ends with these terms. What authors and publishers made stays theirs (5.10, 11.4).

Warranties, other people’s software, and what a scan can promise

13.1We warrant the parts that are ours, and only these. A failed call is never billed (7.8). A cap is enforced before a publisher’s code runs (section 8). A payout is what the ledger says, and the figure on a Friday statement is the figure we transfer to the connected account that day; when Stripe moves it on to a bank is Stripe’s timing rather than a number we produce. Where a number we produced is wrong we correct it and refund or pay the difference, because merchant of record means a wrong number is ours.

13.2A scan is evidence about a build, not a promise about behaviour. It reads source, manifest, dependencies and tool descriptions — which says what a build contains, not what it will do when it runs (6.5). It cannot prove the absence of a bug, it cannot read intent, and it cannot tell you whether a tool that is allowed to write should be trusted with your repository. A good grade is not a guarantee that software is safe; a poor one is not a finding that anyone did wrong.

13.3A grade describes the version it names. A listing that was clean a year ago is not evidence about the release you are installing today, which is why a new version of a scanned source is scanned again rather than inheriting the last result (6.5).

13.4We do not warrant that a listing is fit for your purpose, that it will still be published next month, or that a model driving it will call it sensibly. The first two are the publisher’s; the third is yours.

13.5EXCEPT AS 13.1 EXPRESSLY STATES, AND TO THE FULLEST EXTENT THE LAW ALLOWS, THE MARKETPLACE, THE CATALOGUE, THE GATEWAY, HOSTING, THE CLI AND THE API, SCAN RESULTS AND GRADES, AND EVERY LISTING AND INDEXED ENTRY ARE PROVIDED “AS IS” AND “AS AVAILABLE”, WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND. WE DISCLAIM ALL IMPLIED WARRANTIES AND CONDITIONS, INCLUDING OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY AND QUIET ENJOYMENT, AND ANY WARRANTY ARISING FROM A COURSE OF DEALING OR USAGE OF TRADE. WE DO NOT WARRANT THAT ANY OF IT WILL BE UNINTERRUPTED, SECURE, ERROR-FREE OR FREE OF HARMFUL CODE.

13.6Every listing and every indexed entry is software somebody else wrote. You decide whether to install it, which permissions, keys and data to give it, and where to run it; you are responsible for backups, for isolating what you do not trust, and for complying with its licence. We do not audit the software in the catalogue and we do not undertake to monitor it.

13.7MCP servers and skills act on the instructions of the agent that calls them and with the credentials you give it. What an agent does — and what a model says — can be wrong, incomplete or harmful, and it is not professional, legal, financial, medical or security advice. Review what matters before you rely on it or let it act.

13.8We take reasonable care over the security of what we run, but no system is completely secure, and a scan finds some problems, not all. Where a security incident affects personal data, we notify whoever the law requires us to notify.

13.9There is no service level on any plan except where an Enterprise contract states one. The marketplace, the gateway and hosting can be slow, interrupted or changed — for maintenance, for security, or because something upstream failed — and features marked as a preview may change or go away.

13.10The marketplace relies on services run by others — among them Stripe, GitHub, npm, PyPI, container registries, Google, Cloudflare and our hosting providers — and links to sites we do not control. We are not responsible for them, for their availability, or for what they do with what you give them under their own terms.

13.11If you are a consumer, nothing in this section takes away a right the law gives you that cannot be excluded — for example to digital content that conforms to the contract under EU law or the UK Consumer Rights Act 2015.

Liability and indemnities

14.1To the extent the law allows, neither of us is liable to the other for indirect, incidental, special, consequential, exemplary or punitive loss, or for lost profit, revenue, goodwill or data, the cost of substitute services, the cost of the run that failed, or the hours spent finding out why — even if told it was possible. This does not limit money owed under sections 7 and 9 or the indemnities in 14.4 to 14.6.

14.2To the extent the law allows, and except as 14.3 provides for claims arising from publishing, our total liability to you for all claims together is limited to the greater of (a) what your account paid us, seats included, in the 12 months before the event giving rise to the most recent claim, and (b) US$100.

14.3To the extent the law allows, our total liability to a publisher for all claims arising from publishing is limited to the greater of (a) the fees we charged them in the 12 months before the event giving rise to the most recent claim — our 12%, not their 88% — and (b) US$100. We do not keep a fee for a service we failed to provide, and we do not underwrite their business either. The limits in 14.2 and 14.3 do not add together.

14.4A publisher will defend and indemnify us — and our members, managers, employees and contractors — against any third-party claim, and the losses, damages, fines, settlements and reasonable costs, including lawyers’ fees, that follow from it, arising from: their listing, software, files, name or content infringing or misappropriating anyone’s rights or breaching a licence; something their code did, including outside the capabilities it declared; personal data their software handles; their taxes, or the information they gave for tax and payouts; or their breach of these terms or of the law.

14.5If you use the marketplace for a business, you will defend and indemnify us in the same way against third-party claims arising from your use of the marketplace, or of software obtained through it, in breach of these terms, of a licence or of the law; from content you submit; and from what an agent you run does with a listing. If you are a consumer, this applies only as far as the law where you live allows.

14.6Whoever claims an entry (5.4) or sends a notice or counter-notice (section 16) answers for its truth, and indemnifies us against claims arising from one that was false or made without authority.

14.7Subject to 13.11 and 14.10, and to the extent the law allows, we are not liable for: indexed software, or anything that follows from installing or running it (section 5); software a publisher lists, its behaviour, or the data it handles; a scan’s output, a grade, or the absence of either; what an agent does with a listing; a service run by someone else (13.10); or events outside our reasonable control (15.11).

14.8Under an indemnity, we tell the indemnifying party about the claim promptly — a delay relieves them only to the extent it prejudices them — let them control its defence with counsel we reasonably accept, and cooperate at their expense. They may not settle a claim in a way that admits fault for us or binds us to do anything without our written consent.

14.9To the extent the law allows, a claim under these terms must be brought within one year after the facts it rests on were known or could reasonably have been known; after that it is barred.

14.10Nothing in these terms excludes or limits liability that cannot be excluded or limited by law — for fraud or fraudulent misrepresentation, for death or personal injury caused by negligence, for gross negligence or wilful misconduct where the law does not allow it, under product liability law, or a consumer’s statutory rights. Where the law limits how far a clause may go, it goes that far and no further. Rights you have by statute stay yours.

14.11Your contract is with the operator of mcprush.com alone. To the extent the law allows, you will bring any claim about the marketplace against the operator, and not personally against its owners, members, managers, employees or contractors, who may rely on this clause and on the limits in this section.

Disputes, law, changes and contact

15.1Raise it with us first, from the account it concerns or at support@mcprush.com, and give us 30 days to put it right before you start a claim. We aim to answer billing and refunds in one working day, a listing frozen by a report in one, account and access in two. Payout questions are read by the people who run the settlement rather than by a first line that forwards them. The period in 14.9 is paused while those 30 days run, and nothing in this clause prevents either of us from asking a court for urgent injunctive relief.

15.2These terms are governed by the laws of the State of Florida, without regard to its conflict-of-laws rules, and by the federal law of the United States, including the Federal Arbitration Act. Subject to 15.3, the state and federal courts sitting in Miami-Dade County, Florida have exclusive jurisdiction. If you are a consumer in the European Union, the United Kingdom or Switzerland, you keep the protection of the mandatory law of the country where you live, you may bring proceedings in its courts, and we will bring proceedings against you only in those courts.

15.3ARBITRATION AND CLASS-ACTION WAIVER (UNITED STATES). If you reside in the United States — or, for an organisation, have your principal place of business there — any dispute between us arising out of or relating to these terms or the marketplace is resolved by binding individual arbitration, not in court. The arbitration is administered by the American Arbitration Association under its Consumer Arbitration Rules if you are an individual acting for personal purposes, and under its Commercial Arbitration Rules otherwise. For a consumer claim we pay the AAA filing, administration and arbitrator fees beyond what the Consumer Arbitration Rules require of you, and any hearing is held by video or in the county where you live. Either of us may instead bring an individual claim in a small-claims court, or ask a court for an injunction against the infringement or misuse of intellectual property or of the service. Claims are brought and decided individually, not as a plaintiff or class member in any class, collective or representative proceeding; except as the AAA’s Mass Arbitration Supplementary Rules provide for administering many similar cases, no arbitrator may award class or representative relief. A claim for public injunctive relief, where the law does not allow it to be waived, is decided by a court after the individual arbitration ends. If the class-action waiver is found unenforceable for a claim, that claim goes to court, not to arbitration. You may opt out of this clause by writing to support@mcprush.com from your account email with the words “arbitration opt-out” within 30 days after you first accept it. This clause does not apply to a claim already filed, or to a dispute of which either of us had notice, before you accepted it, and it does not apply to consumers in the EU, the UK or Switzerland.

15.4A material change — the split in 7.2, the schedule in 9.1, what the cap does in section 8, the grounds in 10.1, any new obligation, ground for removal, set-off or restriction on you, or anything in sections 13, 14 and 15 that narrows your rights — is announced, with the reason for it, at least 30 days before it takes effect, by email to every account it affects or by a prominent notice in the account or on this site; for an account opened after the change is published, it applies from then. For a publisher, any other change to these terms is also notified at least 15 days before it takes effect, and a publisher is always told of a change by email. If you do not accept a change, you may close the account, or as a publisher end our agreement, before it takes effect; using the marketplace after that date is acceptance. A change the law requires, or one needed to deal with a security risk or fraud, may take effect sooner. Otherwise — a clearer sentence, a corrected typo — a change takes effect when it is published, or for a publisher 15 days after we notify it.

15.5The date at the head of this page is the date these terms took effect; a change is published here with the date it takes effect. We send a copy of the terms you accepted on request.

15.6If a clause turns out to be unenforceable, the rest stand, and that one is read as narrowly as it takes to make it work.

15.7We may transfer these terms to whoever takes over the business or the marketplace, and we will say so before it happens; your rights under them go with it. You may not transfer yours without asking us.

15.8Not enforcing a clause once does not waive it.

15.9A question about a clause goes to support@mcprush.com. A notice of infringement goes as section 16 says. Anything about an account, an invoice or a listing goes through the account it concerns, where it reaches somebody who can already see it. A formal notice to us is given by email to support@mcprush.com with “Legal notice” in the subject line. We do not take notices by post. That email address is also our single point of contact for users and for authorities under the EU Digital Services Act. We deal with messages in English.

15.10These terms and the documents named in 1.8 are the whole agreement between us about the marketplace, and replace anything said or written before. Where they conflict, an Enterprise contract comes first for its account, then these terms, then the rest; the licence on a listing governs the software itself (3.5).

15.11Neither of us is responsible for a failure or delay caused by something outside reasonable control — an outage at a provider we depend on, an attack, a natural disaster, war, a government act, a strike — for as long as it lasts. This does not excuse a payment already due.

15.12You agree to receive notices from us electronically — by email to the address on the account, or in the account itself — and they count as “in writing”. A notice to us is given when it reaches the email address in 15.9.

15.13Nobody other than you and us has rights under these terms, except the people 14.4 to 14.6 and 14.11 protect. The author of an indexed entry gains no rights under them by being its author (5.12).

15.14These terms are written in English, and the English text governs any translation of them.

Copyright, trade-mark and other notices

How to tell us that something here infringes your rights or is otherwise unlawful, what we do with the notice, and how the person it concerns can answer it. This is our policy under the US Digital Millennium Copyright Act (17 U.S.C. §512) and our notice-and-action mechanism under the EU Digital Services Act (Article 16).

16.1Anyone may send a notice, with or without an account, about anything on the marketplace: a published listing, an indexed entry, a file we deliver, a review, a page. You do not need to be the author of an indexed entry to report it, but for copyright or a trade mark you must own the right or be authorised to act for whoever does.

16.2Send it to our agent for notices of claimed infringement — the Copyright Agent, mcprush.com — by email to support@mcprush.com with “Legal notice” in the subject line. We do not take notices by post. Put the statements in 16.3(e) and (f) in the message and sign it; in an email, typing your full name at the end of it is your signature.

16.3A copyright notice under US law must contain:

(a)the physical or electronic signature of the owner of the right, or of a person authorised to act for them;

(b)identification of the copyrighted work, or, for several works, a representative list of them;

(c)identification of the material said to infringe and enough to find it — the address of the listing or entry, and the file or text concerned;

(d)your name, postal address, telephone number and email address;

(e)a statement that you believe in good faith that the use is not authorised by the owner, its agent or the law;

(f)a statement that the information in the notice is accurate and, under penalty of perjury, that you are the owner or authorised to act for the owner.

16.4Any other notice — a copyright notice under another law, a trade mark, another right, or content you consider illegal under the law of an EU member state or elsewhere — should contain: an explanation of why you consider it infringing or illegal, with the right relied on and, for a trade mark, the registration and where it is registered; the exact address of the material; your name and email address; and a statement that you believe in good faith that the notice is accurate and complete.

16.5We confirm receipt, read the notice, and decide on it with care and without undue delay; a notice that is incomplete may be one we cannot act on until it is completed. Where a notice is valid, we remove or disable access to the material expeditiously. An indexed entry is taken out of the catalogue. For a published listing we may freeze or remove it, or the part concerned, and we send the publisher the notice and a statement of our reasons, including the name and contact details the notice gave. We tell the sender what we decided and how it can be challenged, and whether any part of the decision was made by automated means.

16.6A publisher whose material was removed under US copyright law may send a counter-notice to the same agent. It must contain: their physical or electronic signature; identification of the material and where it appeared before it was removed; a statement under penalty of perjury that they believe in good faith it was removed by mistake or misidentification; and their name, address and telephone number, with consent to the jurisdiction of the federal district court for the district where that address is — or, outside the United States, any district in which we may be found — and agreement to accept service of process from whoever sent the notice.

16.7We forward a valid counter-notice to whoever sent the notice. Unless they tell us, within 10 business days, that they have filed a court action to restrain the infringement, we restore the material, or stop disabling access to it, between 10 and 14 business days after the counter-notice arrived. An indexed entry has no counter-notice, because nobody here published it; its author can use 5.4 instead.

16.8We terminate, in appropriate circumstances, the accounts of users who repeatedly infringe.

16.9Someone who knowingly and materially misrepresents that material infringes, or that it was removed by mistake, may be liable for the damages that causes (17 U.S.C. §512(f)), and answers to us under 14.6. We may stop acting on notices from anyone who frequently sends ones that are plainly unfounded.

16.10We have no general obligation to monitor what is on the marketplace or to look for infringement. Removing something on a notice is not an admission that it infringed, and we may say publicly that material was removed following a notice.

16.11If you disagree with a decision we made on a notice, reply to it: it is read again under 10.7. Nothing here stops the sender or the publisher going to court, or to arbitration under 15.3.

What nobody may do here

17.1You may not use the marketplace, the gateway, hosting, the CLI or the API — or try — to:

(a)break the law or infringe anyone’s rights, including by publishing, claiming or distributing software or content you have no right to;

(b)publish, deliver or hide malware, undeclared behaviour, or instructions meant to subvert an agent (6.4, 10.1(g));

(c)take the catalogue in bulk (12.2), or use it — beyond the access the CLI, the API and the catalogue MCP server give you for your own use — to build or populate another directory or dataset, or to train a model;

(d)exceed or get around a rate limit, a cap, an allowance or metering — including by sharing keys, opening extra accounts or rotating identities;

(e)probe, scan, load-test or attack the service, or bypass its authentication, the gateway or its controls — except good-faith security research that stops at the minimum needed to show an issue and is reported to us promptly at support@mcprush.com;

(f)decompile, reverse-engineer or copy the gateway, the CLI or hosting, or derive their source, except where the law expressly allows it notwithstanding this clause;

(g)resell, rent or share access, keys or seats outside your own account (3.3);

(h)impersonate a person or a company, claim an entry you do not control, or suggest an affiliation that does not exist;

(i)manipulate reviews, ratings, downloads, readership or referrals (7.12, 10.1(h));

(j)use a listing or the gateway against anyone else — spam, fraud, unauthorised access, or collecting data about people without a lawful basis;

(k)breach sanctions or export control law;

(l)interfere with anyone else’s use of the marketplace.

17.2We may investigate a suspected breach, remove what it concerns, act under section 10, and report it to the authorities where we think that right or the law requires it.

17.3Automated tools — the scan in 6.5 and the licence matching in 5.11 — find some of this, not all of it. They are not a complete check, and their silence is not approval.

Hosting a publisher’s code

Only for a publisher who asks us to run a published listing.

18.1Hosting builds an image from the source you point us to and runs it on demand, one task per install, on infrastructure we rent from a cloud provider in the United States. A task that receives no calls is stopped after about 15 minutes and started again on the next call. There are ceilings on how many tasks run at once, per publisher and in total, and on builds. Storage inside a task does not survive it: whatever your server writes next to itself is lost when the task stops, restarts or is replaced by a new release.

18.2You give us, and the providers we use for it, the right to copy, build, store and run your code and its dependencies for as long as hosting it takes, and you warrant under 6.10 that you may. The code, what it does, the licences it carries and the data it handles remain yours to answer for; we are not its author or its operator in any sense beyond keeping it running.

18.3Secrets that buyers or you provide for a hosted server are stored encrypted with the cloud provider and handed to the task when it starts. What your server prints to its own output is kept in the provider’s logs for 7 days and can contain whatever your code chose to print; do not print secrets or personal data.

18.4We may refuse a build, stop a task, roll back to an earlier image or suspend hosting — for security, for a breach of these terms, for abuse, for a legal reason, or where a server runs up cost out of proportion to its use. There is no service level for hosting (13.9).

18.5When a hosted listing is unpublished or removed, or hosting ends, its tasks stop receiving calls and are stopped when they next go idle. Keep your own copy of your source: hosting is not a backup.