How do I obtain a free API key for the EPA CTX services?

You must send an email to `ccte_api@epa.gov` to request an individual API key. The key is usually issued free of charge for research and professional use.

What is a DTXSID and how is it used?

DTXSID is the EPA Dashboard Chemical Identifier. It is the primary unique identifier used across all CompTox APIs to ensure precise substance identification.

Are the results returned in real-time from the EPA databases?

Yes, this agent queries the live CompTox Chemicals Dashboard APIs directly, ensuring you have the most up-to-date scientific data available from the CCTE.

EPA Computational Toxicology MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: EPA Computational Toxicology
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to EPA Computational Toxicology through the Vinkius — pass the Edge URL in the `mcps` parameter and every EPA Computational Toxicology tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="EPA Computational Toxicology Specialist",
    goal="Help users interact with EPA Computational Toxicology effectively",
    backstory=(
        "You are an expert at leveraging EPA Computational Toxicology tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in EPA Computational Toxicology "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, EPA Computational Toxicology becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call EPA Computational Toxicology tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the EPA Computational Toxicology MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from EPA Computational Toxicology

Why Use CrewAI with the EPA Computational Toxicology MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with EPA Computational Toxicology through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

EPA Computational Toxicology + CrewAI Use Cases

Practical scenarios where CrewAI combined with the EPA Computational Toxicology MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries EPA Computational Toxicology for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries EPA Computational Toxicology, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain EPA Computational Toxicology tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries EPA Computational Toxicology against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

EPA Computational Toxicology MCP Tools for CrewAI (10)

These 10 tools become available when you connect EPA Computational Toxicology to CrewAI via MCP:

get_bioactivity_summary

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

get_chemical_details

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

get_chemical_lists

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

get_chemical_synonyms

Retrieve all known synonyms and alternative names for a specific chemical

get_exposure_summary

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

get_fate_and_transport

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

get_hazard_summary

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

get_physicochemical_properties

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

search_chemical_by_casrn

Search for chemicals by their CAS Registry Number (CASRN)

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 CrewAI

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

"Search for the chemical properties of Bisphenol A."

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

"Find predicted exposure data for DTXSID7020182."

Troubleshooting EPA Computational Toxicology MCP Server with CrewAI

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

EPA Computational Toxicology + CrewAI FAQ

Common questions about integrating EPA Computational Toxicology MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.