Disco MCP server
com.leap-labs/discovery-engineleap-labs.comstreamable-httpv1.0.1Scanned
Find novel, statistically validated patterns in tabular data — hypothesis-free.
14 tools: 3 can delete or cancel things, 7 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Disco MCP server can do
The Disco MCP server is published by leap-labs.com, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (3 tools: discovery_analyze, discovery_purchase_credits and discovery_subscribe) and create or change data (7 tools: discovery_estimate, discovery_upload, discovery_account, discovery_signup and 3 more). 4 tools only read.
1 tool reads private data (discovery_analyze).
The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 3Claude Code: deny
discovery_analyzeRun Disco on tabular data to find novel, statistically validated patterns.Reads private data2 findings
Why it is in this group
- The name "discovery_analyze" says "analyze": a word for reading.
- The description's first verb is "run": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- private-dataThe input names a file (input.file_ref), and the tool reads: it reads files.
Findings
- Info
The description is 2,332 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ey: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set."
- Warn
The server marks "discovery_analyze" destructive (destructiveHint: true), and its name says "analyze", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true,"idempotentHint":false}; The name "discovery_analyze" says "analyze": a word for reading.
Description, as the server wrote it 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 for the dataset. use_llms: Slower and more expensive, but you get smarter pre-processing, summary page, literature context and pattern novelty assessment. Only applies to private runs — public runs always use LLMs. Default false. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
Annotations the server declares
- title: Run Discovery Analysis
- destructiveHint: true
- idempotentHint: false
discovery_purchase_creditsPurchase Disco credit packs using a stored payment method.No findings
Why it is in this group
- The name "discovery_purchase_credits" says "purchase": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Purchase Credits
- destructiveHint: true
- idempotentHint: false
discovery_subscribeSubscribe to or change your Disco plan.No findings
Why it is in this group
- The name "discovery_subscribe" says "subscribe": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Subscribe to Plan
- destructiveHint: true
- idempotentHint: true
Changes things 7Claude Code: ask
discovery_accountCheck your Disco account status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get Account Info
- readOnlyHint: true
discovery_add_payment_methodAttach a Stripe payment method to your Disco account.No findings
Why it is in this group
- The name "discovery_add_payment_method" says "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Add Payment Method
- destructiveHint: false
- idempotentHint: true
discovery_estimateEstimate the credits required to run a Disco analysis.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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`.
Annotations the server declares
- title: Estimate Analysis Cost
- readOnlyHint: true
discovery_login_verifyComplete login and receive a new API key.No findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify Log In
- destructiveHint: false
- idempotentHint: true
discovery_signupCreate a Disco account and get an API key.No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it 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).
Annotations the server declares
- title: Sign Up
- destructiveHint: false
- idempotentHint: true
discovery_signup_verifyComplete Disco signup using an email verification code.No findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify Sign Up
- destructiveHint: false
- idempotentHint: true
discovery_uploadUpload a dataset file and return a file reference for use with discovery_analyze.No findings
Why it is in this group
- The name "discovery_upload" says "upload": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Upload Dataset
- destructiveHint: false
- idempotentHint: false
Only reads 4Show 4 read-only tools
discovery_get_resultsFetch the full results of a completed Disco run.No findings
Why it is in this group
- The name "discovery_get_results" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get Analysis Results
- readOnlyHint: true
discovery_list_plansList available Disco plans with pricing.No findings
Why it is in this group
- The name "discovery_list_plans" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List Plans
- readOnlyHint: true
discovery_loginGet a new API key for an existing Disco account.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Log In
- destructiveHint: false
- idempotentHint: true
discovery_statusCheck the status of a Disco run.No findings
Why it is in this group
- The name "discovery_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check Analysis Status
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (3 destructive, 7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://disco.leap-labs.com/mcp: tools/list returned 14 tools to an anonymous client, including discovery_analyze (destructive), discovery_purchase_credits (destructive), discovery_subscribe (destructive), discovery_estimate (write), discovery_upload (write) and 5 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "discovery_analyze" destructive (destructiveHint: true), and its name says "analyze", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true,"idempotentHint":false}; The name "discovery_analyze" says "analyze": a word for reading.
The description is 2,332 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ey: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http discovery-engine https://disco.leap-labs.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http discovery-engine https://disco.leap-labs.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__discovery-engine__discovery_list_plans",
"mcp__discovery-engine__discovery_status",
"mcp__discovery-engine__discovery_get_results",
"mcp__discovery-engine__discovery_login"
],
"ask": [
"mcp__discovery-engine__discovery_estimate",
"mcp__discovery-engine__discovery_upload",
"mcp__discovery-engine__discovery_account",
"mcp__discovery-engine__discovery_signup",
"mcp__discovery-engine__discovery_signup_verify",
"mcp__discovery-engine__discovery_login_verify",
"mcp__discovery-engine__discovery_add_payment_method"
],
"deny": [
"mcp__discovery-engine__discovery_analyze",
"mcp__discovery-engine__discovery_purchase_credits",
"mcp__discovery-engine__discovery_subscribe"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as discovery-engine. Review it before you use it.
Capability tags behind 1 rule
- mcp__discovery-engine__discovery_analyze private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.leap-labs/discovery-engine/verify?hash=753d8eae762734dcaf9bb1fc04ab182b169e1523ed6bd0de3e0adcce85c7ff35" | jq -e '.changed == false'Pinned hash 753d8eae7627, from Nov 10, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.leap-labs/discovery-engine/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.leap-labs/discovery-engine)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:58 UTC.
Disco MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Disco MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 10 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Disco MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: discovery_analyze, discovery_purchase_credits and discovery_subscribe.
Can the Disco MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Disco MCP server have?
- 14 tools: 3 destructive, 7 write, 4 read. discovery_analyze, discovery_purchase_credits, discovery_subscribe, discovery_estimate, discovery_upload, discovery_account, discovery_signup, discovery_signup_verify and 6 more.
Does the Disco MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Disco MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Disco MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.