Skip to main content
Glama

Related Servers

Alternatives to AgentScore MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides 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.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      6
      112 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      495 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      4
      342 npm
      -

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues