Skip to main content
Glama
ToxMCP

Comptox MCP Server

by ToxMCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Comptox MCP Server

No user-submitted related servers found.

    Related Servers

    • ChemDraw Server

      tom832
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides chemical informatics endpoints for converting between chemical names and SMILES, processing molecule structures, and comparing molecules, with MCP compatibility.
      5
      MIT

    • TogoMCP

      dbcls
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).
      29
      18
      MIT

    • Cure Cancer With AI MCP Server

      hifarrer
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides oncology data (research, news, FDA approvals, clinical trials) and IBM MAMMAL biomedical predictions (PPI, DTI, ClinTox) as MCP tools. Allows AI agents to query cancer datasets and run predictions through a remote MCP server.
      -

    • EPA MCP Server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Access EPA environmental data — facility compliance (ECHO), toxic releases (TRI), Superfund sites, drinking water systems, environmental justice screening (EJScreen), and real-time air quality (AirNow) via MCP.
      201 npm
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 85 tools

    Disambiguation2/5

    Several tools target the same underlying resource with only subtle differences, such as search_httk vs get_exposure_httk, search_qsurs vs get_exposure_functional_use_probability, and search_exposures vs the many specific get_exposure_* tools. Batch variants are clearly labeled, but these overlapping exposure, HTTK, and functional-use endpoints make misselection likely.

    Naming Consistency4/5

    All names use snake_case and most follow a predictable verb_noun pattern with domain prefixes (get_bioactivity_*, get_hazard_*, get_exposure_*). Minor deviations exist, like metadata_get_model_card and opsin_convert_name where the domain/service prefix precedes the verb.

    Tool Count1/5

    85 tools is far beyond the 3-15 range for a well-scoped server and exceeds even a generous ceiling for a broad public-data API. Many batch and dataset-specific variants inflate the count, making the surface extremely heavy.

    Completeness5/5

    The surface covers chemical identity, bioactivity, exposure, hazard, metadata, public lists, and cross-domain aggregation workflows, with search/get/batch/list operations for most resources. No obvious gaps for the read-only CompTox domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources