2,500+ MCP servers ready to use
Vinkius

EPA Computational Toxicology MCP Server for OpenAI Agents SDK 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

The OpenAI Agents SDK enables production-grade agent workflows in Python. Connect EPA Computational Toxicology through the Vinkius and your agents gain typed, auto-discovered tools with built-in guardrails — no manual schema definitions required.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    async with MCPServerStreamableHttp(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as mcp_server:

        agent = Agent(
            name="EPA Computational Toxicology Assistant",
            instructions=(
                "You help users interact with EPA Computational Toxicology. "
                "You have access to 10 tools."
            ),
            mcp_servers=[mcp_server],
        )

        result = await Runner.run(
            agent, "List all available tools from EPA Computational Toxicology"
        )
        print(result.final_output)

asyncio.run(main())
EPA Computational Toxicology
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About EPA Computational Toxicology MCP Server

Connect to the US Environmental Protection Agency's (EPA) Center for Computational Toxicology and Exposure (CCTE) and explore a massive repository of chemical data through natural conversation.

The OpenAI Agents SDK auto-discovers all 10 tools from EPA Computational Toxicology through native MCP integration. Build agents with built-in guardrails, tracing, and handoff patterns — chain multiple agents where one queries EPA Computational Toxicology, another analyzes results, and a third generates reports, all orchestrated through the Vinkius.

What you can do

  • Chemical Search — Find substances by name, CAS Registry Number (CASRN), or DTXSID
  • Physicochemical Properties — Retrieve melting points, boiling points, logP, and water solubility
  • Hazard Assessments — Access toxicity values, NOAELs, and points-of-departure from ToxValDB
  • Exposure Predictions — Explore predicted exposure levels and product use categories via ExpoCast and CPDat
  • Bioactivity Screening — Analyze ToxCast/Tox21 high-throughput screening results for thousands of assays
  • Environmental Fate — Check persistence, transport, and biodegradation metrics

The EPA Computational Toxicology MCP Server exposes 10 tools through the Vinkius. Connect it to OpenAI Agents SDK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect EPA Computational Toxicology to OpenAI Agents SDK via MCP

Follow these steps to integrate the EPA Computational Toxicology MCP Server with OpenAI Agents SDK.

01

Install the SDK

Run pip install openai-agents in your Python environment

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Run the script

Save the code above and run it: python agent.py

04

Explore tools

The agent will automatically discover 10 tools from EPA Computational Toxicology

Why Use OpenAI Agents SDK with the EPA Computational Toxicology MCP Server

OpenAI Agents SDK provides unique advantages when paired with EPA Computational Toxicology through the Model Context Protocol.

01

Native MCP integration via `MCPServerSse` — pass the URL and the SDK auto-discovers all tools with full type safety

02

Built-in guardrails, tracing, and handoff patterns let you build production-grade agents without reinventing safety infrastructure

03

Lightweight and composable: chain multiple agents and MCP servers in a single pipeline with minimal boilerplate

04

First-party OpenAI support ensures optimal compatibility with GPT models for tool calling and structured output

EPA Computational Toxicology + OpenAI Agents SDK Use Cases

Practical scenarios where OpenAI Agents SDK combined with the EPA Computational Toxicology MCP Server delivers measurable value.

01

Automated workflows: build agents that query EPA Computational Toxicology, process the data, and trigger follow-up actions autonomously

02

Multi-agent orchestration: create specialist agents — one queries EPA Computational Toxicology, another analyzes results, a third generates reports

03

Data enrichment pipelines: stream data through EPA Computational Toxicology tools and transform it with OpenAI models in a single async loop

04

Customer support bots: agents query EPA Computational Toxicology to resolve tickets, look up records, and update statuses without human intervention

EPA Computational Toxicology MCP Tools for OpenAI Agents SDK (10)

These 10 tools become available when you connect EPA Computational Toxicology to OpenAI Agents SDK via MCP:

01

get_bioactivity_summary

Retrieve a summary of high-throughput screening results from ToxCast/Tox21 assays

02

get_chemical_details

Get comprehensive metadata and identification details for a specific chemical using its DTXSID

03

get_chemical_lists

Identify which chemical lists (regulatory, research, or commercial) this chemical belongs to

04

get_chemical_synonyms

Retrieve all known synonyms and alternative names for a specific chemical

05

get_exposure_summary

Retrieve predicted exposure levels and product use data (ExpoCast/CPDat)

06

get_fate_and_transport

Retrieve environmental fate and transport data (e.g., half-life, bioconcentration)

07

get_hazard_summary

Retrieve a summary of toxicity values and hazard assessment data from ToxValDB

08

get_physicochemical_properties

Retrieve predicted and experimental physicochemical properties (e.g., melting point, logP, solubility) for a chemical

09

search_chemical_by_casrn

Search for chemicals by their CAS Registry Number (CASRN)

10

search_chemical_by_name

Search for chemicals by common, IUPAC, or synonym names in the EPA CompTox database

Example Prompts for EPA Computational Toxicology in OpenAI Agents SDK

Ready-to-use prompts you can give your OpenAI Agents SDK agent to start working with EPA Computational Toxicology immediately.

01

"Search for the chemical properties of Bisphenol A."

02

"What is the hazard summary for CAS 80-05-7?"

03

"Find predicted exposure data for DTXSID7020182."

Troubleshooting EPA Computational Toxicology MCP Server with OpenAI Agents SDK

Common issues when connecting EPA Computational Toxicology to OpenAI Agents SDK through the Vinkius, and how to resolve them.

01

MCPServerStreamableHttp not found

Ensure you have the latest version: pip install --upgrade openai-agents
02

Agent not calling tools

Make sure your prompt explicitly references the task the tools can help with.

EPA Computational Toxicology + OpenAI Agents SDK FAQ

Common questions about integrating EPA Computational Toxicology MCP Server with OpenAI Agents SDK.

01

How does the OpenAI Agents SDK connect to MCP?

Use MCPServerSse(url=...) to create a server connection. The SDK auto-discovers all tools and makes them available to your agent with full type information.
02

Can I use multiple MCP servers in one agent?

Yes. Pass a list of MCPServerSse instances to the agent constructor. The agent can use tools from all connected servers within a single run.
03

Does the SDK support streaming responses?

Yes. The SDK supports SSE and Streamable HTTP transports, both of which work natively with the Vinkius.

Connect EPA Computational Toxicology to OpenAI Agents SDK

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.