AI Agents - 4chems MCP Server

Connect an AI assistant to the 4chems platform via our Model Context Protocol (MCP) server.

4chems runs a remote MCP server so AI assistants and agents can work with the 4chems platform on a customer’s behalf — from the first 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 and the mcp-server <link> hint in every page’s <head>.

Add it in Claude Code:

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

In Claude Desktop or other MCP clients, add a remote HTTP MCP server with the same URL.

Authentication

Connecting to the server and listing its tools is anonymous. Five tools need no token at all — get_catalog_templates, get_legal_entity_types, get_onboarding_route, start_inquiry, and verify_inquiry — so an agent can browse the catalog, check onboarding requirements, 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, 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.

  • Contact (no token needed) — start_inquiry, verify_inquiry
  • Onboarding — get_onboarding_route (no token needed), create_access_request, create_self_service_tenant, get_legal_entity_types (no token needed)
  • Catalog — get_catalog_templates (no token needed)
  • Consents — list_consents, record_consent
  • Access & tenant administration — get_my_access, list_members, grant_assignment, revoke_assignment, list_tenant_services, add_tenant_service
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.
  • Before calling tools that change consents, assignments, 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.