Trust Gate

io.github.BotagramPublished by GitHub account Botagramv1.0.1Updated Oct 24, 2026

Merchant trust verification for agentic commerce. Verify any merchant before autonomous payment.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant check a merchant's trust status through RegisteredBrands.AI before making an autonomous payment.

What you can do
Trust Gate is a local MCP server for merchant trust verification in agentic commerce. According to its registry description, it lets an assistant verify a merchant before an autonomous payment is made. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant is expected to pay or transact with merchants on its own and you want a trust check in the loop first. It is less relevant if payments are always confirmed by a human or if no merchant verification is needed.
Requirements
Runs locally over stdio, installed from the npm package @registeredbrands/trust-gate-mcp, so Node.js is needed. Requires an API key supplied as the RB_API_KEY environment variable, obtained from the provider's dashboard. An optional RB_API_URL variable sets the API base URL, defaulting to the provider's site. Network access to that API is required.
Before you install
The server needs a secret API key, RB_API_KEY, which it sends to the provider's API; keep it out of logs and shared configuration. It is positioned around autonomous payments, so treat any resulting payment action as consequential and keep human review where money can move. The manifest lists no tools, so what it can actually do should be confirmed before relying on it.

Installation

In SourceWeft

  1. Open Trust Gate in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.