Skip to content
IsoKron

MCP advisory

Advice for teams building MCP servers in-house

You build the server; we read it the way our audits test one: your mcp-writecheck results, a design before it ships, or your work month by month.

Writecheck readout $450, counted toward an audit within 30 days. Design review $1,500 fixed. Advisory retainer $2,000 per month, month-to-month. See the packages

Which one you need

Want us to design the server instead? The MCP blueprint ($1,000) is the design and a fixed build quote in writing.

Packages and prices

Each starts with a short written statement of work.

Design review

$1,500

Fixed price

Best for a team about to ship a new server or a change to its write paths, that wants it read before it ships.One design doc, pull request or tool catalog for one MCP server, reviewed against the 37 MWS requirements before it ships. For teams building in-house.

Delivery: date agreed in writing before we start

  • A review against every MWS requirement that applies: where the design meets it, where it falls short, and what to change
  • The write paths first: lost updates, stale writes, retries, partial writes and destructive calls
  • A written review you keep and can share with your team
  • A 60-minute call to go through it
  • No testing: we read the design, the code or the catalog; we do not run the server
  • No code changes
  • Not an audit and not a security review

Requested through the contact form.

Request a design review

Advisory retainer

$2,000

per month, month-to-month

Best for a team building MCP servers over months, that wants a regular reviewer without hiring one.Ongoing advice for a team building MCP servers in-house: the write paths, the tool design and what to test. At most three retainer clients at a time.

Month-to-month, with no minimum term

  • Two 60-minute sessions a month
  • Written answers between sessions within one business day
  • Reviews of your designs and pull requests
  • Writing code or running tests: builds and audits are separate offers
  • No production data or production credentials

We take at most three retainer clients at a time, so the retainer starts with a request, not a checkout: we reply to say whether a place is open.

Request a place

None of the three touches production data or production credentials; we need a test tenant only if we make the readout’s mcp-writecheck run ourselves. No online checkout: we confirm the scope and the dates by email or on a call. Terms for the writecheck readout, the design review and the advisory retainer.

How a readout or a review runs

We read against the MCP Write-Safety Requirements (MWS): 37 testable requirements for MCP servers that write data.
  1. Step 1: Request

    Tell us which offer, the server and what you want read. For the retainer, we reply to say whether a place is open.
  2. Step 2: Scope in writing

    A short statement of work with the price, what we read and the dates. Access to a test tenant only if we make the run.
  3. Step 3: We read and write it up

    The reading or the review in writing, with the write paths first and the fixes in order.
  4. Step 4: The call

    We go through it with your team, and you keep the written copy.

The retainer runs the same way, month by month: two sessions of 60 minutes, written answers in between, and reviews of the designs and pull requests you send.

MCP advisory FAQ

Who is advisory for?

Teams that build or run their own MCP server and want an experienced reader on its write paths, without handing the work over. If you want us to test the running server, that is the Write-Safety Audit (https://isokron.ai/mcp-audit); if you want us to change it, that is a rebuild or a build (https://isokron.ai/mcp-development).

What does the readout add to an mcp-writecheck run?

mcp-writecheck is our open-source CLI: it runs the MWS checks it covers against your server in a test environment (14 requirements in full and 23 in part, in the preview) and prints one verdict per requirement and write path. The run is free and its output is yours. The readout is our reading of that output: which verdicts matter for your users and which do not, and the three fixes to make first.

How does the readout count toward an audit?

The full $450 counts toward a Write-Safety Audit or a design-partner audit booked within 30 days of the readout. It is part of the audit’s price, not on top of it. After that window it does not count, and it is not paid out in cash.

Is a design review the same as an audit?

No. A design review reads a design, a pull request or a tool catalog before it ships, and involves no testing. An audit tests the running server on a test tenant, with controls, reproductions, fixes and an Evidence Pack. The review comes before the build; the audit comes before release.

How does the retainer work?

Two 60-minute sessions a month, written answers between sessions within one business day, and reviews of your designs and pull requests, for $2,000 a month, month-to-month. We take at most three retainer clients at a time, so the retainer starts with a request, not a checkout: we reply to say whether a place is open.

What do you need from us?

For a readout, the mcp-writecheck output, or a test tenant and a token scoped to it if we make the run. For a design review, the design doc, pull request or tool catalog. Never production data or production credentials. NDA on request; nothing is published without your written consent (https://isokron.ai/security#client-data).

Want a second reader on your MCP server?

Tell us which offer, the server and what you want read: a writecheck run, a design, a pull request or a tool catalog. We reply to confirm the scope, the price and the dates.