Euclid-MCP
Related Servers
Alternatives to Euclid-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceDeterministic logical reasoning server for MCP clients that compiles facts, rules, and queries to Prolog and returns exact answers with proof trees.4MIT
- FlicenseAqualityDmaintenanceMCP server wrapping SWI-Prolog for symbolic reasoning, enabling coding agents to assert facts and query rules deterministically.77-
- AlicenseNot gradedqualityBmaintenanceMCP-Logic is a server that provides AI systems with automated reasoning capabilities, enabling logical theorem proving and model verification using Prover9/Mace4 through a clean MCP interface.46MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for the Pyke logic programming engine that enables LLMs to perform logical reasoning using knowledge bases with facts, rules, and queries. It supports session management, forward chaining inference, and bulk loading of programs in Logic-LLM format.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives LLMs access to formal verification via Z3 and SWI-Prolog, plus tree-sitter-based source code analysis. Translates natural language problems into formal logic using a template-based pipeline, verifies results with mathematical certainty, and analyzes call graphs for reachability, dead code, and impact analysis.26 npm213Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes the DALI2-Agent-Brain symbolic verification system as tools, allowing MCP clients to submit reasoning problems for formal Prolog-based verification.-
TDQS
Scored across 8 tools
Several tools overlap in purpose: reason, explain, and diagnose all deal with explaining or producing query outcomes, making it hard to know which to call. diagnose even includes a 'why' mode that duplicates explain. The KB management tools are clear, but the reasoning tools blur together.
Naming is mixed: some tools use bare verbs (reason, explain, diagnose), some use snake_case verb_noun (register_kb, unregister_kb, list_kbs, check_kb), and what_if deviates entirely from the pattern. The style is inconsistent across the tool set.
Eight tools is a well-scoped size for a knowledge-base reasoning server. Each tool contributes to either KB lifecycle management or query/reasoning workflows without feeling padded or sparse.
The KB lifecycle is covered well: register, unregister, list, and check. Reasoning coverage includes query, explanation, diagnosis, and what-if analysis. Minor gap: there is no way to retrieve the actual content of a registered KB, only metadata, which agents may need for inspection.