MCP-T trust scoring protocol for agent authorization#541
MCP-T trust scoring protocol for agent authorization#541arkavo-com wants to merge 2 commits intomainfrom
Conversation
Implements the MCP-T spec (v0.1.0-draft) from Percival-Labs/mcp-t as an L1 trust provider. Maps existing agent behavioral scoring (BetaPrior, AntiPatternStore) to MCP-T trust dimensions and exposes five JSON-RPC methods: trust/query, trust/verify, trust/history, trust/providers, trust/publish. New arkavo-trust crate with RFC 8785 JCS canonicalization, Ed25519 signing over canonical JSON, SQLite persistence following the arkavo-memory store pattern, and 55 passing tests. Ref: decentralized-identity/trusted-ai-agents#38 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Spec Coverage Report
Quality Gate
Uncovered Scenarios (454)
|
CI requires version increment on PRs and license field for dependency audit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The MCP-T trust scoring integration with behavioral signals (BetaPrior, AntiPatternStore, LearningVelocity) is a thoughtful design — mapping real agent behavior to trust dimensions is more meaningful than static credentials. For the
The HCS-20 auditable points standard provides verifiable trust scores on Hedera consensus — these could compose with your behavioral dimensions as an additional trust provider in the Our Go SDK would integrate cleanly with arkavo-trust since both are in the Rust/Go ecosystem. Happy to collaborate. |
|
The MCP-T trust scoring implementation is clean — mapping behavioral signals to the 6 trust dimensions is a thoughtful design. One gap worth noting: trust scores are only useful if they are portable and verifiable. If Agent A earns a high trust score in one arkavo deployment, and then needs to interact with a different system, that score does not transfer. The agent starts from zero trust everywhere else. At HOL, our HCS-20 auditable points/rewards standard addresses exactly this — trust history is recorded on-chain and verifiable by any system. An agent trust score from arkavo could be anchored to a UAID, making it:
The arkavo trust scores (6 dimensions) could be published as HCS-20 events linked to the agent UAID. Other systems can then consume them without being arkavo deployments. Our TypeScript SDK could integrate with the arkavo-trust crate. Happy to collaborate. |
Summary
arkavo-trustcrate implementing the MCP-T spec (v0.1.0-draft) as an L1 trust providerA2aRpctrait:trust/query,trust/verify,trust/history,trust/providers,trust/publishModules
types.rsjcs.rssigning.rsmapper.rsservice.rsstore.rshandlers/trust.rsTest plan
cargo test -p arkavo-trust— 55 tests passingcargo clippy -p arkavo-trust -p arkavo-server -- -D warnings— cleancargo fmt -- --check— cleancargo build -p arkavo-server -q— builds successfullyRef: decentralized-identity/trusted-ai-agents#38
🤖 Generated with Claude Code