Teams shipping with AI agents
When AI coding agents write and test the code, Microfilm is the MCP server they write signed test evidence to as they work — so you keep a verifiable record of what was tested and why each change is trusted, instead of a log that scrolls past and disappears.
When agents write and run the tests, the open question is trust: what was actually tested, and why do you believe this change is safe to ship? Microfilm is the evidence layer the agent writes to — every test event signed and chained — so the proof of what happened keeps pace with the code, and your team can search, trace, and share it.
Availability · Writing signed evidence through the MCP server is free. The shared portal, requirements traceability, sharing, and integrations are Team-and-up cloud features.
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 pain
AI coding agents generate, change, and test code faster than anyone can document what was checked. The risk isn’t just bugs — it’s that nobody can say, after the fact, what was tested and why a change was trusted. The agent’s test output scrolls past in a log and disappears; there’s no record left to stand on.
How it maps
Microfilm runs the same four steps the rest of the site does — Capture, Sign, Hand off, Trace — but here the writer at the Capture step is the coding agent itself.
As your agent tests a change, it writes each event to the MCP server — the procedure it ran, the work item, and the result — through a typed tool call, as the work happens.
Every event is signed with a KMS-backed key and chained into a tamper-evident reel — so trust in an agent-authored change is backed by a record anyone can verify offline, not an assertion.
Signed records flow into the web portal, where your team searches and shares them — one source of truth for what the agent tested, not a log that vanished.
A traceability view links each requirement to the signed records that prove it was tested, so the proof keeps up as agents move fast — and an untested requirement surfaces as a gap.
For your coding agents
Microfilm exposes a native Model Context Protocol (MCP) server as the write path for test evidence. The agent records what it tested as a structured event — and gets back a signed record, not a line in a console.
Point your agents at Microfilm’s MCP server and they write test evidence directly through a tool call — no desktop app, no extension, no screen recorder to bolt on.
Each event carries the procedure, the work item, and the result. Because the write path is typed, the shape is consistent across every agent and run — your evidence stays queryable.
Every write comes back signed with a KMS-backed key (ES256) and chained into a tamper-evident reel — a record that can be verified offline by anyone you share it with.
The agent, the developer, and the auditor all work from the same signed evidence. There’s no separate “agent version” of the truth to drift out of sync.
FAQ
No. Microfilm records and proves the testing behind a change — it doesn’t review or certify the code itself. The decision that a change is safe to ship stays with your team; Microfilm gives you the verifiable evidence to make and defend it.
Through a native Model Context Protocol (MCP) server. As an agent tests, it writes each event — the procedure, the work item, and the result — to the server and gets back a signed, chained record. There’s no app or extension to install.
That for any change — including one an agent authored and tested — there’s a signed, verifiable record of what was tested and the result. You can answer "why do we trust this?" with evidence anyone can check, rather than a claim.
Writing signed evidence through the MCP server is free. The shared portal, requirements traceability, sharing, and integrations are cloud capabilities on the Team plan and up.
Microfilm records and proves the testing behind AI-assisted changes; it does not review or certify AI-generated code on its own. The decision that a change is safe to ship stays with your team — Microfilm gives you the evidence to make and defend it.
Create an account, connect your agent to the MCP server, and write your first signed record.