llms.txt
+74 −55
− > IsoKron (isokron.ai) is the home of four open-source, local-first tools for coding agents — kronicle-lite, sea-lite, cc-anchor and mcp-catalog-snap — and of the IsoKron platform, a multi-agent, multi-tenant layer growing out of the same ideas. The tools are free and Apache-2.0. The platform is in development and not self-serve. A hosted service, Anchor (anchor.isokron.ai), countersigns kronicle-lite checkpoints on a free tier.− Author: Joshua Bryan (GitHub: rafe-walker). Legal entity: Stormhaven Enterprises LLC. Contact: hello@isokron.ai.− ## kronicle-lite 0.2.0 (MCP server; npm; MCP Registry io.github.rafe-walker/kronicle-lite)− A SQLite-backed document store where every write is an event on a SHA-256 hash chain (RFC 8785 canonical JSON, public genesis sha256("kronicle-lite-genesis-v1")), blocks are content-addressed by BLAKE3-256, every recall() hit carries an Ed25519 receipt bound to the chain head, and get_system_state gives the agent an orient call: pass the last cursor, get the delta since, a drift banner when away too long, and a retraction list of superseded or tombstoned blocks. Checkpoints are Ed25519-signed Me− Install (Claude Code plugin, server + orient skill):− claude plugin marketplace add rafe-walker/isokron-plugins− /plugin install kronicle-lite@isokron-plugins− Install (server only, Claude Code or Cowork):− claude mcp add kronicle-lite -- npx -y kronicle-lite serve− Cursor / Claude Desktop (.cursor/mcp.json, claude_desktop_config.json):− { "mcpServers": { "kronicle-lite": { "command": "npx", "args": ["-y", "kronicle-lite", "serve"] } } }− GitHub Copilot (.vscode/mcp.json): { "servers": { "kronicle-lite": { "type": "stdio", "command": "npx", "args": ["-y", "kronicle-lite", "serve"] } } }− Codex (~/.codex/config.toml): [mcp_servers.kronicle-lite] command = "npx" args = ["-y", "kronicle-lite", "serve"]− - Repository: https://github.com/rafe-walker/kronicle-lite− - npm: https://www.npmjs.com/package/kronicle-lite− - README: https://github.com/rafe-walker/kronicle-lite#readme− - Data format (every hash and signature, worked examples): https://github.com/rafe-walker/kronicle-lite/blob/main/docs/FORMAT.md− - Threat model: https://github.com/rafe-walker/kronicle-lite/blob/main/docs/THREAT-MODEL.md− - Orient skill for Claude Code: https://github.com/rafe-walker/kronicle-lite/blob/main/skills/orient/SKILL.md− - Roadmap: https://github.com/rafe-walker/kronicle-lite/blob/main/ROADMAP.md− Tools: get_system_state, audit_assumptions, recall, verify, verify_chain, checkpoint_chain, put_document, supersede_block, tombstone_block. Resource: kronicle://docs/{slug}.− ## sea-lite 0.1.1 (MCP server; npm; MCP Registry io.github.rafe-walker/sea-lite)− A fenced work queue for parallel coding agents. sea_next atomically picks and claims the best eligible ticket and returns a one-time claim token; every write must present it. Claims are leases (<= 600 s) with lazy expiry. Typed links (depends_on, blocks, parent_of, ...) keep the precedence graph acyclic; sea_apply lays down up to 50 tickets and 100 links in one all-or-nothing write. Every change is an event on the kronicle-lite chain in the same SQLite file.− Install: claude mcp add sea-lite -- npx -y sea-lite serve (or /plugin install sea-lite@isokron-plugins)− - Repository: https://github.com/rafe-walker/sea-lite− - npm: https://www.npmjs.com/package/sea-lite− ## cc-anchor 0.1.0 (Claude Code plugin; GitHub only)− A <= 25-line anchor card (project, goal, invariants, last five tool-call breadcrumbs, kronicle-lite cursor) written on PreCompact and re-injected verbatim at the top of the fresh context on SessionStart(compact), with a reconciliation discipline (treat the summary as as-of before compaction; mark stale claims RETRACTED). Status line shows goal, tool calls since compaction and drift. Works without kronicle-lite; carries the orient cursor across compaction when present.− Install: claude plugin marketplace add rafe-walker/cc-anchor && claude plugin install cc-anchor@cc-anchor− - Repository: https://github.com/rafe-walker/cc-anchor− ## mcp-catalog-snap 0.1.0 (CLI + GitHub Action; npm)− Snapshot an MCP server's tools/list, prompts/list and resources/templates/list as RFC 8785 canonical JSON with a sha256 fingerprint; re-capture and fail CI (exit 1) on any byte of drift, with JSON-Pointer paths. Catalog drift silently invalidates prompt-cache prefixes and changes agent behavior.− Usage: npx mcp-catalog-snap snapshot -- npx -y kronicle-lite serve ; npx mcp-catalog-snap check -- npx -y kronicle-lite serve− - Repository: https://github.com/rafe-walker/mcp-catalog-snap− - npm: https://www.npmjs.com/package/mcp-catalog-snap− ## isokron-plugins (Claude Code plugin marketplace)− claude plugin marketplace add rafe-walker/isokron-plugins ; then /plugin install kronicle-lite@isokron-plugins or sea-lite@isokron-plugins. Each plugin pins one npm server version and bundles its skill.− - Repository: https://github.com/rafe-walker/isokron-plugins− ## Anchor (hosted, planned, not available)− Hosted checkpoint verification: kronicle-lite checkpoint --push sends the signed Merkle root, range and public key (never the events); Anchor countersigns and returns a receipt; a public page and verify --remote check it. Live since 2026-11-01 on a free tier (1 key, 1,000 anchors/month, 30-day retention; free key via a $0 Polar checkout). Not yet running: nightly day roots published to a public git repository, OpenTimestamps (Bitcoin) and Sigstore Rekor (receipts show pending until then). A per-+ > IsoKron (isokron.ai) audits MCP (Model Context Protocol) servers for security and write-path correctness, and rebuilds or builds MCP servers for safe writes, both at fixed prices. In a client audit, every finding is checked against a control where one exists, challenged by a separate AI refuter in a clean context, and reproduced and reviewed by a person before it reaches a report; the public audits say which of these checks their findings went through, and where a check fell short. Rebuilds an+ Publisher: IsoKron. IsoKron is a trading name of Stormhaven Enterprises LLC, an Arizona LLC · Founded 2026. Contact: hello@isokron.ai. GitHub: https://github.com/isokron-ai+ Who: Joshua Bryan founded IsoKron in 2026 and runs it alone. He spent ten years at Ring as a support engineer, from its startup days through the Amazon acquisition, rising from Support Engineer I to IV and handling executive escalations, outage communications and on-call incident response. Before leaving, he designed and built internal MCP tooling that connected Splunk, Amazon Redshift and Athena, and Ring’s documentation and ticketing systems, so AI assistants could investigate across them. At + ## Services+ All prices are in US dollars. Audits are on https://isokron.ai/mcp-audit; rebuilds and builds on https://isokron.ai/mcp-development; every offer compared on https://isokron.ai/pricing.+ ### Audits+ - Write-Safety Audit, $2,500 fixed (https://isokron.ai/mcp-audit#write-safety-audit): one server, up to 40 tools, on a test tenant; it leads with the write paths and also covers security and token cost. Includes write-path tests (lost updates under concurrency, stale writes, silent no-ops, type coercion, partial multi-step writes, annotation honesty), each compared with the vendor's own API as a control where one exists; a security review (permission boundaries, read-only switches, data and cred+ - Design-partner audit, $1,250 (half price), paid upfront (3 of 3 design-partner places open, as of 12 November 2026): the same Write-Safety Audit, same scope, in exchange for a named case study and a short quote. The client approves the exact case-study text before anything is published. By request: https://isokron.ai/contact?offer=design-partner+ - Submission evidence pack, $1,000, available with a Write-Safety Audit: prepares your audit evidence for a connector directory or marketplace review, such as Claude's Connectors Directory, ChatGPT app review or Microsoft MCP certification. You submit it. Approval is the platform's decision: we don't submit on your behalf and we don't promise acceptance. Privacy policies, publisher verification, OAuth setup and listing assets aren't covered. Not affiliated with or endorsed by Anthropic, OpenAI o+ - Per-release regression check, $750 per month per server, 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 each release and reports what changed.+ - Custom / multi-server, quoted, from $5,000: more servers, multi-tenant or OAuth setups, client and server together, or the agent benchmark (calls, turns and failed calls per task), which is an optional add-on and not a package.+ - Agencies: white-label pre-release testing is available to agencies that build MCP servers. Request a quote at https://isokron.ai/contact?offer=other+ - Write-path testing for security firms: Add IsoKron's write-path testing to your own MCP security assessment: lost updates under concurrency, stale writes, silent no-ops and partial multi-step writes, each compared with the vendor's own API as a control where one exists. It complements your security testing; it does not replace it. Quoted per engagement. White-label or subcontract terms on request. Request a quote at https://isokron.ai/contact?offer=other+ - Guarantee: the agreed test coverage, documented evidence for every finding, the included fix pull requests and one retest. If IsoKron misses the agreed scope, it puts it right at no charge. IsoKron does not guarantee a number of findings.+ - Independence: the included fixes are part of the fixed price, so finding more earns IsoKron nothing extra. Larger fixes and builds are quoted separately, after the client has read the report. IsoKron does not present an audit of code it built for a client as independent work.+ ### Rebuilds and builds+ None of these has an online checkout: each is requested through the contact form or a scoping call and starts with a written statement of work.+ - MCP blueprint, $1,000 (https://isokron.ai/mcp-development#blueprint), paid upfront: a written design for one MCP server, new or existing: tool inventory and schemas, auth design, write-safety design, test plan, and a fixed-price build quote. No code changes. The full $1,000 is credited against a build or rebuild started within 30 days of delivery. The blueprint is the client's to keep and use either way. Request it at https://isokron.ai/contact?offer=blueprint Terms: https://isokron.ai/terms#b+ - Write-path rebuild, $6,000 fixed (https://isokron.ai/mcp-development#write-path-rebuild): one existing or generated MCP server, up to 40 tools. IsoKron rebuilds its write paths and tool design in its own repository, as in the PostHog research build: 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, confirm for destructive calls, tool-name aliases (no r+ - New MCP server, from $5,000, as a fixed quote after the blueprint (https://isokron.ai/mcp-development#custom-build): a new MCP server built from scratch to the ten rules on the build page. Request at https://isokron.ai/contact?offer=custom-build+ - Larger rebuilds (more than one server or more than 40 tools) are a fixed quote after the blueprint.+ - Ownership: the code is delivered into the client's repository and belongs to the client from the first pull request. IsoKron keeps its own general tools, test harnesses and know-how; its open-source tools stay under their own licenses.+ - Working practice: test tenants only, never production data; all changes as pull requests in the client's repository; scoped, revocable access; NDA on request; private by default.+ - After delivery: a handover call, the 60-day defect warranty for a rebuild, and the per-release regression check as optional maintenance.+ - Proof (research builds of vendors' open-source servers on IsoKron's own test setups, not client engagements): the PostHog MCP server research build used 15.8% fewer tool calls, 14.0% fewer turns and 23.9% fewer tool-result bytes than the unmodified build on six pre-registered tasks, at about the same estimated cost (−0.7%), with every run correct on every build; on a friction-derived task set that favors it by construction, 31.0% fewer tool calls and 22.4% lower estimated cost (https://github.+ - Sample report (https://isokron.ai/sample-report): built from the public GitHub MCP server v2.1.0 audit, laid out like a client report. It shows three of the audit's findings; the full register in the audit article lists 17 findings: 13 new, filed upstream in 11 issues; 4 already covered by earlier reports. Not a client engagement.+ - Verify an Evidence Pack (https://isokron.ai/verify): how to check an IsoKron Evidence Pack on your own machine with `npx -y kronicle-lite@0.10.1 verify-audit PACK --key-fingerprint <from your statement of work>` (runs locally; after npx's first download it needs no network), the anchor service genesis key fingerprint, the timestamp authority CAs, and a sample pack to try.+ ### Contact+ - Request an audit, a blueprint, a rebuild or a build (https://isokron.ai/contact), email hello@isokron.ai, or book a 20-minute scoping call: https://cal.com/isokronai/mcp-audit-scoping-call+ ## Public findings+ Upstream record, as of 14 November 2026: GitHub, 11 issues filed; our fix PR #3781 open; 10 community fix PRs open, 1 draft, covering 9 of the 11 issues. Grafana, 4 fix PRs (#1518–#1521) open. PostHog, 1 fix merged (#131620, co-authored by IsoKron); 3 of our PRs approved, awaiting merge. Kubernetes, 15 issues filed (#1658–#1672) and a comment on #1584, covering 17 bugs, with patches offered; issues all open; 10 fix PRs open (#1675–#1684), for 10 of the 15 issues; a maintainer reviewed 5 of the 1+ Statuses below as of 14 November 2026 (2026-11-14).+ - github/github-mcp-server v2.1.0, correctness, fix PR open (ours, #3781; no maintainer review as of 14 November 2026): concurrent issue-field updates silently revert; 19 of 30 concurrent pairs lost a change across three runs, GitHub's per-field API lost 0 of 28. https://github.com/github/github-mcp-server/issues/3751 and https://github.com/github/github-mcp-server/pull/3781+ - github/github-mcp-server v2.1.0, hardening, fix PRs open (community; #3750 and #3801 by other contributors): GITHUB_READ_ONLY=yes (or on) is parsed as false, so write tools stay enabled. https://github.com/github/github-mcp-server/issues/3747, https://github.com/github/github-mcp-server/pull/3750 and https://github.com/github/github-mcp-server/pull/3801+ - github/github-mcp-server v2.1.0, hardening (low severity), issue open: directory listings put short-lived tokenized private-file URLs in model context. https://github.com/github/github-mcp-server/issues/3748+ - grafana/mcp-grafana v2.2.0, correctness, fix PR open (ours, #1518; no maintainer review as of 14 November 2026): update_dashboard patches force an overwrite, skipping the version check that rejected a stale save in 10 of 10 through Grafana's API; two simultaneous patches lost an edit in 30 of 30 pairs while both reported success (Grafana's own save API also lost simultaneous saves, 30 of 30 on Grafana 13 and 20 of 30 on Grafana 11, so the control is not clean). The proposed fix lost 0 of 60 pa+ - PostHog MCP server (tested on test accounts in PostHog Cloud), correctness, fix PR approved, awaiting merge: generated tool schemas turned the string "false" into true and null into 0. https://github.com/PostHog/posthog/pull/131514+ - PostHog MCP server (test accounts in PostHog Cloud), correctness, fix merged: concurrent updates to one insight lost a write in 7 of 11 pairs through the MCP server and in 6 of 11 sent straight to PostHog's API, so the bug was in the API. PostHog merged the fix for insights in https://github.com/PostHog/posthog/pull/131620, co-authored by IsoKron.+ - Cost, github/github-mcp-server v2.1.0: in our audit, Claude Opus via Claude Code completed four routine development jobs through the server using MCP tools only (bug fix to merged PR, PR review, issue triage, multi-file rename): 17–33 tool calls and about $0.77–$1.37 per job, as Claude Code's reported API-equivalent cost, two runs per job. Per-run figures: https://isokron.ai/research/github-mcp-server-audit#developer-runs-calls-and-cost-per-job Submitting a pull-request review with inline comm+ An open issue is a report, not a confirmed vulnerability, until the maintainers say so.
Showing the first 40 of each.