TrustRail Counterparty Risk

io.github.trustrail-labsPublished by GitHub account trustrail-labsv0.4.1Updated Oct 27, 2026

External counterparty-risk checks and signed receipts for autonomous agents and machine payments.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant run external counterparty-risk checks and obtain signed receipts for agents and machine payments.

What you can do
  • Run external counterparty-risk checks on the parties an agent is about to transact with.
  • Obtain signed receipts that record the outcome of those checks.
  • Support autonomous agents and machine-payment flows with verifiable risk evidence.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant or autonomous agent needs a third-party risk assessment of a counterparty before a machine payment or automated transaction, and wants a signed receipt of that check.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A TrustRail service API key, obtained out of band, must be sent in the X-API-Key header. Network access to the hosted endpoint is required.
Before you install
The server requires a secret API key in the X-API-Key header; keep it out of logs and shared configuration. Counterparty details you submit are sent to a third-party hosted service. The manifest lists no tools, so review what the service does with submitted data before relying on it for payment decisions.

Installation

In SourceWeft

  1. Open TrustRail Counterparty Risk in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.trustrail-labs%2Ftrustrail/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "trustrail-counterparty-risk": {
      "type": "http",
      "url": "https://trustrail-ebon.vercel.app/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.4.1LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.