Skip to main content
Glama
unixlamadev-spec

aiprox-mcp

by unixlamadev-spec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to aiprox-mcp

No user-submitted related servers found.

    Related Servers

    • x402-discovery

      rplryan
      A
      license
      Not graded
      quality
      D
      maintenance
      Discovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.
      MIT

    • Moltjiji

      qionf
      A
      license
      Not graded
      quality
      D
      maintenance
      An agent-to-agent marketplace where AI agents discover, hire, and pay each other in USDC on Base. Agents list services, post jobs, submit proposals, and invoke each other's capabilities — all through API, MCP, or A2A protocol.
      MIT
    • com.ausca/agent-services by auscahq

      com.ausca/agent-servicesofficial

      auscahq
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover, pay for, and invoke x402-priced services such as document OCR, document analysis, media transcription, remote browser sessions, and receive-only email inboxes using USDC on Base, with no API keys and receipt-backed results.
      37
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: find_agent searches by task description, get_agent retrieves details by name, list_agents shows all agents, register_agent adds new ones, and get_spec provides technical documentation. However, find_agent and list_agents could potentially be confused since both involve discovering agents, though their different input parameters (task description vs. filtering) help distinguish them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: find_agent, get_agent, get_spec, list_agents, and register_agent. The naming is predictable and readable throughout, with no deviations in style or convention.

    Tool Count5/5

    With 5 tools, this server is well-scoped for managing an agent registry. The count is appropriate for the domain, covering key operations like discovery, retrieval, listing, registration, and specification access without being overly sparse or bloated.

    Completeness4/5

    The tool set covers core CRUD operations for an agent registry: create (register_agent), read (get_agent, list_agents, find_agent), and documentation (get_spec). A minor gap is the lack of update or delete tools for modifying or removing registered agents, but agents can likely work around this given the domain's likely administrative controls.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources