fispro-mcp
Related Servers
Alternatives to fispro-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server for logical reasoning that turns facts into formal proofs using a deterministic inference engine with Prolog.867 PyPI7Apache 2.0
- AlicenseBqualityDmaintenanceMCP server that connects AI clients to a local MiroFish instance for document-driven multi-agent simulations and prediction report generation.50MIT
- AlicenseAqualityDmaintenanceMCP server for FSM report migration analysis, providing fuzzy search of report mappings, pattern registry, and columnar report generation.7MIT
- 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
- AlicenseAqualityDmaintenanceDeterministic logical reasoning server for MCP clients that compiles facts, rules, and queries to Prolog and returns exact answers with proof trees.4MIT
- 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.47MIT
TDQS
Scored across 7 tools
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).
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.
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.
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.