mcp-tool

Legal

Terms of service

For everything sold at mcp-tool.com. Revised 2026-09-09.

The short version

You buy a package with a written scope and a fixed price. The clock starts when we have what the scope names. You own the code when it is paid for. We get your server to meet the directories' published requirements and fix one round of reviewer feedback; whether Anthropic or OpenAI list it is their decision, not ours, and not guaranteed. Care runs month to month. Our liability is capped at what you paid us in the last twelve months. Florida law, English text.

§ 1Parties and scope

These terms are between FINAL MASTER LLC, 7901 4th St N Ste 300, St. Petersburg, FL 33702, USA (“we”), and the company that orders a package at mcp-tool.com or by email (“you”). The services are for businesses and professionals; they are not offered to consumers.

§ 2The packages

Listing Sprint ($1,900): an existing MCP server or API is audited against the published submission criteria of the Claude Connectors Directory and ChatGPT Apps, the findings are fixed in code, the documents and assets a listing needs are produced, and we accompany you through the submission. Delivery target: 5 business days from the start date.

Build ($4,900): an MCP server with up to eight tools over one API or one website, on the current Streamable HTTP transport, with OAuth 2.0 where the directories require it, deployed to a staging URL, monitored for 30 days, handed over as a repository, plus everything in the Listing Sprint. Delivery target: 10 business days from the start date.

Care ($390 per month, cancel monthly): hosting, monitoring, protocol updates, re-submission after changes, and up to two hours of changes per month for one MCP server.

The exact scope of a Listing Sprint or Build is written down at the kickoff and confirmed by email. Work outside it is quoted in writing before it starts. Delivery targets are targets in business days; they move by the number of days we wait for something named in § 4.

§ 3Ordering and start date

An order is placed by paying through the checkout on mcp-tool.com or by confirming a written quote. The start date is the later of the kickoff call and the day we receive everything named in § 4. Before the start date you may cancel and receive the payment back in full, less payment processing fees.

§ 4What you provide

Documentation of the API or product, a test account with representative data and credentials, answers to our questions within one business day, your privacy policy or the person who approves one, and, for the submission, the person who owns your Claude Team or Enterprise organisation or your OpenAI platform account. You confirm that you are entitled to have a server built over the API and data you provide.

§ 5Payment

Listing Sprint and Care are paid in full when ordered. Build is paid 50% when ordered and 50% when the server is on the staging URL and submitted, invoiced with seven days to pay. Prices are in US dollars and exclude any tax you owe in your country. Card payments run through Stripe; bank transfer on request. Care renews monthly on the day of the first payment until cancelled.

§ 6Directory review

Listings in the Claude Connectors Directory and in ChatGPT Apps are granted by Anthropic and OpenAI under their own rules, from your own account, and we have no influence over their decision or their timing. We undertake that the server meets every requirement those companies have published on the day it is submitted, and that one round of reviewer feedback is fixed within the package at no charge. Further rounds, or requirements published after submission, are quoted separately. A refusal by a directory is not a defect in our work and does not entitle you to a refund.

§ 7Acceptance

A Listing Sprint is delivered when the audit, the fixes and the documents have been handed over and the submission has been made. A Build is delivered when the server on the staging URL performs the tools named in the written scope, which you have five business days to verify. Defects reported in that time are fixed without charge; silence counts as acceptance.

§ 8Ownership of the work

On full payment, you own the code we deliver for your project and may use, change and relicense it without limit. We keep ownership of our generic building blocks (transport, authentication, monitoring, deployment scripts) and grant you a perpetual, royalty-free licence to use them within the delivered work. We may name you as a client and describe the project in general terms unless you tell us in writing not to.

§ 9Care

Under Care we host the server in Germany or on your infrastructure, monitor it, apply protocol and dependency updates, and make up to two hours of changes per month; unused hours do not carry over. We aim for the server to be reachable at all times but promise no specific availability. Either side may cancel Care to the end of the current month by email. On cancellation we hand over the deployment and stop the monitors; the repository is yours already.

§ 10Confidentiality

What you give us for a project, and what we learn about your product while doing it, is used for the project only and not disclosed, for as long as it is not public. The same applies to our methods and pricing offered to you. Credentials are deleted 90 days after handover or when Care ends.

§ 11Liability

We are liable for intent and gross negligence without limit. For anything else our liability is limited to the amount you paid us in the twelve months before the event, and excludes lost profit, lost data and indirect loss. We are not liable for the conduct of the directories, of your API, or of AI models that call the server.

§ 12Law and changes

The law of the State of Florida applies, and the courts of Pinellas County, Florida have jurisdiction, without prejudice to mandatory rules of the country where you are established. These terms are written in English. Changes apply to orders placed after the change; a running Care subscription is told 30 days before a change applies to it. Questions: hi@webmcp-tool.com.