Publisher portfolio
blackswancausallabs.com
Explore the MCP servers published by blackswancausallabs.com, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 6
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 0
Active servers with a recorded connection probe
- Latest probe connected
- 0
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 6
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
DAG Studio MCP Causal DAG analysis: backdoor paths, adjustment sets, bias simulation. Validated against dagitty. | Requires auth | Not measured | 4 / 22 | Not checked yet |
Docket Lens Retrieve FDA docket comments, attachments and draft/final guidance for reviewable analysis. | Not measured | Not measured | 4 / 6 | Not checked yet |
NHANES (design-correct survey analysis) Design-correct NHANES analysis: survey weights, pooled cycles, CIs and NCHS reliability flags. | Not measured | Not measured | 4 / 6 | Not checked yet |
openFDA Regulatory Metadata Resolve FDA application numbers and product names to regulatory metadata (CDER, CBER, CDRH). | Not measured | Not measured | 3 / 6 | Not checked yet |
ROBINS-I V2 MCP ROBINS-I V2 (not V1): risk of bias in one result of a non-randomized cohort study | Not measured | Not measured | 3 / 6 | Not checked yet |
TARGET Checklist MCP Score how completely a target-trial-emulation study reports what the TARGET guideline requires. | Not measured | Not measured | 3 / 6 | Not checked yet |
Company & identity
About blackswancausallabs.com
blackswancausallabs.com publishes MCP servers under the com.blackswancausallabs namespace. This namespace uses a reverse-domain identity in the directory.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.