Skip to main content
Glama
tadas-github

a2asearch-mcp

by tadas-github
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to a2asearch-mcp

No user-submitted related servers found.

    Related Servers

    • remoteopenclaw-mcp

      aidevelopers2
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search a directory of 13,870+ MCP servers, 4,384+ agent skills, and plugins from Remote OpenClaw, returning install commands directly.
      3
      31 npm
      4
      MIT

    • getagentictools MCP server

      dmoka
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.
      MIT

    • claude-oracle-mcp

      Vvkmnn
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for discovering Claude Code skills, plugins, and MCP servers by searching 15,000+ resources from 17 registries, GitHub, and the web with zero setup.
      3
      26 npm
      3
      MIT
    • MCPfinder by mcpfinder

      MCPfinderofficial

      mcpfinder
      A
      license
      Not graded
      quality
      A
      maintenance
      AI-first MCP server discovery tool that enables agents to search, inspect, and install MCP servers from multiple registries.
      12
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_agent retrieves detailed information for a specific agent, list_agents provides a filtered browse of agents by category, and search_agents performs a broader search across the directory. There is no overlap in functionality, making tool selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_agent, list_agents, search_agents) with clear, descriptive verbs and pluralization where appropriate. This uniformity aids in predictability and readability.

    Tool Count4/5

    With 3 tools, the count is slightly low but reasonable for the server's purpose of searching and browsing agents. It covers core operations (get, list, search), though additional tools like update or delete might be expected if the domain included management capabilities.

    Completeness4/5

    The tool set provides comprehensive coverage for searching and browsing agents, with no obvious gaps in this domain. However, it lacks CRUD operations (e.g., create, update, delete), which might be expected if the server also supported agent management, but based on the descriptions, the focus appears to be on discovery.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources