Key Drivers Mcp

io.github.petrmasaPublished by GitHub account petrmasav0.1.1Updated Oct 24, 2026

MCP server for key driver and feature importance analysis based on rule mining

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

Local MCP server that lets an assistant run key driver and feature importance analysis using rule mining.

What you can do
  • Performs key driver analysis on data supplied to it.
  • Ranks features by importance using rule-mining based methods.
  • Exposes this analysis to the assistant as MCP tools over a local stdio connection.
  • No individual tools are documented in the available listing, so exact operations are not described.
When to use it
Useful when you want an assistant to help identify which variables most influence an outcome in a dataset, for example in exploratory analytics or feature selection discussions, and you prefer the computation to run locally.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package key-drivers-mcp, so a Python environment is needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The listing documents no tools, parameters or data handling, so review the package before use. Analysis runs locally, but any dataset you pass to the assistant is handled by the model in that conversation.

Installation

In SourceWeft

  1. Open Key Drivers Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.