Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
W

warewithall2/gage

Independent directory — not the official site. Details below come from the project's public repository.

Hand work between AI agents without handing over trust.

1 ★ measured · checked 2026-11-19

Before you install: no copy-paste command · license Apache-2.0

First step: nothing runnable here yet - start from the repository: https://github.com/warewithall2/gage

★ 1·updated 2026-11-15
View on GitHub ↗Direct link · no redirect page

We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →

Star count
1 ★ · warewithall2/gage · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository warewithall2/gage;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# gage

Excerpted from the repository README (abridged)

Hand work between AI agents without handing over trust.
Your Claude hands a task to Codex. A colleague's agent sends you their project
state. Normally nothing on the receiving end says who wrote it, or whether you
have ever confirmed that person — and an agent reading its inbox is not a human
reading email. A human who reads a phishing message is not executing it; an
agent is. A channel that lets one LLM send prompts to another is, by default,
a prompt-injection delivery network.
gage is that channel built the other way round. It is three things:
A bundle — files, a prompt and decisions in a signed, sealed directory.
A list you control. Two people compare four word-pairs over a channel
neither machine controls, and gage confirm records that they did. A key
nobody has confirmed still works and says so — SENDER ON YOUR LIST,
UNCONFIRMED — because being on a list and having been checked are two
different facts and only one of them is a claim about a person. Arrival is
not consent either: a bundle that lands in your inbox sits there unread
until you accept it. (A sealed file somebody hands you is the exception, and
the frame says so when you open one: pointing gage open at a directory is
itself the decision, and there is no gate behind it.)
A reading frame. Before any payload, the receiving agent is told that
this is data from an identified party carrying no authority — and when the
sender is not attributable under a key you currently accept, the contents
are withheld rather than annotated, because an annotation is something the
payload can argue with.
Every line of that recording is genuine output. The same capture is
docs/demo.md as annotated text and
docs/demo.cast in asciinema v2 format, and
scripts/demo.sh reproduces it in a throwaway directory
without touching your own gage home.
Try it:
curl -fsSL https://gage.sh/install.sh | sh # verifies its own checksum
gage quickstart
It works across vendors because it is not a protocol: a bundle is a signed
directory, so it moves over a shared folder, git, email, or anything else you
already have. There is a viewer (gage ui), machines find each other on a LAN
with no server in the middle (gage lan), and an agent can drive the whole
thing itself over MCP (gage mcp).
A gage is a pledge: something of value handed over to stand behind a promise,
and historically the glove thrown down to open a challenge. Both senses fit.
Everything downstream — every verdict, every grant, every unattended
acceptance — rests on that one human moment.
## "Why not just sign the payload yourself?"
Asked by a reviewer, and no document here answered it, which is a gap worth
closing because it is the first question anyone technical will have. Ed25519
is forty lines away in any language. If you want a signed handoff, sign the
tarball and send it.
What that gets you is authenticity. Every part of the gap between that and
this is a local decision the signature cannot make for you:
A signature says a key signed something. It does not say you ever agreed
to hear from that key. The verdict is computed from your allowlist, and
— since this release — from a record that a human compared four word-pairs
with its owner. "Valid signature" and "someone I have confirmed" are
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/warewithall2-gage/)
Source
awesome · https://github.com/warewithall2/gage
Browse by field
MCP servers
Traction
1 ★
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index