BRYDGE
NPM · BRYDGE-MCP · SCANNED SEP 27
Checks whether an agent's actions actually happened, against the destination's own records.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 789 tokens (~157/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the BRYDGE MCP server?
BRYDGE runs locally as an npm package, launched with npx -y brydge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · brydge-mcp
claude mcp add com-brydge-ai-brydge -- npx -y brydge-mcp
{
"mcpServers": {
"com-brydge-ai-brydge": {
"command": "npx",
"args": [
"-y",
"brydge-mcp"
]
}
}
} {
"servers": {
"com-brydge-ai-brydge": {
"command": "npx",
"args": [
"-y",
"brydge-mcp"
]
}
}
} codex mcp add com-brydge-ai-brydge -- npx -y brydge-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-brydge-ai-brydge": {
"type": "local",
"command": [
"npx",
"-y",
"brydge-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-brydge-ai-brydge --command npx --arg -y --arg brydge-mcp
mcp_servers:
com-brydge-ai-brydge:
command: "npx"
args: ["-y", "brydge-mcp"] {
"McpServers": {
"com-brydge-ai-brydge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"brydge-mcp"
]
}
}
} assistant mcp add com-brydge-ai-brydge -t stdio -c npx -a -y brydge-mcp
{
"mcpServers": {
"com-brydge-ai-brydge": {
"command": "npx",
"args": [
"-y",
"brydge-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 26 Sept 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Analysed npm/brydge-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brydge_get_finding What BRYDGE has found so far ~72
What BRYDGE has already found about an action, without reading the records again. Free. BRYDGE checks each action by itself once the destination's reporting window has passed; until then this says PENDING.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | yes | The authorization id brydge_supervise returned for the action. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentAgreed | boolean|null | yes | – |
| authorization | string | yes | – |
| because | string | yes | – |
| checkedAt | string|null | yes | – |
| claimed | string|null | yes | – |
| externalRef | string|null | yes | – |
| reason | string|null | yes | – |
| replayed | boolean | yes | – |
| state | string | yes | – |
No examples provided.
brydge_get_headroom How much you may do without a person ~80
How many actions of this kind you may take in any 24 hours before a person is asked, how many are left, and what raises or lowers that. Every report BRYDGE checks and finds true raises it.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The kind of work, as it is set up in BRYDGE, such as refund. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| actions | number | yes | – |
| earned | number | yes | – |
| lowers | string | yes | – |
| raises | string | yes | – |
| remaining | number | yes | – |
| says | string | yes | – |
| used | number | yes | – |
No examples provided.
brydge_report_outcome Report what happened ~138
Tell BRYDGE what you believe happened after you carried out an allowed action. BRYDGE keeps your report beside what it finds in the destination's records; the report never changes the finding.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | yes | The authorization id brydge_supervise returned for the action. |
| outcome | string | yes | SUCCEEDED: it was carried out and did what it was meant to. FAILED: the destination refused it or errored. REVERSED: it happened and was undone. CORRECTED: it happened and had to be fixed afterwards. |
| said | string | – | What the destination said, in its own words. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | yes | – |
| recorded | string | yes | – |
No examples provided.
brydge_supervise Ask BRYDGE before acting ~219
Ask BRYDGE whether you may take an action, before you take it. ALLOWED returns an authorization id: carry the action out and write that id into the record it creates, where the destination keeps it (for a Stripe refund: metadata.brydge_authorization). ESCALATED means a person decides: do not carry it out.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The kind of work, as it is set up in BRYDGE, such as refund. |
| facts | object | – | What BRYDGE's rules judge the action by, such as {"amount": 4200}. BRYDGE compares a fact named amount with the amount in the destination's record, so give it in the same units. |
| idempotency_key | string | yes | A name for this one intended action, such as refund:ch_123. Send the same value if you retry the same action; never reuse it for a different one. |
| target | string | yes | What the work acts on: the charge, order or ticket id. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | yes | – |
| because | string | yes | – |
| decision | string | yes | – |
| replayed | boolean | yes | – |
| unobserved | array | yes | – |
No examples provided.
brydge_verify Check the work actually happened ~122
Check whether an action actually happened. BRYDGE reads the destination system's own records now, with its own credential, and compares them with what it permitted. Only VERIFIED means it happened as permitted; FAILED, MISMATCH, UNKNOWN (BRYDGE could not tell) and PENDING (still in progress) are not. Use it before you tell anyone the work is done. A check that finds something new is billed; asking again when nothing has changed is free.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | yes | The authorization id brydge_supervise returned for the action. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentAgreed | boolean|null | yes | – |
| authorization | string | yes | – |
| because | string | yes | – |
| checkedAt | string|null | yes | – |
| claimed | string|null | yes | – |
| externalRef | string|null | yes | – |
| reason | string|null | yes | – |
| replayed | boolean | yes | – |
| state | string | yes | – |
No examples provided.
What is the BRYDGE MCP server?
BRYDGE is an MCP server listed in the public MCP registry as com.brydge-ai/brydge. Checks whether an agent's actions actually happened, against the destination's own records. This page covers its npm package (brydge-mcp).
Is the BRYDGE MCP server safe to use?
BRYDGE scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BRYDGE MCP server expose?
BRYDGE exposes 5 tools: brydge_supervise, brydge_report_outcome, brydge_verify, brydge_get_finding, brydge_get_headroom. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Is the BRYDGE MCP server still maintained?
BRYDGE is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the BRYDGE MCP server under?
BRYDGE declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.