Skip to content
IsoKron

Pricing

Every offer and its price, in one table

Fixed prices where the scope is fixed, and a fixed quote after the blueprint where it is not. The listed price is the price.

Compare the offers

Scope, turnaround, deliverables and exclusions for each. Prices in US dollars.
Every IsoKron offer: price, scope and turnaround, what you get, and what is not included
Offer and priceScope and turnaroundWhat you getNot included
Audits
Write-Safety Audit$2,500Fixed priceRequest an audit

One server, up to 40 tools, one test account on one test tenant: the write paths first, plus a security review and what the tool catalog costs in context.

5 business days from the day access is in place

Local or remote. Servers behind OAuth sign-in are the same price: today we need a test account and someone on your side who can issue us a fresh access token during the test week. Testing two tenants against each other is not available yet. Extra only if you need it: tools 41 to 65 are +$500 (above 65 tools, the audit is quoted), and a second server in the same engagement is +$1,750. Payment: 50% deposit ($1,250) to reserve the slot, 50% on delivery. Design-partner audit: the same audit for $1,250, in exchange for a named case study; terms under the table.

  • Write-path tests: lost updates under concurrency, stale writes, silent no-ops, type coercion, partial multi-step writes, annotation honesty
  • Each write-path test compared with the vendor’s own API as a control, where one exists
  • Security review: permission boundaries, read-only switches, data and credentials in model context
  • Tool catalog review: catalog token weight (what the tool list costs in the model’s context), annotation and schema flags
  • A pinned catalog snapshot made with mcp-catalog-snap, so you can detect drift later
  • Every finding control-checked (where a control exists), refuter-challenged and reproduced by a person
  • Written report (reproduction steps, evidence, impact, suggested fix) and a 60-minute walkthrough
  • Evidence Pack: the harness is frozen and independently timestamped before the first run, and you can verify the results with one command that runs locally (after npx’s first download it needs no network)
  • Fix pull requests (or patches where we have no repository access) for up to five of the highest-severity findings, where the fix fits within the server’s existing code; further fixes, and fixes that need a redesign, new tools or changes to other systems, are quoted separately
  • One free retest within 30 days
  • No production data or production tenants
  • Not a penetration test of the platform behind the server, or of its OAuth provider
  • Two accounts or tenants tested against each other: not available yet
Rebuilds and builds
Write-path rebuild$6,000Fixed price in total, no blueprint neededRequest a rebuild

One existing or generated MCP server, up to 40 tools. We keep your server and rebuild its write paths and tool design in its own repository.

About two weeks; the date is agreed in writing before we start

No blueprint needed: send us the tool list and we confirm the price. Payment: 50% ($3,000) to start, 50% on delivery. Requested through the contact form or a scoping call. Larger rebuilds (more than one server or more than 40 tools) are a fixed quote after the blueprint.

  • Fixes for the defects we find in the server’s tools and write paths
  • The write-path and tool-design patterns from our PostHog research build, where the server needs them: compact write receipts, batch tools with per-item results, version-checked partial updates, validate-first errors, create-with-children with rollback, read-only batching, schema de-duplication and the others listed below
  • Tests for every change, run in your CI, and a pinned tools/list snapshot made with mcp-catalog-snap
  • A before/after agent benchmark on two task sets: tasks frozen before the changes are designed, and tasks drawn from the friction we find, which favor the rebuild by construction. Reported separately, whatever they show
  • Code delivered through pull requests into your repository, owned by you
  • A handover call with whoever will maintain it
  • A 60-day defect warranty
  • Backend or API changes behind the server: quoted separately
  • Production data or production tenants
  • No promised benchmark gain: we report the before/after either way
New MCP serverfrom $7,500Fixed in the blueprint, which is part of the priceRequest a quote

One API, one sign-in method, up to 10 tools. We design and build a new MCP server from scratch to the ten rules on the build page: sign-in, tools, reads, writes and tests.

Date quoted with the price

Starts with the blueprint: the design and a fixed price in writing. The blueprint costs $1,000 and is part of the build price, not on top of it: a $7,500 server is $1,000 for the blueprint, then $6,500 for the build. If you stop after the blueprint, you have paid $1,000 and the design is yours to keep. Requested through the contact form or a scoping call.

  • A server built to the ten rules on the build page, in your repository, under your account
  • Tests for each rule, run in your CI, and a pinned tools/list snapshot
  • A short note on deployment and auth: stdio for one machine, or remote HTTP with OAuth when other people need to call it
  • A handover call with whoever will maintain it
  • A 60-day defect warranty
  • Backend or API changes behind the server: quoted separately
  • Production data or production tenants
  • Running the server in production, unless the quote includes it
  • More tools, APIs or sign-in methods: a higher fixed quote from the same blueprint
MCP blueprint$1,000Part of the build price if you sign the build within 60 daysRequest a blueprint

One MCP server, new or existing. The design and a fixed price, in writing, before any code is written. Needed for a new server or larger work, not for the standard rebuild.

Date agreed in writing before we start

Requested through the contact form or a scoping call. Paid upfront. Part of the build price, not on top of it; if you stop after the blueprint, the design is yours to keep. The blueprint counts toward a build you sign within 60 days of receiving it.

  • Tool inventory and schemas: each tool, what it does, its inputs and its result
  • Auth design: how users and agents sign in, token scopes and tenant separation
  • Write-safety design: for each write, how lost updates, retries, partial writes and destructive calls are handled
  • Test plan: what we test and how, including the before/after benchmark tasks for a rebuild
  • A fixed-price build quote with a delivery date
  • No code changes: the blueprint is the design and the quote
