horizon-torn-mcp
Related Servers
Alternatives to horizon-torn-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA TypeScript-based MCP server that integrates with Swagger/OpenAPI specifications to expose API endpoints as tools for Large Language Models (LLMs), enabling natural language interaction with any OpenAPI-compliant API.49MIT
- AlicenseNot gradedqualityAmaintenanceA TypeScript MCP Server exposing the bungie API as natural-language tools.ISC
- AlicenseBqualityDmaintenanceA simple TypeScript MCP server that provides two tools: one for greeting users with a customizable name and another for adding two numbers together.26 npmMIT
- AlicenseNot gradedqualityDmaintenanceA minimal MCP server that auto-generates tools from your OpenAPI spec, optimized for Vercel.19 npm8MIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript-based template for rapidly developing MCP servers with modular tool architecture, built-in validation using Zod schemas, and comprehensive error handling.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceProxy MCP server that translates tool calls into TypeScript code generation, enabling LLMs to orchestrate multi-tool workflows efficiently via code.7 npm14MIT
TDQS
Scored across 205 tools
Many tools have overlapping purposes, e.g., multiple faction, company, and property tools with vague descriptions like 'Get any X selection'. It's very difficult for an agent to distinguish between them.
Naming follows a pattern (horizon_torn_get[Section][Detail]), but there are inconsistencies like 'horizon_torn_getMarketItemMarketItem' (redundant) and mixing of action verbs (get, lookup, etc.).
With 205 tools, the server is extremely bloated. Such a high number overwhelms the agent and makes selection impractical; it should be split into multiple focused servers.
The tool set appears to cover nearly all aspects of the Torn game API, but it includes redundant and overlapping tools (e.g., Generic, Lookup, BasicInformation), which adds noise rather than true coverage.