Enterprise DNAEnterprise DNA

MCP Servers

leap-laboratories/discovery-engine

Discovery Engine — find novel, statistically validated patterns in tabular data

Our verdict

Not reviewed yet

We have not reviewed leap-laboratories/discovery-engine yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About leap-laboratories/discovery-engine

Discovery Engine is a Python library that identifies novel, statistically validated patterns in tabular data. It applies statistical tests to filter out noise and surface meaningful relationships.

Best for

Data scientists and researchers who need a lightweight tool for statistically validated pattern mining in tabular datasets.

Use cases

  • Exploring hidden correlations in structured datasets
  • Validating candidate patterns with statistical rigor
  • Automating pattern discovery in research or analytics pipelines

Notes

6 stars on GitHub. Last updated 2026-05-29. Licensed MIT.

Pros

  • Open source and written in Python for easy integration
  • Focuses on statistical validation to reduce false positives
  • Lightweight with no external dependencies beyond standard data science libraries

Cons

  • Very low community adoption (6 stars) suggests limited testing and support
  • Documentation and examples may be sparse
  • Narrowly scoped to tabular data pattern discovery

Key facts

What we have checked

Days since the last commit
36
Checked GitHub
GitHub forks
0
Checked GitHub
GitHub stars
7
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

pip install discovery-engine-api

Tools exposed

  • patient_id

Clients the listing names (not checked here)

ChatGPT

Install

Add leap-laboratories/discovery-engine to your client

Server verified

Checked : our lab installed version 1.0.1, started it and listed its 14 tools. How the lab checks

Maker? Show the badge on your own README or site

Our lab passed this server, so it can carry "Server verified on Enterprise DNA". The badge is a live link: it disappears if a later check fails, and it is never for sale.

HTML

<a href="https://enterprisedna.co/directories/mcp/leap-laboratories-discovery-engine"><img src="https://enterprisedna.co/directories/badge/mcp-servers/leap-laboratories-discovery-engine.svg" alt="Server verified on Enterprise DNA, checked 12 Nov 2026" width="300" height="44"></a>

Markdown

[![Server verified on Enterprise DNA, checked 12 Nov 2026](https://enterprisedna.co/directories/badge/mcp-servers/leap-laboratories-discovery-engine.svg)](https://enterprisedna.co/directories/mcp/leap-laboratories-discovery-engine)

Claude Code

Config checked

Run in your terminal (remote server)

claude mcp add --transport http discovery-engine https://disco.leap-labs.com/mcp --header 'Authorization: Bearer YOUR_DISCOVERY_ENGINE_TOKEN'

Needs DISCOVERY_ENGINE_TOKEN: replace each YOUR_ value with your own.

Version 1.0.1 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Cursor

Config checked

Add to .cursor/mcp.json (remote server)

{
  "mcpServers": {
    "discovery-engine": {
      "url": "https://disco.leap-labs.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_DISCOVERY_ENGINE_TOKEN"
      }
    }
  }
}

Needs DISCOVERY_ENGINE_TOKEN: replace each YOUR_ value with your own.

Version 1.0.1 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (remote server)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "discovery-engine-token",
      "description": "Bearer token with disco_ API key (format: Bearer disco_...)",
      "password": true
    }
  ],
  "servers": {
    "discovery-engine": {
      "type": "http",
      "url": "https://disco.leap-labs.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:discovery-engine-token}"
      }
    }
  }
}

Needs DISCOVERY_ENGINE_TOKEN: replace each YOUR_ value with your own.

Version 1.0.1 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (remote server)

[mcp_servers.discovery-engine]
url = "https://disco.leap-labs.com/mcp"
bearer_token_env_var = "DISCOVERY_ENGINE_TOKEN"

Needs DISCOVERY_ENGINE_TOKEN: replace each YOUR_ value with your own.

Version 1.0.1 · From the Official MCP registry, read · Format checked against Codex's config docs

  • Claude Desktop: Its config file takes local servers only; a remote server is added in the app as a connector.
  • ChatGPT: ChatGPT connects only to remote servers that need no API key.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What leap-laboratories/discovery-engine connects to

4 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRemote server, version 1.0.1Config checkedClaude Code docs
CursorClientInstall recipe matches the client's documented formatRemote server, version 1.0.1Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRemote server, version 1.0.1Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRemote server, version 1.0.1Config checkedCodex docs

Stars and usage

How leap-laboratories/discovery-engine is growing

GitHub stars

7 to 7

stars. 29 Oct 2026 to 12 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is leap-laboratories/discovery-engine looked after, and what do its setup files show

Health score

81 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity29.5 of 30Last push 36 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer15 of 15Owned by an organisation
Official source20 of 20Official server

Security check static checks

97 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1. What it checks

Licence: MIT

  • Low The documented install uses discovery-engine-api, whose published metadata names no source repository. Check it is the right package before installing.
  • Note No published npm or PyPI package of this repository was found, so package advisories were not checked.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.