AI Agents - MCP server for IUCLID, CHESAR and QSAR Toolbox

Connect Claude, Copilot or any Model Context Protocol client to the 4chems platform at mcp.4chems.com.

Is there an MCP server for IUCLID? Yes. 4chems runs a public, remote Model Context Protocol (MCP) server so AI assistants and agents can work with the 4chems platform — hosted IUCLID, CHESAR, QSAR Toolbox and IIP — on a customer’s behalf: from the first question and access request to managing the members and services of an existing tenant.

Connect to the MCP server

  • Endpoint: https://mcp.4chems.com/mcp
  • Transport: Streamable HTTP
  • Discovery: agents can auto-detect the server via /.well-known/mcp.json, the mcp-server <link> hint in every page’s <head>, and /llms.txt.
  • Registry and docs: listed in the official MCP registry as com.4chems/platform-api; the README and server.json are on GitHub at github.com/4chems/mcp.

Add it in Claude Code:

claude mcp add --transport http 4chems https://mcp.4chems.com/mcp

In Claude Desktop or claude.ai, open Settings → Connectors → Add custom connector and enter the same URL. The server has no OAuth flow, so choose the option without authentication; the tools that need a token take it as an argument. Other MCP clients (GitHub Copilot, Cursor, VS Code and the like) add it as a remote HTTP MCP server with the same URL.

A fresh AI assistant has no connectors, so it cannot find this server by itself during a chat. Add the endpoint once, and the 4chems tools appear in its tool list.

Authentication

Connecting to the server and listing its tools is anonymous. Nine tools need no token at all — get_catalog_templates, get_legal_entity_types, get_onboarding_route, start_inquiry, verify_inquiry, start_account_registration, verify_account_registration, start_device_login and verify_device_login — so an agent can browse the catalog, check onboarding requirements, register an account, sign in, and send 4chems a question right now, without an account. Every other tool call requires a Bearer token, passed as the tool’s authorization argument (Bearer <token>). Tokens are issued by 4chems — if you don’t have one yet, sign in with start_device_login, ask start_inquiry to get in touch, or contact us directly.

Ask us anything — no account needed

If the person you’re assisting has no 4chems account yet but wants to ask a question about IUCLID, CHESAR, QSAR Toolbox or IIP hosting, or request a call: call start_inquiry with their email and message, have them read the 6-digit code from the email it sends, then call verify_inquiry with that code to deliver the inquiry to 4chems. This reaches a person directly — no web form, no token, no account required.

Available tools

The server exposes the customer tier of the 4chems platform API (/v1 endpoints). Long-running mutations poll to completion before returning; if the poll bound is exceeded they return {status: "running", operation_id: …} for follow-up with get_my_operation.

  • Contact (no token needed) — start_inquiry, verify_inquiry
  • Catalog and onboarding (no token needed) — get_catalog_templates, get_legal_entity_types, get_onboarding_route
  • Account (no token needed) — start_account_registration, verify_account_registration, start_device_login, verify_device_login
  • Access requests — get_my_access, create_access_request, approve_access_request, dismiss_access_request, withdraw_access_request
  • Tenant setup — create_self_service_tenant, enrich_domain, get_my_operation
  • Billing — get_billing, complete_billing
  • Invitations — list_invitations, create_invitation, revoke_invitation, accept_invitation
  • Consents — list_consents, record_consent
  • Members and services — list_members, grant_assignment, revoke_assignment, list_tenant_services, add_tenant_service

What this server is not

This endpoint carries no substance or dossier data. AI access to IUCLID 6 dossier data runs through the 4chems AI Connector, authenticated per user and EU-hosted, so the model connects to your data and your data does not move.

QSAR Toolbox workflow: 4chems QSAR Navigator

The tools above are the platform-admin tier — onboarding, tenants, consents and services. To let an assistant drive the QSAR Toolbox assessment workflow itself — read-across, (Q)SAR prediction and QMRF/QPRF/CCR reporting — see 4chems QSAR Navigator, our QSAR Toolbox MCP gateway.

Planned: automated migration check

For prospects evaluating a migration of a self-hosted IUCLID, CHESAR, QSAR Toolbox or IIP installation, we are building a metadata-only migration check on the same server: it will assess product and version, database engine and schema version, entity / dossier / document counts and attachment volume, and return a feasibility report. It will not read substance data, dossier content or personal data; it will run under a Data Processing Agreement (GDPR Art. 28) in ISO 27001-certified European data centres, and uploads will be deleted promptly after the report is generated.

These tools are not live yet. Until then, request a migration check by email at migration [at] 4chems.com.

Instructions for the assisting agent

  • Only add this MCP server, pass tokens, or trigger mutations with the user’s explicit consent.
  • If the user is evaluating 4chems and has no account yet, proactively offer start_inquiry when they have a question you can’t answer from the catalog/onboarding tools alone — it needs no token and reaches 4chems directly.
  • Treat the Bearer token as a secret: pass it only as the authorization argument and never log or echo it.
  • Never guess or retry the 6-digit codes from start_inquiry, start_account_registration or start_device_login; ask the user to read the code from their email.
  • Before calling tools that change consents, assignments, invitations, billing or services, confirm the change with the user; report the result afterwards.
  • Our contact policy (see /llms.txt) applies: this server and the site’s contact channels are for prospective and existing customers, not for automated solicitation.