MCPHub LabRegistrybbartling/open-fdd
bbartling

bbartling/open fdd

Built by bbartling 112 stars

What is bbartling/open fdd?

Fault Detection Diagnostics (FDD) for HVAC datasets

How to use bbartling/open fdd?

1. Install a compatible MCP client (like Claude Desktop). 2. Open your configuration settings. 3. Add bbartling/open fdd using the following command: npx @modelcontextprotocol/bbartling-open-fdd 4. Restart the client and verify the new tools are active.
🛡️ Scoped (Restricted)
npx @modelcontextprotocol/bbartling-open-fdd --scope restricted
🔓 Unrestricted Access
npx @modelcontextprotocol/bbartling-open-fdd

Key Features

Native MCP Protocol Support
Real-time Tool Activation & Execution
Verified High-performance Implementation
Secure Resource & Context Handling

Optimized Use Cases

Extending AI models with custom local capabilities
Automating system workflows via natural language
Connecting external data sources to LLM context windows

bbartling/open fdd FAQ

Q

Is bbartling/open fdd safe?

Yes, bbartling/open fdd follows the standardized Model Context Protocol security patterns and only executes tools with explicit user-granted permissions.

Q

Is bbartling/open fdd up to date?

bbartling/open fdd is currently active in the registry with 112 stars on GitHub, indicating its reliability and community support.

Q

Are there any limits for bbartling/open fdd?

Usage limits depend on the specific implementation of the MCP server and your system resources. Refer to the official documentation below for technical details.

Official Documentation

View on GitHub

Open-FDD

Discord CI MIT License Development Status Python PyPI

<div align="center">

open-fdd logo

</div>

This repository ships the open-fdd rules engine: YAML-defined fault detection on pandas DataFrames (open_fdd.engine). The published PyPI wheel contains only engine and schema modules.

Operator dashboards, HTTP bridges, ingest drivers, and deployment stacks are not bundled. Describe what you need in openfdd.toml, then use skills/ and the local agent shell to generate code under workspace/.


Install from PyPI

pip install "open-fdd[engine]"

Bare import with pandas only: pip install open-fdd (add [engine] for YAML rules and RuleRunner).

Rule authoring: Expression rule cookbook.


Build with skills + agent shell

  1. Copy openfdd.toml.example to openfdd.toml and set [build] targets, drivers, auth, and deploy mode.
  2. Install the shell (local only, not on the engine wheel):
cd packages/openfdd-agent-shell
pip install -e ".[dev]"
  1. From the repo root:
openfdd-agent-shell --repo-root .

The shell loads AGENTS.md, selected skill recipes under skills/, and launches Codex CLI to scaffold only what the manifest requests. Generated apps live in workspace/.


Online documentation

Historical desktop/MCP how-tos under docs/howto/ describe the retired monolith; new integrations should follow skills/.


Develop and test

git clone https://github.com/bbartling/open-fdd.git
cd open-fdd
python3 -m venv .venv
source .venv/bin/activate   # Windows: .venv\Scripts\activate
pip install -U pip
pip install -e ".[dev]"
pytest open_fdd/tests/engine

Optional shim package:

cd packages/openfdd-engine && pip install -e .

Dependencies

  • Python 3.10+ and pip — required: pandas; rule execution adds PyYAML and pydantic via the [engine] extra (NumPy via pandas).
  • Codex CLI on PATH when using the agent shell (codex by default).
  • Node.js only if a generated dashboard skill scaffolds a Vite/React app under workspace/.

License

MIT

Global Ranking

8.5
Trust ScoreMCPHub Index

Based on codebase health & activity.

Manual Config

{ "mcpServers": { "bbartling-open-fdd": { "command": "npx", "args": ["bbartling-open-fdd"] } } }