TrustAgent — counterparty verification
NPM · TRUSTAGENT-MCP
Is this address safe to pay? OFAC sanctions, ERC-8004 reputation, contract analysis.
Available components
Last scanned (9 hours ago)
Scores higher than 48% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 61 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 318 tokens (~106/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
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 5 Nov 2026 · Analysed npm/trustagent-mcp@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
trustagent_check_address Check an address (free) ~145
Screen an EVM address, contract or ERC-8004 agent before paying it. Returns a risk band, an OFAC sanctions-list verdict, flag counts and a confidence score. Free — no wallet or payment needed. Use this first for any "is this safe to pay / interact with" question. A sanctions hit is a strong signal warranting review; a miss is not legal clearance.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM address (0x…), an ERC-8004 agentId, or an eip155:<chain>:<registry>/<id> identifier |
| type | string | – | Optional hint about what the subject is. Defaults to auto-detection. |
No output schema declared.
No examples provided.
trustagent_pricing What the paid tools cost (free) ~52
List the paid endpoints, their prices in USDC, and the free-trial allowance. Useful for deciding whether a deeper check is worth paying for, and for explaining costs to a user before spending their money.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trustagent_resolve_agent Resolve an ERC-8004 agent (free) ~121
Look up an ERC-8004 agent identity: its owner, payout wallet, registration file and a liveness classification saying whether it is a working agent or an unactivated placeholder. Accepts an agentId, an eip155 identifier, or an address that owns an agent. Free. Returns 404 only when the registry index is complete, so an absent answer is never a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| subject | string | yes | agentId (e.g. "60015"), eip155:<chain>:<registry>/<id>, or an owner address |
No output schema declared.
No examples provided.
How do I install the TrustAgent — counterparty verification MCP server?
TrustAgent — counterparty verification runs locally as an npm package, launched with npx -y trustagent-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 · trustagent-mcp
claude mcp add io-trust-agent-trustagent-mcp -- npx -y trustagent-mcp
What is the TrustAgent — counterparty verification MCP server?
TrustAgent — counterparty verification is an MCP server listed in the public MCP registry as io.trust-agent/trustagent-mcp. Is this address safe to pay? OFAC sanctions, ERC-8004 reputation, contract analysis. This page covers its npm package (trustagent-mcp).
Is the TrustAgent — counterparty verification MCP server safe to use?
TrustAgent — counterparty verification scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 TrustAgent — counterparty verification MCP server expose?
TrustAgent — counterparty verification exposes 3 tools: trustagent_check_address, trustagent_resolve_agent, trustagent_pricing. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.
Is the TrustAgent — counterparty verification MCP server still maintained?
TrustAgent — counterparty verification is still listed as active in the MCP registry. We last reached this channel on 5 November 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 TrustAgent — counterparty verification MCP server under?
TrustAgent — counterparty verification declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.