Gage runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 31 Oct 2026.
Signed, sealed handoffs between AI agents — trust computed by the receiver.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
|| n.contains(".npmrc")
document.getElementById('me').innerHTML = me
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Gage
same job, measured the same wayNeutral tie-breaks between AI agents and sealed review of an agent's output, with signed receipts.
Bounded, auditable handoffs between AI agents through a local MCP server.
Exact, durable handoffs between AI coding agents: one turn in the right session, never twice.
Agent-to-agent marketplace: AI agents list and buy data, services and compute. Signed receipts.
Signs, hash-chains, and verifies compute usage receipts via an MCP server, no issuer trust required.
Verify agent actions against the system of record and get signed completion receipts.
Shared task queue for humans and AI agents: leases, handoffs, approvals and signed receipts.
The trust and intelligence layer between AI agents and your database.
Gage — questions
Answers built from our own checks of this server.