Skip to main content
Glama

Related Servers

Alternatives to Euclid-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      MCP server for logical reasoning that turns facts into formal proofs using a deterministic inference engine with Prolog.
      8
      63 PyPI
      7
      Apache 2.0
    • F
      license
      A
      quality
      D
      maintenance
      MCP server wrapping SWI-Prolog for symbolic reasoning, enabling coding agents to assert facts and query rules deterministically.
      7
      7
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP-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.
      46
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      57 npm
      213
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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
    • A
      license
      A
      quality
      D
      maintenance
      Structured reasoning MCP server that decomposes problems into atomic steps (premise, reasoning, hypothesis, verification, conclusion) with confidence scoring, live visualization, and approval feedback.
      3
      91
      MIT

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: reason for proving, diagnose for understanding unexpected results, what_if for hypothetical changes, and check_kb for static validation. There is no overlap; an agent can easily select the appropriate tool.

    Naming Consistency5/5

    All tool names use snake_case with imperative verbs or common phrases: reason, diagnose, what_if, check_kb. The naming pattern is consistent and predictable, making it easy for an agent to infer functionality.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to logical reasoning tasks. Each tool serves a critical function without redundancy, and the count is well-suited for its domain.

    Completeness4/5

    The tool surface covers reasoning, diagnostics, hypotheticals, and validation. Minor gaps exist, such as no direct tool to list all facts/rules or permanently modify the knowledge base, but the core workflow is well-supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues