Conduit
Let agents drive a headless browser while producing SHA-256 audit trails and Ed25519-signed proof bundles you can retain after automated checks.
Overview
Conduit is a MCP server for the Ship phase that runs headless browser automation with SHA-256 audit trails and Ed25519-signed proof bundles for AI agents.
What is this MCP server?
- Headless browser automation exposed as MCP tools for agents
- SHA-256 audit trails for actions and captured artifacts
- Ed25519-signed proof bundles for verifiable run records
- PyPI package conduit-browser v0.2.1 with stdio transport
- Designed for agent-driven flows that need evidence, not silent scraping
- Server version 0.2.1
- PyPI identifier conduit-browser
What problem does it solve?
Agent browser runs are hard to trust after the fact because there is no standard signed record of what was opened, clicked, or captured.
Who is it for?
Builders who need auditable, agent-controlled headless browsing before release or for security-sensitive checklists.
Skip if: Simple local UI tests with no proof requirements, non-technical marketing-only image tasks, or teams that forbid automated browser access to production accounts.
What do I get? / Deliverables
After you register Conduit, agent-driven browser sessions can return hash-chained audit data and Ed25519-signed proof bundles you can verify offline.
- Agent-invokable headless browser automation via MCP
- SHA-256 audit trail artifacts from documented runs
- Ed25519-signed proof bundles suitable for release or security records
Recommended MCP Servers
Journey fit
Conduit belongs in Ship because it wraps browser automation with tamper-evident logging for pre-release verification and accountability, not casual browsing during ideation. Security is the canonical shelf when the differentiator is cryptographic audit trails and signed proof bundles, not just clicking through a UI test.
How it compares
Auditable headless-browser MCP server, not a generic screenshot skill or a passive monitoring SaaS.
Common Questions / FAQ
Who is Conduit for?
Solo builders and small teams whose agents must automate browsers and produce verifiable SHA-256 audit trails plus Ed25519-signed proof bundles.
When should I use Conduit?
Use it in Ship when you are running security or launch checks that need a headless browser and a cryptographic record of the agent’s actions.
How do I add Conduit to my agent?
Install conduit-browser v0.2.1 from PyPI, configure stdio MCP in your client, and grant the server environment access needed for headless browser runs.