1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
[//]: (mcp-name: io.github.mims-harvard/tooluniverse) AI agent (recommended) — open your AI agent and run: The agent will walk you through MCP configuration, API keys, skill installation, and validation. Add to your MCP config file: Install agent skills: Python developers — install the SDK: CLI — discover, inspect, run, and test tools from the terminal. Python SDK — programmatic access for…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
[//]: # (mcp-name: io.github.mims-harvard/tooluniverse) AI agent (recommended) — open your AI agent and run: The agent will walk you through MCP configuration, API keys, skill installation, and validation. Add to your MCP config file: Install agent skills: Python developers — install the SDK: CLI — discover, inspect, run, and test tools from the terminal. Python SDK — programmatic access for building AI scientist systems. Click to watch the demo (YouTube) (Bilibili) ToolUniverse is an ecosystem…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.