Feature · MCP server
Microfilm’s MCP server is the headless write path for test evidence: an AI coding agent records each test event — the procedure it ran, the work item, the result — to the server as it works, and gets back a signed, tamper-evident record. There’s no desktop app and no extension.
Point your coding agent — Claude Code, Cursor, whatever you run — at Microfilm’s Model Context Protocol server. As it tests, it writes each event to the server and Microfilm signs it on the spot. The agent is the user; the evidence is a by-product of the work it already does.
Availability · Free — the MCP server and signed records are included on every plan.
What Microfilm is · Microfilm is the evidence engine for teams and agents: a headless MCP server that AI coding agents write signed test evidence to as they work, paired with a web portal where teams search, trace, and share that evidence. Every event is signed with a KMS-backed key and chained, so any record can be verified offline.
The problem
AI coding agents now write most of the test code and run most of the tests. Running them was never the bottleneck — proving they ran is. A green log scrolls past in a terminal and disappears; nobody can say afterward what was tested, against which work item, or what the result actually was. The output is there; the evidence isn’t.
How it works
Microfilm runs as a Model Context Protocol server with no UI to open. Your agent connects, calls a tool to record each test event, and keeps working. Nothing to install on a tester’s machine, because there is no tester in the loop.
Each event carries the procedure that ran, the work item it exercised, and the result. The record is captured at the moment of work — not reconstructed from a log or a screenshot after the fact.
Every write comes back signed and chained into a tamper-evident reel. The agent — and the rest of your team — gets a record that can be verified offline, not a line in a console.
Because evidence is written through a typed tool call, the shape is consistent across every agent and every run. The structure is enforced at the write path, so your evidence is queryable instead of a pile of free text.
Where it fits
The MCP server is where the evidence trail begins. What the agent writes here becomes a signed, tamper-evident record, lands in the evidence portal, and is the substance the requirements-traceability views are built from.
FAQ
No. Microfilm is a headless MCP server — there’s no desktop app, browser extension, or screen recorder. You point your AI coding agent at the server and it writes evidence through a tool call as it tests.
Any agent that speaks the Model Context Protocol, such as Claude Code or Cursor. The agent records each test event — the procedure, the work item, and the result — as it runs.
A signed, chained record. Every event is signed with a KMS-backed key (ES256) and linked into a tamper-evident reel, so the record can be verified offline by anyone you share it with.
Yes. The MCP server and signed records are included on every plan. The shared, searchable portal and requirements-traceability views are Team-and-up cloud features.
Create an account, connect your agent to the MCP server, and write your first signed record.