Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Remote MCP server for 4chems hosted IUCLID, CHESAR and QSAR Toolbox: onboarding, inquiries, admin.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.4chems.com/mcp在终端中运行这条命令
claude mcp add --transport http platform-api https://mcp.4chems.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"platform-api": {
"url": "https://mcp.4chems.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"platform-api": {
"type": "http",
"url": "https://mcp.4chems.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.4chems.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 4chems.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.12.1)于27天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Safe Fetch
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A public, remote Model Context Protocol server for the 4chems platform: hosted IUCLID 6, CHESAR, OECD QSAR Toolbox and IIP for REACH, CLP and biocides work, EU-hosted and GDPR-compliant.
| Endpoint | https://mcp.4chems.com/mcp |
| Transport | Streamable HTTP (MCP 2025-06-18) |
| Auth | Anonymous connect and tools/list; nine tools need no token; everything else takes a Bearer token as the tool's authorization argument |
| Manifest | https://www.4chems.com/.well-known/mcp.json |
| Docs | https://www.4chems.com/mcp/ (DE: https://www.4chems.com/de/mcp/) |
| Registry | com.4chems/platform-api — see server.json |
Claude Code
claude mcp add --transport http 4chems https://mcp.4chems.com/mcp
Claude Desktop / claude.ai — Settings → Connectors → Add custom connector → https://mcp.4chems.com/mcp. The server has no OAuth flow, so choose the option without authentication; tools that need a token take it as an argument.
Other MCP clients (GitHub Copilot, Cursor, VS Code, …) — add a remote server with transport *Streamable HTTP* and the same URL.
Raw handshake (no client needed):
curl -s -X POST https://mcp.4chems.com/mcp \
-H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}'
The server exposes the customer tier of the 4chems platform API (/v1). This endpoint carries no substance or dossier data — see What this is not.
No token needed
| Tool | Purpose |
|---|---|
start_inquiry, verify_inquiry | Send 4chems a question or request a call: a 6-digit code goes to the user's email, the verified inquiry reaches a person. No web form, no account. |
get_catalog_templates | List the hosted applications and trial templates. |
get_onboarding_route | Return the next onboarding step for the caller. |
get_legal_entity_types | Legal-entity types for a country. |
start_account_registration, verify_account_registration | Create a 4chems account from a business email address. |
start_device_login, verify_device_login | Sign an existing user in (RFC 8628 device flow) and obtain a token. |
Bearer token required (authorization: "Bearer ")
| Area | Tools |
|---|---|
| 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 & services | list_members, grant_assignment, revoke_assignment, list_tenant_services, add_tenant_service |
Long-running mutations poll to completion; past the poll bound they return {"status": "running", "operation_id": …} for follow-up with get_my_operation.
The initialize response carries these as server instructions:
authorization argument, never log it.start_inquiry.server.json; the server itself is operated by 4chems.Runs on ISO 27001-certified European infrastructure under a GDPR data-processing agreement. 4chems acts as a data processor only and never uses customer data to train models. Security questionnaire: https://www.4chems.com/security-questionnaire/.
start_inquiry (no account needed)