
TrustAgent — counterparty verification
io.trust-agentPublished by trust-agent.iov0.1.2Updated Oct 24, 2026
Is this address safe to pay? OFAC sanctions, ERC-8004 reputation, contract analysis.
Overview
Lets an assistant check whether a crypto address is safe to pay by screening sanctions, reputation, and contract risk.
- What you can do
- TrustAgent is a counterparty verification server for crypto payments. It checks addresses against OFAC sanctions lists, looks up ERC-8004 reputation, and analyzes contracts to help judge whether an address is safe to pay. Some tools are free; four paid tools settle per call in USDC over x402 and require a funded Base wallet.
- When to use it
- Use it when an assistant needs to vet a wallet or contract address before sending funds, for example screening a counterparty for sanctions exposure or checking on-chain reputation and contract behavior.
- Requirements
- Runs locally over stdio, typically via the npm package trustagent-mcp, so Node.js is needed. The free tools need no wallet. The paid tools need the secret TRUSTAGENT_WALLET_KEY (a funded Base wallet private key) plus an optional peer dependency, and network access to the service at TRUSTAGENT_URL, which defaults to the hosted deployment.
Installation
In SourceWeft
- Open TrustAgent — counterparty verification in the dashboard and add it to a workspace.
- 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
0Version history
1- v0.1.2LatestSep 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.