Skip to main content
Glama
Kofi04

fispro-mcp

by Kofi04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fispro-mcp

No user-submitted related servers found.

    Related Servers

    • Euclid-MCP

      Euclid-BG
      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
      67 PyPI
      7
      Apache 2.0

    • ReAI MCP Server

      van0219
      A
      license
      A
      quality
      D
      maintenance
      MCP server for FSM report migration analysis, providing fuzzy search of report mappings, pattern registry, and columnar report generation.
      7
      MIT

    • Pyke MCP Server

      NewJerseyStyle
      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

    • Euclid-MCP

      snegi26
      A
      license
      A
      quality
      D
      maintenance
      Deterministic logical reasoning server for MCP clients that compiles facts, rules, and queries to Prolog and returns exact answers with proof trees.
      4
      MIT

    • MCP-Logic

      angrysky56
      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.
      47
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: environment check, file listing, system description, single inference, inference explanation, dataset inference, and validation. There is no overlap; even infer and explain_inference are clearly separated by output (results vs. reasoning).

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun or verb pattern (check_environment, list_fis, describe_fis, infer, explain_inference, infer_dataset, validate_fis). The only minor deviation is the bare verb 'infer', but it is clean and understandable in context.

    Tool Count5/5

    Seven tools is a well-scoped count for a fuzzy inference system server. Each tool covers a distinct operation needed to work with FIS files, and none feel redundant or excessive.

    Completeness5/5

    The tool surface covers the full workflow for the domain: preparing/checking the environment, discovering and inspecting FIS files, running single and batch inferences, understanding inference results, and validating system integrity. No obvious dead ends or missing core operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources