12 tools from the Discovery Engine MCP Server, categorised by risk level.
View the Discovery Engine policy →discovery_analyze Run Disco on tabular data to find novel, statistically validated patterns.
This is NOT another data analyst — it's a discovery pipeline that s... 2/5 discovery_get_results Fetch the full results of a completed Disco run.
Returns discovered patterns (with conditions, p-values, novelty scores,
citations), featu... 2/5 discovery_list_plans List available Disco plans with pricing.
No authentication required. Returns all available subscription tiers
with credit allowances and p... discovery_signup_verify Complete Disco signup using an email verification code.
Call this after discovery_signup returns {"status": "verification_required"}.
The ... 2/5 discovery_status Check the status of a Disco run.
Returns current status and progress details:
- status: "pending" | "processing" | "completed" | "failed"
... 2/5 discovery_account Check your Disco account status.
Returns current plan, available credits (subscription + purchased), and
payment method status. Use this t... 3/5 discovery_add_payment_method Attach a Stripe payment method to your Disco account.
The payment method must be tokenized via Stripe's API first — card details
never tou... 3/5 discovery_estimate Estimate cost, time, and credit requirements before running an analysis.
Returns credit cost, estimated duration in seconds, whether you have
... 3/5 discovery_purchase_credits Purchase Disco credit packs using a stored payment method.
Credits cost $1.00 each, sold in packs of 20 ($20/pack). Credits are used
for p... 3/5 discovery_subscribe Subscribe to or change your Disco plan.
Available plans:
- "free_tier": Explorer — free, 10 credits/month
- "tier_1": Researcher — $49... 3/5 discovery_upload Upload a dataset file and return a file reference for use with discovery_analyze.
Call this before discovery_analyze. Pass the returned result... 3/5 The Discovery Engine MCP server exposes 12 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Discovery Engine server.
Discovery Engine tools are categorised as Read (5), Write (6), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept