Using this website
You may read, link to and quote this site with attribution. Do not try to disrupt, overload or probe the site or the infrastructure that serves it, scrape it in a way that misrepresents it or impersonates us, or use our contact details for spam.
When a client relationship starts
Reading this site, sending the request form, emailing us or booking a call does not create a client relationship. The one thing you can buy on this site is the deposit that reserves a Write-Safety Audit; that purchase is governed by Reserving a Write-Safety Audit online below. Every other engagement (design-partner audits, add-ons, custom scope, fixes, the write-path rebuild, the MCP blueprint, new MCP servers and the advisory offers) starts only when both sides sign a written statement of work. The short terms for the write-path rebuild, a new MCP server, the MCP blueprint, the writecheck readout, the design review and the advisory retainer below say what that statement of work contains.
Audit and build engagements
- Each audit or build engagement is governed by its own written terms, provided with the quote or the scope confirmation. Where they differ from this page, the engagement terms win.
- An audit reports what we tested and what we found, under the conditions documented in the report. It is not a guarantee that a server is secure, correct or free of other defects.
- Prices on this site are fixed per package as described; the price you agree in writing is the price you pay.
Reserving a Write-Safety Audit online
These are the terms of sale when you pay the deposit for a Write-Safety Audit through the checkout link on our packages page. Paying means you accept them.
- What the deposit is. $1,250: 50% of the $2,500 fixed price of one Write-Safety Audit. It reserves your slot. The balance, the other 50%, is invoiced when the report is delivered.
- Scope. One MCP server, local or remote, with up to 40 tools, tested as one test account on one test tenant only, never on production data or production tenants, with the deliverables listed on the packages page. A server behind OAuth sign-in is in the same price; until our sign-in tooling is ready, someone on your side issues us a fresh access token during the test week, as the statement of work sets out. Testing two accounts or tenants against each other is not offered yet. Extra tools: tools 41 to 65 are +$500 (above 65 tools, the audit is quoted); a second server in the same engagement is +$1,750. The scope, including any extra tools or servers, is agreed in writing before testing starts.
- After you pay. We email you within one business day to confirm the server, the tool count, the test-tenant access and the start date. Never send tokens, passwords or keys by email.
- Refunds. You can ask for a full refund at any time before testing starts: email hello@isokron.ai. If the access or details we need are not provided within 14 days of your payment, we refund you in full without being asked. Testing starts on the date we agree with you in writing, and we email you when it does. Once testing has started, the deposit is not refundable; but if we fail to deliver the agreed coverage, the balance is not due.
- Delivery. The report is delivered within 5 business days, counted from the day access is in place.
- Fixes and retest. The price includes fix pull requests, or patches where we have no repository access, for up to five of the highest-severity findings that can be fixed within the server’s existing code, and one free retest within 30 days of the report. Severity is rated against the impact agreed at scoping. Further fixes, and fixes that need a redesign, new tools or changes to other systems, are quoted separately.
- Errors in the report. If the report contains an error, tell us and we correct it free of charge.
- What it is not. The audit reports what we tested and what we found, under the conditions documented in the report. It is not a guarantee that a server is secure, correct or free of other defects.
- Price and taxes. Prices are in US dollars. The deposit is paid at checkout through Stripe; any taxes that apply are shown at checkout before you pay.
The write-path rebuild
Short terms for the write-path rebuild described on our build page. There is no online checkout: it is requested through the contact form or a scoping call, and starts when both sides sign a statement of work.
- What it is. $6,000 in total for one existing or generated MCP server with up to 40 tools: its write paths and tool design rebuilt, fixes for the defects we find, tests for every change, and a before/after agent benchmark on two task sets, reported separately. No blueprint is needed: we confirm the price from the tool list. The scope is agreed in writing before work starts.
- Payment. 50% ($3,000) when the statement of work is signed, to start; the other 50% when the work is delivered. Prices are in US dollars.
- Delivery. About two weeks. The delivery date is agreed in writing before we start. If the work turns out bigger than the agreed scope, we tell you before doing more, and you decide.
- What is out of scope. The rebuild covers code changes inside the server’s own repository. Changes to the backend or API behind the server are quoted separately. So are more than one server, more than 40 tools, and deploying or running the server in production. We work on test tenants only, never on production data or production tenants.
- Benchmark. We report the before/after on both task sets whatever it shows. We do not promise a gain in calls, turns, bytes or cost.
- Warranty. For 60 days after delivery, if the code we delivered does not do what the agreed scope and its tests say, we fix it at no charge. The warranty does not cover code changed by anyone else after delivery, changes in your backend, API, SDK or MCP client after delivery, or new features.
- IP and ownership. The code we write for you is delivered into your repository and belongs to you. IsoKron keeps its own general tools, test harnesses and know-how, which are not part of the deliverable; our open-source tools stay under their own licenses.
- Independence. We test what we build and give you that evidence, but we do not present it as an independent audit.
- Confidentiality. The work is private by default. We sign a reasonable NDA on request, and nothing is published without your written consent.
A new MCP server
Short terms for a new MCP server described on our build page. It starts with the MCP blueprint, and with a statement of work signed by both sides.
- What it is. From $7,500 for one API, one sign-in method and up to 10 tools; larger servers cost more. The price is fixed in the blueprint, and the blueprint’s $1,000 is part of it (see the MCP blueprint).
- Warranty. For 60 days after delivery, if the code we delivered does not do what the agreed scope and its tests say, we fix it at no charge, with the same exclusions as the write-path rebuild’s warranty.
- Payment. The blueprint is paid upfront; how the rest of the price is paid is set out in the statement of work. Prices are in US dollars.
- Everything else. Delivery date, scope changes, IP, independence and confidentiality are as for the write-path rebuild above unless the statement of work says otherwise.
The MCP blueprint
Short terms for the MCP blueprint described on our build page. It is requested through the contact form or a scoping call; there is no online checkout.
- What it is. $1,000 for a written design of one MCP server, new or existing: the tool inventory and schemas, an auth design, a write-safety design, a test plan and a fixed-price build quote with a delivery date. It contains no code changes. It is needed for a new MCP server or larger work, not for the standard write-path rebuild.
- Payment. Paid upfront, in US dollars.
- Part of the build price. If you sign a statement of work for a build or rebuild with us within 60 days of the day we deliver the blueprint, the full $1,000 counts toward its price: it is part of that price, not on top of it. After that window it does not count. It is not paid out in cash.
- What is out of scope. Building or changing the server, and any testing of a live system.
- IP and ownership. The blueprint is yours to keep and use, with us or with anyone else. IsoKron keeps its own general tools and know-how.
- Confidentiality. Private by default; NDA on request.
The writecheck readout
Short terms for the writecheck readout described on our advisory page. It is requested through the contact form; there is no online checkout.
- What it is. $450 for a written reading of every verdict in one mcp-writecheck run on one MCP server, the top three fixes in order, and a 30-minute call. You make the run and send us its output, or we make it on your test tenant with a token scoped to it.
- Part of an audit’s price. If you book a Write-Safety Audit or a design-partner audit with us within 30 days of the day we deliver the readout, the full $450 counts toward its price: it is part of that price, not on top of it. After that window it does not count. It is not paid out in cash.
- What is out of scope. Testing beyond the mcp-writecheck run, a security review, an Evidence Pack and writing fixes. We work on test tenants only, never on production data or production tenants.
- Payment. In US dollars, as set out in the statement of work.
The design review
Short terms for the design review described on our advisory page. It is requested through the contact form; there is no online checkout.
- What it is. $1,500 fixed for a review of one design document, pull request or tool catalog for one MCP server against the 37 requirements of the MCP Write-Safety Requirements, delivered in writing, and a 60-minute call.
- What is out of scope. Testing of any kind, code changes, and a security review. A design review is not an audit.
- Payment. In US dollars, as set out in the statement of work.
The advisory retainer
Short terms for the advisory retainer described on our advisory page. It starts with a request through the contact form; we take at most three retainer clients at a time and reply to say whether a place is open.
- What it is. $2,000 a month for two 60-minute sessions a month, written answers between sessions within one business day, and reviews of your designs and pull requests.
- Term. Month-to-month, with no minimum term. The statement of work sets out how either side ends it.
- What is out of scope. Writing code and running tests: builds and audits are separate offers. We never need production data or production credentials.
- Payment. In US dollars, as set out in the statement of work.
For all three: advice and reviews are our professional opinion of what we were shown, not a guarantee that a server is secure or correct. The work is private by default; we sign a reasonable NDA on request, and nothing is published without your written consent.
Website content and intellectual property
Text, graphics and the IsoKron name and logo on this site belong to Stormhaven Enterprises LLC unless noted otherwise. Research pieces may be quoted with attribution and a link. Third-party names, such as those of the MCP servers we have tested, belong to their owners; their mention does not imply endorsement.
Open-source tools
Our open-source tools are licensed under the license in each repository (Apache-2.0). That license, not this page, sets your rights and our disclaimers for the code.
No warranty; limitation of liability
The website is provided as is. We try to keep it accurate and available but make no warranty that it is complete, current or uninterrupted. To the fullest extent permitted by law, we are not liable for indirect, incidental or consequential damages arising from your use of the website.
Governing law
These terms are governed by the laws of the State of Arizona and of the United States, without regard to conflict-of-law rules. Disputes go to the courts located in Arizona.
Changes
We may update these terms by posting a new version with a new date. Using the site after that date means you accept the update. A statement of work already signed keeps the terms it was signed under.
Changed on 18 November 2026 (the previous version was dated 14 November 2026): short terms for the writecheck readout, the design review and the advisory retainer.
Changed on 14 November 2026 (the previous version was dated 11 November 2026): the blueprint now counts toward a build or rebuild signed within 60 days of delivery (it was one started within 30 days); the audit’s included fixes are up to five of the highest-severity findings (they were every high-severity finding plus up to five others); the audit covers servers behind OAuth sign-in, extra tools are capped at one step and a second server has a price; the rebuild needs no blueprint; and a new MCP server has its own short terms, with a 60-day warranty.
Contact
Questions about these terms: hello@isokron.ai.