Does the DAG Studio MCP MCP server require authentication?

Yes. When we connected to https://dagstudio-mcp.blackswancausallabs.com/mcp without credentials on 2026-09-19, it returned HTTP 401.

Can I grant read-only access to the DAG Studio MCP MCP server?

Not documented. We found no scope list to read.

Can the DAG Studio MCP MCP server be self-hosted?

Not from the registry record. No installable package is declared, so the vendor-hosted endpoint is the only documented option.

Vendor-published

DAG Studio MCP MCP server

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

DAG Studio MCP (`com.blackswancausallabs/dagstudio-mcp`, v0.1.0) is published by the vendor. It exposes a hosted endpoint over streamable-http, and no self-hostable package. It requires authentication; it publishes no scope list we could read. 4 of 4 enterprise control criteria are undocumented. Last checked 2026-09-19.

Add to comparison Vendor documentation Source repository

Identity and maintenance

Publisher and version information
Registry name	com.blackswancausallabs/dagstudio-mcp
Publisher domain	blackswancausallabs.com
Maintainer type	Vendor-published namespace com.blackswancausallabs -> blackswancausallabs.com; host dagstudio-mcp.blackswancausallabs.com is within blackswancausallabs.com
Latest version seen	0.1.0
Last checked	2026-09-19
Last changed	2026-09-19 Separate from “last checked”: we check far more often than anything changes.

Enterprise evaluation

Every row below exists whether or not we found an answer. Expand any row to see the exact source and the date. Unknown means undocumented, never unsupported.

Enterprise evaluation criteria for DAG Studio MCP
Access and authentication
Authentication required Whether the hosted endpoint accepted a connection with no credentials when we checked.	Yes We checked checked 2026-09-19 POST initialize without credentials -> HTTP 401 Unauthenticated connection attempt — https://dagstudio-mcp.blackswancausallabs.com/mcp
OAuth 2.1 authorization Whether the server publishes OAuth discovery metadata a client can follow automatically.	Not documented We checked checked 2026-09-19 no OAuth discovery document at either well-known location OAuth discovery metadata — https://dagstudio-mcp.blackswancausallabs.com/mcp
Dynamic client registration Without it, an IdP administrator must register a client by hand before anyone can connect.	Could not reach source We checked checked 2026-09-19 no authorization-server metadata document found Authorization server metadata — https://dagstudio-mcp.blackswancausallabs.com/mcp
Documented scopes	Not checked
Read and write are separate scopes A single opaque scope means read-only access cannot be granted: approving access approves everything.	Not checked
Deployment and transport
Streamable HTTP transport	Yes Registry checked 2026-09-19 "type": "streamable-http", "url": "https://dagstudio-mcp.blackswancausallabs.com/mcp" MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=com.blackswancausallabs%2Fdagstudio-mcp&version=latest
SSE transport	No Registry checked 2026-09-19 no sse remote declared MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=com.blackswancausallabs%2Fdagstudio-mcp&version=latest
Vendor-hosted endpoint Data leaves your network. Where it goes is a question for the vendor's documentation.	Yes Registry checked 2026-09-19 1 remote endpoint(s) declared MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=com.blackswancausallabs%2Fdagstudio-mcp&version=latest
Self-hostable package A published npm, PyPI, container or bundle artifact you can run inside your own perimeter.	No Registry checked 2026-09-19 no installable package declared MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=com.blackswancausallabs%2Fdagstudio-mcp&version=latest
Supply chain
Public source repository	Yes Registry checked 2026-09-19 https://github.com/Black-Swan-Causal-Labs/dagstudio-mcp MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=com.blackswancausallabs%2Fdagstudio-mcp&version=latest
Open-source license	Yes Apache-2.0 Vendor checked 2026-09-19 license: Apache-2.0 GitHub repository — https://github.com/Black-Swan-Causal-Labs/dagstudio-mcp
Repository actively maintained	Yes Vendor checked 2026-09-19 last push 61 days ago GitHub repository — https://github.com/Black-Swan-Causal-Labs/dagstudio-mcp
Package deprecated	Not checked
Secret inputs marked as secret Credential-shaped inputs the publisher did not flag as secret may be logged by a client.	Yes Registry checked 2026-09-19 1 credential input(s), all marked isSecret MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=com.blackswancausallabs%2Fdagstudio-mcp&version=latest
Documented controls
Audit logging documented	Not documented
Access controls documented	Not documented
Data residency documented	Not documented
Data retention documented	Not documented

What remains unknown

9 of 18 criteria are undocumented. These are the questions to put to the vendor — not conclusions about the product.

OAuth 2.1 authorization — no OAuth discovery document at either well-known location
Dynamic client registration — no authorization-server metadata document found
Documented scopes — no source found
Read and write are separate scopes — no source found
Package deprecated — no source found
Audit logging documented — no source found
Access controls documented — no source found
Data residency documented — no source found
Data retention documented — no source found

Turn these into a vendor questionnaire

How we checked

One unauthenticated initialize request, plus the two OAuth discovery documents. Nothing was installed or executed. The exact request headers are below so you can reproduce the result — endpoint behaviour can depend on them.

POST https://dagstudio-mcp.blackswancausallabs.com/mcp
user-agent: mcpcompare.ai/1.0 (+https://mcpcompare.ai/methodology/probe; probe@mcpcompare.ai)
content-type: application/json
accept: application/json, text/event-stream
mcp-protocol-version: 2025-06-18

-> HTTP 401  (auth-required)
   checked 2026-09-19T17:17:10.445Z

Questions people ask

Does the DAG Studio MCP MCP server require authentication?: Yes. When we connected to https://dagstudio-mcp.blackswancausallabs.com/mcp without credentials on 2026-09-19, it returned HTTP 401.
Can I grant read-only access to the DAG Studio MCP MCP server?: Not documented. We found no scope list to read.
Can the DAG Studio MCP MCP server be self-hosted?: Not from the registry record. No installable package is declared, so the vendor-hosted endpoint is the only documented option.