MCP.Market

DAG Studio WebMCP MCP server

online · 100% uptime
by Black-Swan-Causal-Labs·io.github.Black-Swan-Causal-Labs/dag-studio-webmcp·v1.0.0
No reviews yet

Read and edit a live DAG Studio canvas through its predefined WebMCP tools.

A85/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed DAG Studio WebMCP yet.

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

DAG Studio WebMCP tools

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

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 182ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (bearer)9/15
  • Maintenancelast push 17 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How DAG Studio WebMCP compares

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

Safety score
85/100
higher than 70% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
68 ms
faster than 90% of 30,031 servers

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

claude mcp add --transport http dag-studio-webmcp https://dag-studio-webmcp-bridge.jdiazdecaro.workers.dev/mcp
Add to Cursor

What the publisher says

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

DAG Studio WebMCP

A human–AI causal DAG workspace for the OpenAI 2026 WebMCP Challenge.

The AI proposes. The researcher decides. The engine verifies.

Live HTTPS sandbox · Original DAG Studio · MIT License

The problem

Causal directed acyclic graphs encode scientific assumptions: which variables cause which, what is measured or latent, and which paths may bias an effect estimate. Those decisions require domain expertise and scientific accountability. A general-purpose agent can help a researcher inspect and edit a graph, but visual browser automation is slow, ambiguous, and disconnected from the application's causal semantics.

DAG Studio WebMCP turns the existing DAG Studio interface into a shared workspace. A researcher can edit the canvas directly while an agent reads and updates that exact same graph through structured browser-native tools. Every agent mutation is visible and undoable. The causal engine checks the implications of the graph; neither the engine nor the agent claims to determine scientific truth.

Why WebMCP matters

Without WebMCP, an agent must infer node identities, edge directions, and analysis controls from pixels and DOM structure. With WebMCP, DAG Studio explicitly exposes safe, purpose-built operations such as addnode, addedge, and analyzecurrentdag.

This enables a two-way collaboration that was difficult before:

  1. The agent can read the live graph without scraping the interface.
  2. The agent can propose a precise, attributed change.
  3. The researcher immediately sees, moves, edits, accepts, or undoes it.
  4. Human canvas edits are immediately visible to the agent.
  5. The existing causal engine verifies backdoor paths and adjustment implications.
  6. The agent can simulate reproducible data under competing DAG hypotheses and compare their structural and statistical implications.

Live demonstration

Open the sandbox in ChatGPT's WebMCP-capable browser or Chrome with chrome://flags/#enable-webmcp-testing enabled. The header displays WebMCP connected when tools are available.

Suggested prompt:

Read the current DAG. Propose Smoking Status as a possible confounder, add it with arrows to Treatment and Outcome, then analyze the graph. Treat the additions as assumptions for my review and do not make any other changes.

The graph updates in place. Move the new node manually, then ask the agent to read the graph again to demonstrate that both participants share the same state.

WebMCP tools

The integration prefers the current document.modelContext API and includes a temporary navigator.modelContext fallback for hosts implementing an earlier WebMCP draft.

Architecture

Shortened. The full README is on GitHub.

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

DAG Studio WebMCP: common questions

Is DAG Studio WebMCP MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the DAG Studio WebMCP safety report
How do I install DAG Studio WebMCP?
It runs remotely at dag-studio-webmcp-bridge.jdiazdecaro.workers.dev. 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 WebMCP need an API key?
Yes. The registry entry asks for Authorization.
Is DAG Studio WebMCP maintained?
The last commit was 37 days ago (2026-09-28). The latest release is v1.0.0.
Is DAG Studio WebMCP up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does DAG Studio WebMCP compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 68 ms (faster than 90% of 30,031 servers). Full comparison.