A
licenseA
qualityF
maintenanceTrust scoring, scam detection, and EAS attestations for ERC-8004 + x402 agents on Base.
18
56 npm
1
MIT
djd-agent-score-mcp
Related Servers
Alternatives to djd-agent-score-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides trust and reputation tools for AI agent wallets within the x402 payment ecosystem and ERC-8004 agent registry. It enables users to perform wallet reputation lookups, real-time risk assessments, and browse registered agents.4342 npm-
- AlicenseAqualityFmaintenanceCounterparty risk scoring for agentic commerce. Scores wallets, domains, IPs, and companies 0-100 before AI agents transact via x402 micropayments on Base13MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to assess counterparty risk, token danger, and wallet creditworthiness on Base by analyzing contract powers and controlling wallet reputation.MIT
- FlicenseNot gradedqualityDmaintenancePay-per-use AI security and research tools for autonomous agents on Base, enabling honeypot detection, risk assessment, wallet analysis, and yield optimization via the x402 protocol.-
- FlicenseAqualityDmaintenancePay-per-call tools for AI agents including trust checks, due diligence, market data, and human-verified approvals, settled in USDC on Base via the x402 protocol.16-
TDQS
A4.2/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a distinct, non-overlapping purpose. The three score variants (basic, full, refresh) are clearly differentiated by granularity and intent, while check_blacklist, report_fraud, get_badge, and register_agent target completely different resources with no ambiguity.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern (check_blacklist, get_badge, register_agent) or a consistent domain prefix pattern (score_basic, score_full, score_refresh). The only deviation is health_check, which reverses the pattern used by check_blacklist and should ideally be check_health.
Tool Count5/5
Nine tools is an ideal scope for an agent reputation service, covering the full lifecycle: registration, scoring (basic/full/refresh), fraud reporting/checking, discovery (leaderboard), visualization (badge), and system status. No tool feels redundant or superfluous.
Completeness4/5
The surface covers core workflows well: CRUD-like operations for scores and fraud reports, registration, and discovery. Minor gaps exist: no update_agent to modify registered metadata after creation, and no delete/deregister capability, though agents can work around these limitations.
Maintenance
ActivityInactive
ResponsivenessUnresponsive