BRYDGE runs on your own machine — the client starts it, so there is no endpoint to ping. 28 installs a week from npm. Last commit 3 Oct 2026.
Checks whether an agent's actions actually happened, against the destination's own records.
Nothing serious here today
Today is the operative word: we check BRYDGE every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add brydge -e 'BRYDGE_API_KEY=<BRYDGE_API_KEY>' -e 'BRYDGE_ACTOR=<BRYDGE_ACTOR>' -- npx -y brydge-mcp{
"mcpServers": {
"brydge": {
"command": "npx",
"args": [
"-y",
"brydge-mcp"
],
"env": {
"BRYDGE_ACTOR": "<BRYDGE_ACTOR>",
"BRYDGE_API_KEY": "<BRYDGE_API_KEY>"
}
}
}
}[mcp_servers.brydge]
command = "npx"
args = ["-y", "brydge-mcp"]
env = { BRYDGE_API_KEY = "<BRYDGE_API_KEY>", BRYDGE_ACTOR = "<BRYDGE_ACTOR>" }{
"mcpServers": {
"brydge": {
"command": "npx",
"args": [
"-y",
"brydge-mcp"
],
"env": {
"BRYDGE_ACTOR": "<BRYDGE_ACTOR>",
"BRYDGE_API_KEY": "<BRYDGE_API_KEY>"
}
}
}
}{
"servers": {
"brydge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"brydge-mcp"
],
"env": {
"BRYDGE_ACTOR": "<BRYDGE_ACTOR>",
"BRYDGE_API_KEY": "<BRYDGE_API_KEY>"
}
}
}
}Put your own values in place of
<BRYDGE_API_KEY> (Your BRYDGE API key. It starts with brydge_sk_; issue one in BRYDGE on the Connect page), <BRYDGE_ACTOR> (The name BRYDGE knows this agent by, such as agent:refund-ops. Mandates are issued to this name).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BRYDGE_URL (Where BRYDGE runs. Leave it unset for BRYDGE's hosted service).
Alternatives to BRYDGE
same job, measured the same wayCrash-test your AI agent on real professional decisions, graded against what actually happened.
Verify agent actions against the system of record and get signed completion receipts.
Checks a coding agent's handback against the pull request's GitHub record. No model decides.
Checks legal citations against the official register they should come from, and records it.
Checks whether an ERC-8004-registered agent is actually alive right now via a real MCP handshake
Gives an agent one tool, submit_confession, and no nudge, then records whether it uses it.
The drift harness as an MCP server. Offline, no key — a fixed reference an agent checks against.
Check an agent action against its operator's mandate before acting: permit, deny or escalate.
BRYDGE — questions
Answers built from our own checks of this server.