MCP.Market

DAG Studio MCP server

online · 100% uptime
by blackswancausallabs.com·com.blackswancausallabs/dagstudio-mcp·v0.1.0

Causal DAG analysis: backdoor paths, adjustment sets, bias simulation. Validated against dagitty.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed DAG Studio MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

DAG Studio MCP tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 467ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 68 days ago12/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How DAG Studio MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
225 ms
faster than 59% of 30,031 servers

Install DAG Studio MCP in Claude Code, Cursor or VS Code

claude mcp add --transport http dagstudio-mcp https://dagstudio-mcp.blackswancausallabs.com/mcp
Add to Cursor

What the publisher says

From the DAG Studio MCP repository's README, as published. We do not edit it. Read it on GitHub

dag-studio-mcp

Model Context Protocol (MCP) server for the DAG Studio causal-inference engine. It lets AI agents construct, analyze, and validate causal directed acyclic graphs (DAGs) using the same engine that powers the DAG Studio canvas.

Built and maintained by Black Swan Causal Labs. Listed in the RWE MCP Registry.

Tools

Every analytical response carries an engine_version stamp, a concordance attestation, a diagnostics block with severity-coded flags, and citations to the underlying methods literature.

Validation

The engine is validated four ways for coherence: against Pearl (2009) theory, against the reference implementation dagitty (Textor et al. 2016), against DAG Studio's own analytical results, and empirically via compute_bias on simulated data.

  • 35 canonical cases: T01 to T15 (structural identification) and EM01 to EM20 (effect modification), runnable live via validate_engine.
  • A release-gate concordance check runs the engine head-to-head against dagitty (vendored at upstream commit 7a65777) and stamps the attestation surfaced in tool responses.
  • 93 unit and integration tests across the engine bindings, the tool layer, and the auth gate.

Hosted endpoint

The server runs as a Cloudflare Worker (Streamable HTTP):

https://dagstudio-mcp.blackswancausallabs.com/mcp

Access is token-gated during the trial period. Request a token at jdiazdecaro@blackswancausallabs.com. Tokens are accepted either as a bearer header or as a ?token= query parameter (the query form exists for clients whose connector UI cannot set custom headers, such as the Claude.ai web connector).

Claude Code:

claude mcp add --transport http dag-studio \
  https://dagstudio-mcp.blackswancausallabs.com/mcp \
  --header "Authorization: Bearer <your token>"

Claude.ai web: add a custom connector pointed at https://dagstudio-mcp.blackswancausallabs.com/mcp?token=.

Repository layout

  • dag-engine.js / dag-engine.d.ts: the analytical engine, a pure ESM module with no runtime dependencies
  • src/tools/: one file per tool, each exporting { InputSchema, OutputSchema, descriptor, handler }
  • src/worker/: Cloudflare Worker transport and the token gate (auth.ts)
  • src/index.ts: stdio entry point for local use
  • ci/: release-gate concordance harness against vendored dagitty
  • tests/: unit and integration tests (npm test)
  • MCP_REQUIREMENTS.md: the v1 specification
  • FDAGUIDANCEALIGNMENT.md: mapping of DAG Studio capabilities onto FDA draft RWE guidance protocol elements

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

DAG Studio MCP: common questions

Is DAG Studio MCP server safe?
Mostly: it is graded B (78/100). Read the DAG Studio MCP safety report
How do I install DAG Studio MCP?
It runs remotely at dagstudio-mcp.blackswancausallabs.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does DAG Studio MCP need an API key?
Yes. The registry entry asks for Authorization.
Is DAG Studio MCP maintained?
The last commit was 107 days ago (2026-07-20). The latest release is v0.1.0.
Is DAG Studio MCP up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does DAG Studio MCP compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 225 ms (faster than 59% of 30,031 servers). Full comparison.

More from blackswancausallabs.com →