Skip to content

v0.6.0: MCP recorder, rules drafter, JavaScript recorder

Choose a tag to compare

View all tags
@ntinosgkiou-code ntinosgkiou-code released this 25 Oct 18:46
· 17 commits to main since this release
v0.6.0
b56dd45

Three ways to get to your first report with fewer steps. Prototype, no external security review; read the known limits.

New

  • mcp-record: a stdio proxy in front of any MCP server. It forwards every message unchanged and copies each tools/call into an events file before the server sees it. No change to your agent or the server.
    python -m agentdryrun mcp-record --out mcp-events.jsonl -- python my_server.py
  • suggest-rules: drafts a first rules file from what your agent did (from tool names only; every entry says REVIEW ME; it never writes limits or refusals).
  • JavaScript/TypeScript recorder (js/): same Recorder, same events file, zero dependencies, Node 18+. npm install github:ntinosgkiou-code/agentdryrun (not on npm yet).

What was checked

  • Byte-for-byte transparency of the proxy against a fake server; the official MCP Python SDK 1.30 and 2.3 (client and server) in CI on Linux and Windows, both calls recorded.
  • Node recorder on Node 18 and 22, Linux and Windows. Events written by JavaScript are judged by the Python side.
  • 92 Python tests, 7 Node tests.
  • A real bug found only by using the official client: the proxy crashed when the server exited while the client still held stdin open. Fixed and pinned by a test.

What was NOT checked

Desktop MCP clients (Claude Desktop, Cursor, VS Code), servers in other languages, the HTTP transport. If yours misbehaves, open an issue with the client name and version.

It records the attempt, not the result or the approval, and it cannot stop anything. See the README.

Assets 2
Loading