LSD MCP Server
Related Servers
Alternatives to LSD MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables deep internet research through natural language, supporting stdio and HTTP/SSE modes for flexible integration.3-
- AlicenseAqualityAmaintenanceAn MCP server providing web search, image search, and page scraping tools to LLMs without requiring API keys.312MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables web search and document retrieval capabilities through Tavily API and LangConnect vector database, supporting AI agents in gathering information for comprehensive report generation.23-
- AlicenseNot gradedqualityDmaintenanceMCP tool server that gives any AI agent the ability to search, scrape, and analyze content across the internet.42MIT
- FlicenseAqualityDmaintenanceAn MCP server providing tools for web research, code review, and concept explanation, callable by any MCP-compatible client.3-
- AlicenseAqualityDmaintenanceAn MCP server that provides real-time web search to AI agents via a pay-per-search USDC microtransaction system.529 npm1MIT
TDQS
Scored across 3 tools
The tools have unclear boundaries and overlapping purposes. 'brave_search' and 'find_trips' could both be interpreted as search tools, with the latter's lack of description making it ambiguous whether it searches for trips or performs another function. 'run_lsd' is completely opaque without a description, potentially overlapping with execution or processing roles.
The naming is mixed but readable. 'brave_search' and 'find_trips' follow a verb_noun pattern, while 'run_lsd' uses a verb_prefix style. There is no chaotic mixing of cases, but the conventions are not fully consistent across all tools.
With only 3 tools, the server feels thin for a general-purpose 'LSD MCP Server', suggesting an incomplete surface. The lack of descriptions for two tools makes it hard to assess scope, but the count is borderline too few for meaningful coverage of any substantial domain.
The server is severely incomplete. Based on the tool names, it appears to cover search and execution, but with no descriptions for 'find_trips' and 'run_lsd', there are significant gaps. It lacks any CRUD operations, lifecycle management, or clear domain coverage, making it impossible for agents to perform coherent workflows.