Skip to main content
Glama

Related Servers

Alternatives to microtensor-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.
      3 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI hosts to discover GPTProto models, retrieve live pricing, make documented API requests, submit custom generations, and poll asynchronous tasks through local MCP tools.
      9
      9 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to discover, evaluate, and serve task-specialist models (embeddings, reranking, classification, extraction) with OpenAI-compatible endpoints and MCP tools for routing, embedding, reranking, and extraction.
      -

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are largely distinct: ask_specialist performs inference, list_models enumerates models, and routing_tasks enumerates task routes. list_models and routing_tasks are both read-only listing tools, so there is mild overlap, but the descriptions differentiate model attributes from task-to-specialist routing.

    Naming Consistency3/5

    ask_specialist and list_models follow a clean verb_noun pattern, but routing_tasks is a noun phrase with no verb and breaks the convention. The set is readable but uses mixed styles.

    Tool Count3/5

    With only 3 tools, the surface is thin for what appears to be a routing/inference service. Each tool earns its place, but the count is borderline minimal for the implied scope.

    Completeness3/5

    Core actions (ask, list models, list routes) are covered, but there is no way to manage or inspect pins even though ask_specialist references them, and no tool to query individual model or routing details. Notable gaps exist in the lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues