Skip to content
@isokron-ai

IsoKron

MCP server audits and builds. Open research and tools for agent-safe writes: correctness, concurrency, preconditions and verifiable evidence.

IsoKron

IsoKron

MCP servers that agents can safely change things through. We audit and build Model Context Protocol servers, and we publish the research and tools behind that work.

An MCP server is part of the system's correctness boundary. A tool can return a perfectly formatted success while it overwrites someone else's edit, changes the wrong object, drops fields the caller never mentioned, or does nothing at all. Our work tests for exactly that: concurrent and stale writes, preconditions, partial failure, honest results, and the extra calls and turns that clumsy tools cost an agent.

Research

GitHub MCP server v2.1.0 audit Concurrent issue-field updates lost a change in 19 of 30 pairs while both calls reported success. 17 findings, 13 reported upstream, and a before/after benchmark.
How to test an MCP server without fooling yourself The rules our audits run under and the refutation funnel every claim passes through.
Verify an audit's evidence yourself Check an IsoKron Evidence Pack offline with one command.
Why MCP tool design matters What a clumsy tool really costs: accuracy, failed runs, time and plan limits.
Shipping a production MCP server Auth, per-user limits and tracing on the 2026-07-28 spec.

Open source

Repository What it does
github-mcp-writepath-experiment The changes behind our GitHub MCP server before/after benchmark, as a build and a patch series. Research only; not affiliated with GitHub.
kronicle-lite Local-first MCP server: hash-chained document store, signed receipts, and the verify-audit command that checks an Evidence Pack offline.
sea-lite MCP work queue for parallel coding agents: claim fencing, path-scoped claims and atomic batches.
mcp-catalog-snap Snapshot an MCP server's tool catalog as canonical JSON and fail CI on drift.
cc-anchor Claude Code plugin: an anchor card that survives context compaction.

How we report what we find

Findings go to the maintainers first, with a reproduction and, where practical, a fix. Security-sensitive findings go through the vendor's own security process and stay private until it is resolved. Every claim in a write-up is one that survived an attempt to disprove it.

Work with us

Fixed-price MCP server audits and MCP server builds. See a sample report, or write to hello@isokron.ai.

IsoKron is a brand of Stormhaven Enterprises LLC.

Popular repositories Loading

  1. kronicle-lite kronicle-lite Public

    Local-first MCP server: hash-chained document store, signed retrieval receipts, and an orient protocol that tells your agent when its beliefs went stale.

    TypeScript 1

  2. github-mcp-writepath-experiment github-mcp-writepath-experiment Public

    Research build: write-path changes to GitHub MCP server v2.1.0 behind IsoKron's before/after benchmark. Not affiliated with GitHub.

    Go 1

  3. kubernetes-mcp-writepath-experiment kubernetes-mcp-writepath-experiment Public

    Research build: bug fixes and usability changes to the Kubernetes MCP server (v0.1.2, 66553fed) behind IsoKron's audit and before/after benchmark

    Go 1

  4. strapi-plugin-writesafe strapi-plugin-writesafe Public

    Write-safe MCP tools for Strapi 5: version-checked writes and row-level edits for the built-in MCP server. MIT, on npm and the Strapi Marketplace.

    JavaScript 1

  5. mcp-writecheck-action mcp-writecheck-action Public

    Test your MCP server's write tools against the MCP Write-Safety Requirements (MWS 0.9) in CI. By IsoKron.

    JavaScript 1

  6. mcp-write-safety-kits mcp-write-safety-kits Public

    Helper kits (TypeScript and Python) for MCP servers whose write tools meet the MCP Write-Safety Requirements

    Python 1

Repositories

Showing 10 of 19 repositories

Top languages

Loading…

Most used topics

Loading…