BRYDGE MCP Server

Checks whether an agent's actions actually happened, against the destination's own records.

Local serverstdio

What is the BRYDGE MCP Server?

BRYDGE is an MCP integration. Checks whether an agent's actions actually happened, against the destination's own records.

Packages and local setup

The published npm package is brydge-mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares BRYDGE_API_KEY (required): Your BRYDGE API key. It starts with brydge_sk_; issue one in BRYDGE on the Connect page.; BRYDGE_ACTOR (required): The name BRYDGE knows this agent by, such as agent:refund-ops. Mandates are issued to this name.; BRYDGE_URL: Where BRYDGE runs. Leave it unset for BRYDGE's hosted service..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
BRYDGE_API_KEYYour BRYDGE API key. It starts with brydge_sk_; issue one in BRYDGE on the Connect page.Yes
BRYDGE_ACTORThe name BRYDGE knows this agent by, such as agent:refund-ops. Mandates are issued to this name.Yes
BRYDGE_URLWhere BRYDGE runs. Leave it unset for BRYDGE's hosted service.Optional