AgentScore MCP Server
Related Servers
Alternatives to AgentScore MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides protocol-neutral market intelligence for the AI agent economy, with read-only tools to search agents, retrieve details and histories, compare agents, list categories, view category rankings, and access methodology.-
- AlicenseAqualityCmaintenanceEnables MCP clients to search and inspect AI agents registered in ERC-8004 registries, retrieving profiles, owners, feedback, validations, and USDC-weighted trust scores without requiring a wallet or API key.672 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and interact with onchain agent infrastructure on Base, including identity, micropayments, and tool capabilities via MCP.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to assess counterparty risk, token danger, and wallet creditworthiness on Base by analyzing contract powers and controlling wallet reputation.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query Base on-chain data such as balances, token metadata, transactions, gas, names, prices, transfers, and contract details through paid MCP tools using x402 payments.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up token risk verdicts and ERC20 facts, wallet snapshots, gas prices, transaction summaries, and Basename resolution on the Base network. Each call is paid in USDC over x402 from a dedicated wallet the user controls, with per-call price caps and a session budget.51 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: getAgentHistory retrieves historical data, getAgentScore provides current reputation metrics, and listRegisteredAgents enumerates agents with optional filtering. There is no overlap in functionality, and the descriptions clearly differentiate their roles.
The naming is mixed: getAgentHistory and getAgentScore follow a consistent verb_noun pattern, but listRegisteredAgents uses a different verb style ('list' vs. 'get'). While all names are readable, the inconsistency in verb choice reduces predictability.
With only 3 tools, the set feels thin for a server named 'AgentScore MCP Server', which suggests a broader scope for managing agent scores and data. While the tools cover basic retrieval and listing, the count may be insufficient for comprehensive operations like updating scores or managing registrations.
The tool surface is significantly incomplete for an agent scoring system. It only includes read operations (get and list), with no ability to create, update, or delete scores or agents. This leaves obvious gaps in CRUD coverage, likely causing agent failures in scenarios requiring data modification.