Lithic MCP Server
Related Servers
Alternatives to Lithic MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceTypeScript implementation of the Model Context Protocol that standardizes how LLMs connect to data sources and tools, eliminating vendor lock-in and simplifying AI integration.51 npmISC
- AlicenseNot gradedqualityCmaintenanceA TypeScript implementation of a Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and CRUD operations.2MIT
- AlicenseNot gradedqualityCmaintenanceA TypeScript implementation of a Model Context Protocol server that enables language models to securely query PostgreSQL databases, including those behind SSH bastion tunnels.12 npm1MIT
- -licenseNot gradedqualityNot gradedmaintenanceA TypeScript implementation of a Model Context Protocol server that enables real-time communication with LLM clients using Server-Sent Events (SSE) for transport and Bearer Token authentication for security.-
- -licenseNot gradedqualityDmaintenanceA TypeScript implementation of a Model Context Protocol server and client that enables interaction with language models (specifically Mistral running on Ollama).-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implemented in TypeScript that provides resources, tools (calculator, weather, timestamp), and prompts for integration with LLMs.221 npmISC
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_resource retrieves a single resource by ID, while list_resources retrieves multiple resources of a type. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (get_resource and list_resources), using snake_case and clear action verbs. The naming is perfectly predictable and uniform.
With only 2 tools, the server feels too thin for a general-purpose resource management domain. It lacks essential operations like create, update, or delete, making it incomplete for typical CRUD workflows.
The tool surface is severely incomplete for resource management. It only supports read operations (get and list), missing create, update, and delete capabilities, which are fundamental for a full lifecycle.