Add-ons
More tools$500 for tools 41 to 65Ask for it in your request

Available with a Write-Safety Audit. One step only: above 65 tools, the audit is quoted.

Agreed in writing with the audit’s scope and dates

Ask for it in your audit request.

  • Tools 41 to 65 on the same server, in the same audit
Set out in the written quote
Second server$1,750 eachAsk for it in your request

Available with a Write-Safety Audit. Same scope as the first server, shared setup and one report.

Agreed in writing with the audit’s scope and dates

Ask for it in your audit request.

  • A further server audited in the same engagement, with the same scope: up to 40 tools and one test account
Set out in the written quote
Directory submission pack$1,000Add-onAsk for it in your request

Available with a Write-Safety Audit. Your audit evidence, prepared for a connector directory or marketplace review.

Agreed in writing with the audit’s scope and dates

Ask for it in your audit request.

  • A per-tool evidence table: each tool’s declared annotations, its observed behavior, the target platform’s published review criteria that apply (dated to when we checked them), the test result and an evidence reference
  • Written per-tool justifications for the read-only and destructive annotations, based on observed behavior
  • A reviewer test set: positive and negative test prompts with expected results, setup steps and a test-tenant checklist
  • A versioned evidence manifest: server version or commit, tool catalog snapshot, test dates, evidence hashes and limits
  • A plain list of what the pack does not cover
  • One follow-up retest of a tool if a platform reviewer disputes its behavior, within the audit’s 30-day retest window
  • Submission on your behalf: you submit it
  • Any promise of approval or acceptance
  • Privacy policy, publisher verification, OAuth setup, listing assets
Per-release regression check$750 per month per serverAsk for it in your request

Three-month minimum. Available after an audit, or as maintenance after a rebuild or build. Re-runs the write-path reproductions from the audit, or the tests from the rebuild or build, against up to four releases a month and reports what changed. More releases are quoted.

Up to four releases a month, for at least three months

Ask for it with an audit, a rebuild or a build.

  • Re-runs the write-path reproductions from the audit, or the tests from the rebuild or build, against up to four releases a month and reports what changed
Set out in the written quote

How the audit compares with MCP security audits, pentests and scanners

Larger work is a fixed quote: an audit of more than 65 tools after a look at the tool list, a larger rebuild or build from the blueprint. The MCP blueprint is needed for a new server or larger work, not for the standard rebuild: how the blueprint works.

Security firms and agencies. We add our write-path testing to a security firm’s own MCP assessment, or test an agency’s builds before release, under your name if you prefer. It complements your security testing; it does not replace it. Quoted per engagement. Request a quote.

Note: Design-partner places available

The same Write-Safety Audit at half price, $1,250 paid upfront, in exchange for a named case study and a short quote from you.

Who it is for: a server that fits the audit’s scope, one server with up to 40 tools, tested on a test tenant.

The case study is published only after you approve its exact text; until then nothing about the engagement is published. It starts when both sides sign a written statement of work.

The lower price is in exchange for the published case study: if you later decide not to publish it, you pay the $1,250 difference.

Apply for a design-partner place

Audit or rebuild?

An audit compared with a write-path rebuild
ComparedWrite-Safety AuditWrite-path rebuild
What it doesTests the server you have and reports what it gets wrong, with reproductions and an Evidence PackChanges the server’s write paths and tool design, with a before/after benchmark
Price$2,500 fixed$6,000 in total, no blueprint needed
Delivery5 business days from the day access is in placeAbout two weeks
FixesFix pull requests for up to five of the highest-severity findings, within the server’s existing codeFixes for the defects we find, and the ten rules where the server needs them
Who checks itEvery finding checked against the vendor’s own API as a control where one exists, challenged by a separate AI refuter in a clean context, then reproduced and reviewed by a personOur own tests, and you get the evidence; not an independent audit

MCP server auditsMCP server builds

Payment and refunds

  • Write-Safety Audit. Know your server and roughly how many tools it has? Pay the $1,250 deposit now; it is fully refundable until testing starts. Want the scope confirmed first? Send us the server instead. Book the audit: $1,250 deposit
  • Builds. No online checkout: each starts with a written statement of work. The MCP blueprint is paid upfront. The blueprint costs $1,000 and is part of the build price, not on top of it: a $7,500 server is $1,000 for the blueprint, then $6,500 for the build. If you stop after the blueprint, you have paid $1,000 and the design is yours to keep. The blueprint counts toward a build you sign within 60 days of receiving it.

Terms of sale and refunds: the audit deposit, the write-path rebuild, a new MCP server and the MCP blueprint.

Paying and procurement

How do we pay?

Through Stripe, in US dollars. Write-Safety Audit: 50% deposit ($1,250) by card at checkout; the balance by Stripe invoice on delivery. Write-path rebuild: 50% when the statement of work is signed and 50% on delivery, by Stripe invoice. The MCP blueprint is paid upfront.

Can you provide a W-9?

Yes, on request.

Will you sign an NDA?

Yes. A mutual NDA is available on request.

Request an audit or a build

Tell us which server and what you need. We reply to confirm the scope, the price and the dates.