How to Use the EPA Computational Toxicology MCP in Cursor

Q: Can Cursor use EPA Computational Toxicology to write unit tests for my chemistry app?

Yes, Cursor can call tools like searchchemicalbyname to pull real test data into your test suites. The editor uses actual EPA CompTox responses instead of mock data, ensuring your unit tests reflect real chemical properties and structures.

Pull EPA toxicity and physical properties directly into Cursor to write safety-compliant chemistry code and data pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect EPA Computational Toxicology MCP to Cursor

Create your Vinkius account to connect EPA Computational Toxicology to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup EPA Computational Toxicology with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Inject real toxicity data into your code with this MCP Server

The `get_chemical_details` tool lets your Cursor agent pull metadata and DTXSID values directly into your active editor. Instead of writing stubs or mocking chemical structures, you write code that pulls live EPA data. Your agent inspects the schema and writes accurate parsing logic on the fly. When building data science pipelines, you use `get_chemical_synonyms` to clean up messy chemical naming datasets. Cursor writes the mapping functions while referencing real-time synonyms from the CompTox database. You get clean, validated code that works with real-world chemistry data from day one.

Write predictive models with live physical properties

The `get_physicochemical_properties` tool gives your Cursor agent direct access to logP, melting points, and solubility data during a chat session. You can ask the editor to write a script that filters a list of chemicals based on their water solubility. This active tool execution grabs real experimental values and tests your script logic immediately. Your editor uses the live properties to populate test cases and validate your filtering algorithms. It shortens the feedback loop between writing code and verifying it against real chemical constants.

Automate hazard screening scripts

The `get_hazard_summary` tool retrieves ToxValDB toxicity values directly into your coding workspace to automate safety classification. You can instruct Cursor to write a Python function that flags compounds exceeding specific toxicity thresholds. This live payload helps structure your database models correctly. To verify exposure risks, your agent calls `get_exposure_summary` to pull predicted consumer product use data. Cursor integrates these exposure profiles directly into your analysis scripts. You build production-ready environmental safety dashboards without spending hours reading API documentation.

Setup guide

Set up EPA Computational Toxicology MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the EPA Computational Toxicology MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent EPA Computational Toxicology transactions." If the MCP tools are loaded correctly, Cursor will call the EPA Computational Toxicology tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "epa-computational-toxicology-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by US EPA CompTox. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect EPA Computational Toxicology now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about EPA Computational Toxicology MCP in Cursor

Add the server configuration to your global MCP configuration file. Once saved, enable Agent mode in the chat panel. Cursor will automatically detect the ten tools and allow the AI to invoke them during code generation.

Yes, Cursor can call tools like `search_chemical_by_name` to pull real test data into your test suites. The editor uses actual EPA CompTox responses instead of mock data, ensuring your unit tests reflect real chemical properties and structures.

While inline auto-complete doesn't call tools directly, Cursor's Agent mode uses these MCP tools to gather context before writing or editing your files. You can ask the agent to write a script using `get_bioactivity_summary` and it will fetch the data first, then write the code.

No, you do not. Vinkius manages all the upstream authentication and endpoint routing. You only configure your single Vinkius token in your Cursor configuration file to access all ten tools.

Yes, all requests containing your chemical names, CAS numbers, or hazard queries run in secure, ephemeral V8 isolates. Vinkius does not store or log the specific chemical identifiers you query. Your development environment stays private, and your proprietary data is never used for training models.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript