Skip to content
IsoKron

Writecheck setup

The mcp-writecheck Action, added to your repository

We open one pull request that adds the write-safety check to your CI, with the first signed record from a run against a disposable backend.

Send the four details below, then pay at checkout. No call needed.

Writecheck setup $950, fixed. Not covered: a SaaS backend we cannot run in a disposable container. For one of those, the tests need a sandbox tenant of your own; name the backend in the intake, and we tell you before any work starts whether the setup fits.

What you get

One pull request in your repository.

Terms for the writecheck setup. The check itself is open source and free to run; this is our work to set it up.

How it runs

  1. Step 1: Send four details

    The repository URL, the backend the server talks to, a contact email, and anything we should know.
  2. Step 2: Pay at checkout

    $950 by card, through Stripe. No call needed.
  3. Step 3: We open the pull request

    The manifest, the compose file, the workflow, the first plan hash and the first signed full-mode record, in one pull request in your repository.
  4. Step 4: You review and merge

    After the merge, the workflow runs the plan on pull requests and the full run on your main branch.

Send the four details

Repository URL, The backend it talks to, Contact email, Anything we should know. Not covered: a SaaS backend we cannot run in a disposable container. For one of those, the tests need a sandbox tenant of your own; name the backend in the intake, and we tell you before any work starts whether the setup fits.

Caution: Never paste tokens, passwords or keys here. We ask for repository access separately, by email.

We reply within two business days. Or email hello@isokron.ai.

Where this fits

The setup is part of the first step. If you want the results read, the readout is next.
  1. Step 1

    Test

    Find out what your server’s writes do.

    • MCP Server CheckerFree

      Paste your server’s tools/list answer and get a grade for each area. It runs in your browser; nothing is stored or sent.

    • Writecheck readout$450

      A written reading of every verdict in your mcp-writecheck run and the top three fixes in order. No call needed.

    • Writecheck setup$950

      We add the mcp-writecheck GitHub Action to your repository as a pull request, with the first signed full-mode record. No call needed.

    • Write-Safety Audit$2,500

      We test your server’s write paths on a test tenant, with a security review, fix pull requests for up to five of the highest-severity findings and one retest.

  2. Step 2

    Fix

    Repair the write paths, or build the server new.

    • Write-path rebuild$6,000

      We rebuild the write paths and tool design of a server you already have, in its own repository, with a before/after benchmark.

    • New MCP serverfrom $7,500

      A new server for one API, one sign-in method and up to 10 tools. The price is fixed in the blueprint, which is part of it.

  3. Step 3

    Keep

    Keep it checked as the server changes.

    • Per-release regression check$750 per month per server

      We re-run the tests against up to four releases a month and report what changed. Three-month minimum.

    • Advisory retainer$2,000 per month

      Two 60-minute sessions a month, written answers in between, and reviews of your designs and pull requests.

On request, or on its own page: Design-partner auditDesign reviewMCP blueprintMore tools or a second serverDirectory submission packLarger audits, rebuilds and buildsSecurity firms and agencies

How the readout works: buying it without a call.

Writecheck setup FAQ

What is in the pull request?

The manifest (writecheck.yaml) for your server. A compose file that starts a disposable backend for the tests to write to. The GitHub Actions workflow: plan mode on pull requests, full mode on your main branch. The first plan hash, from a plan we have read. The first full-mode record, signed: one run against the disposable backend, with a verdict per requirement and write path.

What does the setup not cover?

Not covered: a SaaS backend we cannot run in a disposable container. For one of those, the tests need a sandbox tenant of your own; name the backend in the intake, and we tell you before any work starts whether the setup fits. It also does not fix what the check finds, read the results for you or replace an audit.

Why is there a disposable backend?

A full-mode run makes real writes: it creates, changes and deletes objects in whatever the manifest points at. The compose file starts a backend that exists only for the run, so the tests never write to a system you use.

What do you need from us?

The four details in the intake: repository URL, the backend it talks to, contact email, anything we should know. For a private repository, access to open one pull request, which you can revoke afterwards. Never production data or production credentials.

What comes after the setup?

The check runs in your CI and its results are yours. If you want them read, the writecheck readout ($450) is a written reading of every verdict and the top three fixes. If you want the running server tested by us, with controls and fix pull requests, that is the Write-Safety Audit ($2,500).