MCP servers for data science, machine-learning workflows, notebooks, model training and inference. Each entry is scanned with the deterministic Capability-Flow Trust Model — grades are computed, never self-reported.
Security scan results for the Storybook MCP server.
Security scan results for the Tmcp MCP server.
Security scan results for the Addon MCP server.
Security scan results for the Handler MCP server.
Security scan results for the Hostinger Api MCP server.
Security scan results for the Plugin MCP server.
Security scan results for the Framework MCP server.
Security scan results for the Instrumentation MCP server.
Security scan results for the Use MCP server.
Security scan results for the Adapter MCP server.
Security scan results for the Cli MCP server.
Security scan results for the Pi Mcp Adapter MCP server.
Security scan results for the Webmcp Types MCP server.
Security scan results for the Eslint MCP server.
Security scan results for the Darwin Arm64 MCP server.
Security scan results for the Kubernetes MCP server.
Security scan results for the Typia MCP server.
Security scan results for the Fastify MCP server.
Security scan results for the Xmcp MCP server.
Security scan results for the Searxng MCP server.
Security scan results for the Machine Bridge MCP server.
Security scan results for the Utcp MCP server.
Security scan results for the React Webmcp MCP server.
Security scan results for the Opentelemetry Instrumentation MCP server.
Jupyter kernels, dataframe and SQL engines, experiment trackers, model registries, vector databases, hosted inference endpoints - these are the systems a data science MCP server exposes to an AI assistant such as Claude or Cursor. Instead of pasting code and results back and forth, the assistant calls tools over the Model Context Protocol while the server holds the credentials, the data access, and the compute. The result is a notebook that talks back: analysis happens where the data already lives.
Every package listed here has been run through the same deterministic, open-source scan of its published npm or PyPI code: an A-F Trust Score, a blast-radius map of what the server could reach at worst, and evidence-backed findings. Identical input always yields the identical grade, no LLM sits in the loop, and rank cannot be bought - the scoring model is public.
Security stakes run unusually high in this category because a notebook or kernel tool is arbitrary code execution by design - functionally a shell with your Python environment's permissions. An over-permissioned or malicious MCP server here could read training data full of personal records, exfiltrate proprietary model weights or the cloud and tracker API keys sitting in environment variables, or quietly poison a dataset that feeds automated retraining. Prompt injection hidden in a dataset row or a model card can also steer the assistant itself. Before wiring one into a pipeline, compare candidates across the full registry, pair data tooling with hardening tools from Security & Testing, and treat anything near revenue or payment data with the caution you would apply to Finance & Commerce servers.
Yes - that access is exactly what makes these servers useful, and exactly what needs auditing. A data science MCP server typically inherits whatever its host process can reach: local files, kernel execution, and any ML-platform credentials in scope. Check a package's Trust Score, coverage level, and individual findings first, or run your own check through the free scan API.