Kineti

io.github.therawlogsPublished by GitHub account therawlogsv0.3.4Updated Oct 24, 2026

Kineti: spend cap, undo, and test proof for AI coding agents

Overview

AI-generated overview

Kineti gives AI coding agents local governance tools: a self-reported spend cap, a registered rollback stack, and workspace-bound test receipts.

What you can do
Kineti runs as a local MCP server exposing 14 tools: 13 governance tools plus a plain-talk helper. It keeps a 13-stage project state record, a newest-first transactional undo stack of inverses the agent registered, and test receipts that pair local exit codes with SHA-256 workspace fingerprints. It also maintains a hash-chained spend ledger with a default $50 ceiling that exits with code 3 near the recorded limit, plus a local dashboard.
When to use it
Worth adding when you want a coding agent to log its own token spend against a cap, register rollback steps it can undo, and leave local evidence that tests ran against the current workspace. It suits developers running agents such as Claude Code, Cursor, OpenCode, Codex or Antigravity who want a local record of a run.
Requirements
Local process over stdio, installed from npm as kineti and started with npx. Needs Node.js 18 or later and Bun 1.1 or later installed for governance execution. No accounts, API keys, environment variables or headers are declared. Editor MCP configuration is added manually; kineti init installs skills and hooks but not the MCP server config.
Before you install
Spend totals are reported by the agent; Kineti does not measure provider billing or stop calls made outside it, and it does not mediate every agent action. Test receipts are local and are not signed certificates. Resetting a tripped breaker requires the --i-am-human flag. The dashboard binds to loopback only. Prompt-injection tests in the repository are not a general security guarantee.

Installation

In SourceWeft

  1. Open Kineti in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.4LatestSep 25, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts