microtensor-mcp
Related Servers
Alternatives to microtensor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceMCP 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.54MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides 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 npm1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables agents to query real-time OpenAPI documentation of backend services, providing tools to list services, endpoints, and schemas via MCP.-

GPTProto MCPofficial
AlicenseAqualityCmaintenanceEnables AI hosts to discover GPTProto models, retrieve live pricing, make documented API requests, submit custom generations, and poll asynchronous tasks through local MCP tools.99 npmMIT- FlicenseNot gradedqualityAmaintenanceEnables 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
Scored across 3 tools
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.
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.
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.
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.