Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.bch1212/agenttrust

NPM · AGENTTRUST-MCP

Trust scores & reputation for the agent-to-agent economy. Verify A2A counterparties.

Available components

0 this week 87 Trust /100

Last scanned (3 minutes ago)

Scores higher than 91% of npm servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to bch1212/agenttrust-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 175 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 668 tokens (~55/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
Changelog

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.

  • 5 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 25 Oct 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +1
    • Stability: 0.90 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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/agenttrust-mcp@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo bch1212/agenttrust-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/bch1212/agenttrust-mcp/.github/workflows/publish-mcp.yml@refs/heads/main
Rekor log index 1524482382
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7b3625660eb80c5494e112511e10ee2c32a99c12be1737f82456d53cff98e93fa8be72bef8556d77a6977cf947691aae14d00a30de0d412bfa6609084

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~668 tokens

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 →

Tool Tokens
dispute_transaction ~58

File a dispute on a transaction. Reporter must be a counterparty (from_agent or to_agent).

NameTypeReqDescription
evidencestring––
reasonstringyes–
reporter_idstringyes–
tx_idstringyes–

No output schema declared.

No examples provided.

endorse_agent ~70

Endorse another agent in one of four categories: quality, reliability, speed, domain. Each endorsement adds 10 points (cap 200).

NameTypeReqDescription
endorsed_idstringyes–
endorsement_typestringyes–
endorser_idstringyes–
notesstring––

No output schema declared.

No examples provided.

get_agent_profile ~38

Public read. Returns full profile + recomputed trust score, tier, and stats for the named agent.

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

get_leaderboard ~40

Public read. Top-N agents by trust score, optionally filtered by capability category.

NameTypeReqDescription
categorystring––
limitinteger––

No output schema declared.

No examples provided.

get_transaction_history ~46

Public read. Paginated transaction list for an agent, most recent first.

NameTypeReqDescription
agent_idstringyes–
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

get_trust_score ~52

Public read. Returns trust score (0–1000), tier (PLATINUM/GOLD/SILVER/BRONZE/NEW), and category breakdown.

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

record_transaction ~81

Record an A2A transaction (success or failure). Recomputes both sides' trust scores. Both parties must already be registered.

NameTypeReqDescription
amount_usdnumberyes–
descriptionstring––
from_agentstringyes–
metadataobject––
successbooleanyes–
to_agentstringyes–

No output schema declared.

No examples provided.

register_agent ~69

Register a new agent with a UUID, name, and capability declaration. Returns an agent_token. Required for write tools.

NameTypeReqDescription
agent_idstringyes–
capabilitiesarray––
descriptionstring––
namestringyes–
operator_urlstring––

No output schema declared.

No examples provided.

report_agent ~53

File an out-of-band abuse report (separate from a transaction dispute).

NameTypeReqDescription
evidencestring––
reasonstringyes–
reported_idstringyes–
reporter_idstringyes–

No output schema declared.

No examples provided.

resolve_dispute ~50

Admin-only. Resolve an open dispute. Outcome ∈ {reporter, respondent, invalid}.

NameTypeReqDescription
dispute_idstringyes–
notesstring––
outcomestringyes–

No output schema declared.

No examples provided.

search_agents ~62

Public read. Search agents by capability filter, minimum trust score, or verified flag. Ranked by score desc.

NameTypeReqDescription
capabilitiesarray––
limitinteger––
min_trust_scoreinteger––
verified_onlyboolean––

No output schema declared.

No examples provided.

verify_agent ~49

Admin-only. Operator-verifies an agent (DNS, KYC, or platform check). +100 bonus to trust score.

NameTypeReqDescription
agent_idstringyes–
verification_typestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.bch1212/agenttrust MCP server?

io.github.bch1212/agenttrust runs locally as an npm package, launched with npx -y agenttrust-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 · agenttrust-mcp

# add to Claude Code
claude mcp add bch1212-agenttrust -- npx -y agenttrust-mcp
Common questions

What is the io.github.bch1212/agenttrust MCP server?

io.github.bch1212/agenttrust is an MCP server listed in the public MCP registry as io.github.bch1212/agenttrust. Trust scores & reputation for the agent-to-agent economy. Verify A2A counterparties. This page covers its npm package (agenttrust-mcp).

Is the io.github.bch1212/agenttrust MCP server safe to use?

io.github.bch1212/agenttrust scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.bch1212/agenttrust MCP server expose?

io.github.bch1212/agenttrust exposes 12 tools: register_agent, get_agent_profile, get_trust_score, record_transaction, dispute_transaction, and 7 more. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.

Is the io.github.bch1212/agenttrust MCP server still maintained?

io.github.bch1212/agenttrust 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 io.github.bch1212/agenttrust MCP server under?

io.github.bch1212/agenttrust declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.