Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Disco

REMOTE · DISCO.LEAP-LABS.COM · SCANNED SEP 25

Find novel, statistically validated patterns in tabular data — hypothesis-free.

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2605 tokens (~186/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Disco MCP server?

Disco is a hosted endpoint at https://disco.leap-labs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · disco.leap-labs.com

# add to Claude Code
claude mcp add --transport http com-leap-labs-discovery-engine 'https://disco.leap-labs.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-leap-labs-discovery-engine": {
      "url": "https://disco.leap-labs.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-leap-labs-discovery-engine": {
      "type": "http",
      "url": "https://disco.leap-labs.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-leap-labs-discovery-engine]
url = "https://disco.leap-labs.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-leap-labs-discovery-engine": {
      "type": "remote",
      "url": "https://disco.leap-labs.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-leap-labs-discovery-engine --url 'https://disco.leap-labs.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-leap-labs-discovery-engine:
    url: "https://disco.leap-labs.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-leap-labs-discovery-engine": {
      "Transport": "http",
      "Url": "https://disco.leap-labs.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-leap-labs-discovery-engine -t streamable-http -u 'https://disco.leap-labs.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-leap-labs-discovery-engine": {
      "type": "http",
      "url": "https://disco.leap-labs.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://disco.leap-labs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=disco.leap-labs.com CN=YR2,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 RSA 2048 SHA256-RSA 69ae5373de8b8a4191f68c9abb7aef2f13f
SANs: disco.leap-labs.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of disco.leap-labs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
leap-labs.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.clerk.com https://*.clerk.accounts.dev https://clerk.disco.leap-labs.com https://*.clerk.disco.leap-labs.com https://clerk.halley.leap-labs.com https://*.clerk.halley.leap-labs.com https://www.googletagmanager.com https://www.clarity.ms https://*.clarity.ms https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' https: data: blob:; font-src 'self' data:; connect-src 'self' https://*.clerk.com https://*.clerk.accounts.dev https://api.clerk.com https://*.leap-labs.com https://*.disco.leap-labs.com https://*.halley.leap-labs.com https://*.modal.run https://*.sentry.io https://*.stripe.com https://www.google-analytics.com https://*.google-analytics.com https://*.clarity.ms https://challenges.cloudflare.com https://*.storage.googleapis.com; frame-src 'self' https://*.clerk.com https://*.clerk.accounts.dev https://*.stripe.com https://challenges.cloudflare.com; frame-ancestors 'self'; worker-src 'self' blob:
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://disco.leap-labs.com/mcp Verified 200
http (plaintext) http://disco.leap-labs.com/mcp HTTPS enforced 308 https://disco.leap-labs.com/mcp
MCP tools · 14 exposed · ~2,535 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
discovery_account ~82

Check your Disco account status. Returns current plan, available credits (subscription + purchased), and payment method status. Use this to verify you have sufficient credits before running a private analysis. Args: api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_add_payment_method ~154

Attach a Stripe payment method to your Disco account. The payment method must be tokenized via Stripe's API first — card details never touch Disco's servers. Required before purchasing credits or subscribing to a paid plan. To tokenize a card, call Stripe's API directly: POST https://api.stripe.com/v1/payment_methods with the stripe_publishable_key from your account info. Args: payment_method_id: Stripe payment method ID (pm_...) from Stripe's API. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
payment_method_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_analyze ~558

Run Disco on tabular data to find novel, statistically validated patterns. This is NOT another data analyst — it's a discovery pipeline that systematically searches for feature interactions, subgroup effects, and conditional relationships nobody thought to look for, then validates each on hold-out data with FDR-corrected p-values and checks novelty against academic literature. This is a long-running operation. Returns a run_id immediately. Use discovery_status to poll and discovery_get_results to fetch completed results. Use this when you need to go beyond answering questions about data and start finding things nobody thought to ask. Do NOT use this for summary statistics, visualization, or SQL queries. Public runs are free but results are published. Private runs cost credits. Call discovery_estimate first to check cost. Private report URLs require sign-in — tell the user to sign in at the dashboard with the same email address used to create the account (email code, no password needed). Call discovery_upload first to upload your file, then pass the returned file_ref here. Args: target_column: The column to analyze — what drives it, beyond what's obvious. file_ref: The file reference returned by discovery_upload. analysis_depth: Search depth (1=fast, higher=deeper). Default 1. visibility: "public" (free) or "private" (costs credits). Default "public". title: Optional title for the analysis. description: Optional description of the dataset. excluded_columns: Optional JSON array of column names to exclude from analysis. column_descriptions: Optional JSON object mapping column names to descriptions. Significantly improves pattern explanations — always provide if column names are non-obvious (e.g. {"col_7": "patient age", "feat_a": "blood pressure"}). author: Optional author name for the report. source_url: Optional source URL…

NameTypeReqDescription
analysis_depthinteger––
api_key–––
author–––
column_descriptions–––
description–––
excluded_columns–––
file_ref–––
source_url–––
target_columnstringyes–
title–––
use_llmsboolean––
visibilitystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_estimate ~240

Estimate the credits required to run a Disco analysis. Returns `required_credits` for public (always 0) and private, with private split by whether LLMs are enabled (use_llms=False is faster, use_llms=True adds smarter preprocessing, literature context and a written summary). Also returns per-visibility depth caps and accepted file formats. No authentication required — when an API key is supplied, also returns the caller's available credits. Call this before discovery_analyze whenever cost or feasibility is unclear. Args: file_size_mb: Size of the dataset in megabytes. num_columns: Number of columns in the dataset. analysis_depth: Search depth (1=fast, higher=deeper). Used to compute the private-run cost. Default 2. api_key: Disco API key (disco_...). Optional. When provided, the response includes `account.available_credits`.

NameTypeReqDescription
analysis_depthinteger––
api_key–––
file_size_mbnumberyes–
num_columnsintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_get_results ~259

Fetch the full results of a completed Disco run. Returns discovered patterns (with conditions, p-values, novelty scores, citations), feature importance scores, a summary with key insights, column statistics, and suggestions for what to explore next. The response includes a `dashboard_urls` object with direct links to each page of the interactive report — use these to direct the user to the most relevant view: - **summary**: AI-generated overview with key insights, novel findings, and plain-language explanation of the most important findings - **patterns**: Full list of discovered patterns with conditions, effect sizes, p-values, novelty scores, citations, and interactive visualizations - **features**: Feature importances, feature statistics and distribution plots, and correlation matrix - **territory**: Interactive 3D map showing how patterns select different regions of the data Only call this after discovery_status returns "completed". Args: run_id: The run ID returned by discovery_analyze. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
run_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_list_plans ~45

List available Disco plans with pricing. No authentication required. Returns all available subscription tiers with credit allowances and pricing. Use this to help users choose a plan.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_login ~119

Get a new API key for an existing Disco account. Sends a 6-digit verification code to the email address. Call discovery_login_verify with the code to receive a new API key. Use this when you need an API key for an account that already exists (e.g. the key was lost or this is a new agent session). Returns 404 if no account exists with this email — use discovery_signup instead. Args: email: Email address of the existing account.

NameTypeReqDescription
emailstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_login_verify ~107

Complete login and receive a new API key. Call this after discovery_login returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address. Returns a new API key on success. Args: email: Email address used in the discovery_login call. code: 6-digit verification code from the email.

NameTypeReqDescription
codestringyes–
emailstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_purchase_credits ~126

Purchase Disco credit packs using a stored payment method. Credits cost $0.10 each, sold in packs of 100 ($10/pack). Credits are used for private analyses (public analyses are free). Requires a payment method on file — use discovery_add_payment_method first. Args: packs: Number of 100-credit packs to purchase. Default 1. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
packsinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_signup ~150

Create a Disco account and get an API key. Provide an email address to start the signup flow. If email verification is required, returns {"status": "verification_required"} — the user will receive a 6-digit code by email, then call discovery_signup_verify to complete signup and receive the API key. The free tier (10 credits/month, unlimited public runs) is active immediately. No authentication required. Returns 409 if the email is already registered. Args: email: Email address for the new account. name: Display name (optional — defaults to email local part).

NameTypeReqDescription
emailstringyes–
namestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_signup_verify ~110

Complete Disco signup using an email verification code. Call this after discovery_signup returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address used in discovery_signup. Returns an API key on success. Args: email: Email address used in the discovery_signup call. code: 6-digit verification code from the email.

NameTypeReqDescription
codestringyes–
emailstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_status ~181

Check the status of a Disco run. Returns current status and progress details: - status: "pending" | "processing" | "completed" | "failed" - job_status: underlying job queue status - queue_position: position in queue when pending (1 = next up) - current_step: active pipeline step (preprocessing, training, interpreting, reporting) - estimated_wait_seconds: estimated queue wait time in seconds (pending only) Poll this after calling discovery_analyze. Use discovery_get_results to fetch full results once status is "completed". Args: run_id: The run ID returned by discovery_analyze. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
run_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_subscribe ~154

Subscribe to or change your Disco plan. Available plans: - "free_tier": Explorer — free, 10 credits/month - "tier_1": Researcher — $49/month, 500 credits/month - "tier_2": Team — $199/month, 2000 credits/month Paid plans require a payment method on file. Credits roll over on paid plans. Args: plan: Plan tier ID ("free_tier", "tier_1", or "tier_2"). api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
planstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

discovery_upload ~250

Upload a dataset file and return a file reference for use with discovery_analyze. Call this before discovery_analyze. Pass the returned result directly to discovery_analyze as the file_ref argument. Provide exactly one of: file_url, file_path, or file_content. Args: file_url: A publicly accessible http/https URL. The server downloads it directly. Best option for remote datasets. file_path: Absolute path to a local file. Only works when running the MCP server locally (not the hosted version). Streams the file directly — no size limit. file_content: File contents, base64-encoded. For small files when a URL or path isn't available. Limited by the model's context window. file_name: Filename with extension (e.g. "data.csv"), for format detection. Only used with file_content. Default: "data.csv". api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

NameTypeReqDescription
api_key–––
file_content–––
file_namestring––
file_path–––
file_url–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the Disco MCP server?

Disco is an MCP server listed in the public MCP registry as com.leap-labs/discovery-engine. Find novel, statistically validated patterns in tabular data, hypothesis-free. This page covers its hosted endpoint (https://disco.leap-labs.com/mcp).

Is the Disco MCP server safe to use?

Disco scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Disco MCP server expose?

Disco exposes 14 tools: discovery_list_plans, discovery_estimate, discovery_upload, discovery_analyze, discovery_status, and 9 more. Their descriptions and schemas cost roughly 2,535 tokens of context every time the server is loaded.

Does the Disco MCP server require authentication?

No. We connected to Disco without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Disco MCP server still maintained?

Disco is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.