Data Prism
概览
作者提供的说明(英文原文)
Fail-closed privacy layer that pseudonymises enterprise API data for LLM agents and MCP clients.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: Streamable HTTP
- 分类: 搜索与 AI 记忆
- 你需要填写:LOADER_PATH, DATAPRISM_SECURITY_JWT_ISSUER, DATAPRISM_SECURITY_JWT_AUDIENCE, DATAPRISM_SECURITY_JWT_JWK_SET_URI, DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL, DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES, DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION, DATAPRISM_SECURITY_POLICY_PURPOSES, DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR, DATAPRISM_PRIVACY_PROFILE, DATAPRISM_PRIVACY_SCOPE_LIFETIME, DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID, DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE, DATAPRISM_AUDIT_SINK, DATAPRISM_AUDIT_WRITER_ID, DATAPRISM_METRICS_SINK, DATAPRISM_HAZELCAST_TOPOLOGY, DATAPRISM_SOURCES_CUSTOMER_BASE_URL, DATAPRISM_SOURCES_CUSTOMER_TIMEOUT
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 需要你自己填写:
LOADER_PATH,DATAPRISM_SECURITY_JWT_ISSUER,DATAPRISM_SECURITY_JWT_AUDIENCE,DATAPRISM_SECURITY_JWT_JWK_SET_URI,DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI,DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL,DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES,DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION,DATAPRISM_SECURITY_POLICY_PURPOSES,DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR,DATAPRISM_PRIVACY_PROFILE,DATAPRISM_PRIVACY_SCOPE_LIFETIME,DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID,DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE,DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE,DATAPRISM_AUDIT_SINK,DATAPRISM_AUDIT_WRITER_ID,DATAPRISM_AUDIT_FILE_PATH,DATAPRISM_METRICS_SINK,DATAPRISM_HAZELCAST_TOPOLOGY,DATAPRISM_HAZELCAST_CLUSTERNAME,DATAPRISM_HAZELCAST_JOIN_MODE,DATAPRISM_HAZELCAST_JOIN_MEMBERS,DATAPRISM_HAZELCAST_MEMBER_PORT,DATAPRISM_OPERATOR_ENABLED,DATAPRISM_OPERATOR_PORT,DATAPRISM_OPERATOR_REQUIREDAUDIENCE,DATAPRISM_OPERATOR_REQUIREDSCOPE,DATAPRISM_SOURCES_CUSTOMER_BASE_URL,DATAPRISM_SOURCES_CUSTOMER_TIMEOUT
你需要
- Docker已安装 Docker
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"data-prism": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"LOADER_PATH",
"-e",
"DATAPRISM_SECURITY_JWT_ISSUER",
"-e",
"DATAPRISM_SECURITY_JWT_AUDIENCE",
"-e",
"DATAPRISM_SECURITY_JWT_JWK_SET_URI",
"-e",
"DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION",
"-e",
"DATAPRISM_SECURITY_POLICY_PURPOSES",
"-e",
"DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR",
"-e",
"DATAPRISM_PRIVACY_PROFILE",
"-e",
"DATAPRISM_PRIVACY_SCOPE_LIFETIME",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE",
"-e",
"DATAPRISM_AUDIT_SINK",
"-e",
"DATAPRISM_AUDIT_WRITER_ID",
"-e",
"DATAPRISM_AUDIT_FILE_PATH",
"-e",
"DATAPRISM_METRICS_SINK",
"-e",
"DATAPRISM_HAZELCAST_TOPOLOGY",
"-e",
"DATAPRISM_HAZELCAST_CLUSTERNAME",
"-e",
"DATAPRISM_HAZELCAST_JOIN_MODE",
"-e",
"DATAPRISM_HAZELCAST_JOIN_MEMBERS",
"-e",
"DATAPRISM_HAZELCAST_MEMBER_PORT",
"-e",
"DATAPRISM_OPERATOR_ENABLED",
"-e",
"DATAPRISM_OPERATOR_PORT",
"-e",
"DATAPRISM_OPERATOR_REQUIREDAUDIENCE",
"-e",
"DATAPRISM_OPERATOR_REQUIREDSCOPE",
"-e",
"DATAPRISM_SOURCES_CUSTOMER_BASE_URL",
"-e",
"DATAPRISM_SOURCES_CUSTOMER_TIMEOUT",
"ghcr.io/aindriub/data-prism-server:0.7.1"
],
"env": {
"LOADER_PATH": "your-value",
"DATAPRISM_SECURITY_JWT_ISSUER": "your-value",
"DATAPRISM_SECURITY_JWT_AUDIENCE": "your-value",
"DATAPRISM_SECURITY_JWT_JWK_SET_URI": "your-value",
"DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION": "your-value",
"DATAPRISM_SECURITY_POLICY_PURPOSES": "your-value",
"DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR": "your-value",
"DATAPRISM_PRIVACY_PROFILE": "your-value",
"DATAPRISM_PRIVACY_SCOPE_LIFETIME": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE": "your-value",
"DATAPRISM_AUDIT_SINK": "your-value",
"DATAPRISM_AUDIT_WRITER_ID": "your-value",
"DATAPRISM_AUDIT_FILE_PATH": "your-value",
"DATAPRISM_METRICS_SINK": "your-value",
"DATAPRISM_HAZELCAST_TOPOLOGY": "your-value",
"DATAPRISM_HAZELCAST_CLUSTERNAME": "your-value",
"DATAPRISM_HAZELCAST_JOIN_MODE": "your-value",
"DATAPRISM_HAZELCAST_JOIN_MEMBERS": "your-value",
"DATAPRISM_HAZELCAST_MEMBER_PORT": "your-value",
"DATAPRISM_OPERATOR_ENABLED": "your-value",
"DATAPRISM_OPERATOR_PORT": "your-value",
"DATAPRISM_OPERATOR_REQUIREDAUDIENCE": "your-value",
"DATAPRISM_OPERATOR_REQUIREDSCOPE": "your-value",
"DATAPRISM_SOURCES_CUSTOMER_BASE_URL": "your-value",
"DATAPRISM_SOURCES_CUSTOMER_TIMEOUT": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add data-prism --env LOADER_PATH=your-value --env DATAPRISM_SECURITY_JWT_ISSUER=your-value --env DATAPRISM_SECURITY_JWT_AUDIENCE=your-value --env DATAPRISM_SECURITY_JWT_JWK_SET_URI=your-value --env DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI=your-value --env DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL=your-value --env DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES=your-value --env DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION=your-value --env DATAPRISM_SECURITY_POLICY_PURPOSES=your-value --env DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR=your-value --env DATAPRISM_PRIVACY_PROFILE=your-value --env DATAPRISM_PRIVACY_SCOPE_LIFETIME=your-value --env DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID=your-value --env DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE=your-value --env DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE=your-value --env DATAPRISM_AUDIT_SINK=your-value --env DATAPRISM_AUDIT_WRITER_ID=your-value --env DATAPRISM_AUDIT_FILE_PATH=your-value --env DATAPRISM_METRICS_SINK=your-value --env DATAPRISM_HAZELCAST_TOPOLOGY=your-value --env DATAPRISM_HAZELCAST_CLUSTERNAME=your-value --env DATAPRISM_HAZELCAST_JOIN_MODE=your-value --env DATAPRISM_HAZELCAST_JOIN_MEMBERS=your-value --env DATAPRISM_HAZELCAST_MEMBER_PORT=your-value --env DATAPRISM_OPERATOR_ENABLED=your-value --env DATAPRISM_OPERATOR_PORT=your-value --env DATAPRISM_OPERATOR_REQUIREDAUDIENCE=your-value --env DATAPRISM_OPERATOR_REQUIREDSCOPE=your-value --env DATAPRISM_SOURCES_CUSTOMER_BASE_URL=your-value --env DATAPRISM_SOURCES_CUSTOMER_TIMEOUT=your-value -- docker run -i --rm -e LOADER_PATH -e DATAPRISM_SECURITY_JWT_ISSUER -e DATAPRISM_SECURITY_JWT_AUDIENCE -e DATAPRISM_SECURITY_JWT_JWK_SET_URI -e DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI -e DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL -e DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES -e DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION -e DATAPRISM_SECURITY_POLICY_PURPOSES -e DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR -e DATAPRISM_PRIVACY_PROFILE -e DATAPRISM_PRIVACY_SCOPE_LIFETIME -e DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID -e DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE -e DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE -e DATAPRISM_AUDIT_SINK -e DATAPRISM_AUDIT_WRITER_ID -e DATAPRISM_AUDIT_FILE_PATH -e DATAPRISM_METRICS_SINK -e DATAPRISM_HAZELCAST_TOPOLOGY -e DATAPRISM_HAZELCAST_CLUSTERNAME -e DATAPRISM_HAZELCAST_JOIN_MODE -e DATAPRISM_HAZELCAST_JOIN_MEMBERS -e DATAPRISM_HAZELCAST_MEMBER_PORT -e DATAPRISM_OPERATOR_ENABLED -e DATAPRISM_OPERATOR_PORT -e DATAPRISM_OPERATOR_REQUIREDAUDIENCE -e DATAPRISM_OPERATOR_REQUIREDSCOPE -e DATAPRISM_SOURCES_CUSTOMER_BASE_URL -e DATAPRISM_SOURCES_CUSTOMER_TIMEOUT ghcr.io/aindriub/data-prism-server:0.7.1运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"data-prism": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"LOADER_PATH",
"-e",
"DATAPRISM_SECURITY_JWT_ISSUER",
"-e",
"DATAPRISM_SECURITY_JWT_AUDIENCE",
"-e",
"DATAPRISM_SECURITY_JWT_JWK_SET_URI",
"-e",
"DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION",
"-e",
"DATAPRISM_SECURITY_POLICY_PURPOSES",
"-e",
"DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR",
"-e",
"DATAPRISM_PRIVACY_PROFILE",
"-e",
"DATAPRISM_PRIVACY_SCOPE_LIFETIME",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE",
"-e",
"DATAPRISM_AUDIT_SINK",
"-e",
"DATAPRISM_AUDIT_WRITER_ID",
"-e",
"DATAPRISM_AUDIT_FILE_PATH",
"-e",
"DATAPRISM_METRICS_SINK",
"-e",
"DATAPRISM_HAZELCAST_TOPOLOGY",
"-e",
"DATAPRISM_HAZELCAST_CLUSTERNAME",
"-e",
"DATAPRISM_HAZELCAST_JOIN_MODE",
"-e",
"DATAPRISM_HAZELCAST_JOIN_MEMBERS",
"-e",
"DATAPRISM_HAZELCAST_MEMBER_PORT",
"-e",
"DATAPRISM_OPERATOR_ENABLED",
"-e",
"DATAPRISM_OPERATOR_PORT",
"-e",
"DATAPRISM_OPERATOR_REQUIREDAUDIENCE",
"-e",
"DATAPRISM_OPERATOR_REQUIREDSCOPE",
"-e",
"DATAPRISM_SOURCES_CUSTOMER_BASE_URL",
"-e",
"DATAPRISM_SOURCES_CUSTOMER_TIMEOUT",
"ghcr.io/aindriub/data-prism-server:0.7.1"
],
"env": {
"LOADER_PATH": "your-value",
"DATAPRISM_SECURITY_JWT_ISSUER": "your-value",
"DATAPRISM_SECURITY_JWT_AUDIENCE": "your-value",
"DATAPRISM_SECURITY_JWT_JWK_SET_URI": "your-value",
"DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION": "your-value",
"DATAPRISM_SECURITY_POLICY_PURPOSES": "your-value",
"DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR": "your-value",
"DATAPRISM_PRIVACY_PROFILE": "your-value",
"DATAPRISM_PRIVACY_SCOPE_LIFETIME": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE": "your-value",
"DATAPRISM_AUDIT_SINK": "your-value",
"DATAPRISM_AUDIT_WRITER_ID": "your-value",
"DATAPRISM_AUDIT_FILE_PATH": "your-value",
"DATAPRISM_METRICS_SINK": "your-value",
"DATAPRISM_HAZELCAST_TOPOLOGY": "your-value",
"DATAPRISM_HAZELCAST_CLUSTERNAME": "your-value",
"DATAPRISM_HAZELCAST_JOIN_MODE": "your-value",
"DATAPRISM_HAZELCAST_JOIN_MEMBERS": "your-value",
"DATAPRISM_HAZELCAST_MEMBER_PORT": "your-value",
"DATAPRISM_OPERATOR_ENABLED": "your-value",
"DATAPRISM_OPERATOR_PORT": "your-value",
"DATAPRISM_OPERATOR_REQUIREDAUDIENCE": "your-value",
"DATAPRISM_OPERATOR_REQUIREDSCOPE": "your-value",
"DATAPRISM_SOURCES_CUSTOMER_BASE_URL": "your-value",
"DATAPRISM_SOURCES_CUSTOMER_TIMEOUT": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"data-prism": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"LOADER_PATH",
"-e",
"DATAPRISM_SECURITY_JWT_ISSUER",
"-e",
"DATAPRISM_SECURITY_JWT_AUDIENCE",
"-e",
"DATAPRISM_SECURITY_JWT_JWK_SET_URI",
"-e",
"DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES",
"-e",
"DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION",
"-e",
"DATAPRISM_SECURITY_POLICY_PURPOSES",
"-e",
"DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR",
"-e",
"DATAPRISM_PRIVACY_PROFILE",
"-e",
"DATAPRISM_PRIVACY_SCOPE_LIFETIME",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE",
"-e",
"DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE",
"-e",
"DATAPRISM_AUDIT_SINK",
"-e",
"DATAPRISM_AUDIT_WRITER_ID",
"-e",
"DATAPRISM_AUDIT_FILE_PATH",
"-e",
"DATAPRISM_METRICS_SINK",
"-e",
"DATAPRISM_HAZELCAST_TOPOLOGY",
"-e",
"DATAPRISM_HAZELCAST_CLUSTERNAME",
"-e",
"DATAPRISM_HAZELCAST_JOIN_MODE",
"-e",
"DATAPRISM_HAZELCAST_JOIN_MEMBERS",
"-e",
"DATAPRISM_HAZELCAST_MEMBER_PORT",
"-e",
"DATAPRISM_OPERATOR_ENABLED",
"-e",
"DATAPRISM_OPERATOR_PORT",
"-e",
"DATAPRISM_OPERATOR_REQUIREDAUDIENCE",
"-e",
"DATAPRISM_OPERATOR_REQUIREDSCOPE",
"-e",
"DATAPRISM_SOURCES_CUSTOMER_BASE_URL",
"-e",
"DATAPRISM_SOURCES_CUSTOMER_TIMEOUT",
"ghcr.io/aindriub/data-prism-server:0.7.1"
],
"env": {
"LOADER_PATH": "your-value",
"DATAPRISM_SECURITY_JWT_ISSUER": "your-value",
"DATAPRISM_SECURITY_JWT_AUDIENCE": "your-value",
"DATAPRISM_SECURITY_JWT_JWK_SET_URI": "your-value",
"DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES": "your-value",
"DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION": "your-value",
"DATAPRISM_SECURITY_POLICY_PURPOSES": "your-value",
"DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR": "your-value",
"DATAPRISM_PRIVACY_PROFILE": "your-value",
"DATAPRISM_PRIVACY_SCOPE_LIFETIME": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE": "your-value",
"DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE": "your-value",
"DATAPRISM_AUDIT_SINK": "your-value",
"DATAPRISM_AUDIT_WRITER_ID": "your-value",
"DATAPRISM_AUDIT_FILE_PATH": "your-value",
"DATAPRISM_METRICS_SINK": "your-value",
"DATAPRISM_HAZELCAST_TOPOLOGY": "your-value",
"DATAPRISM_HAZELCAST_CLUSTERNAME": "your-value",
"DATAPRISM_HAZELCAST_JOIN_MODE": "your-value",
"DATAPRISM_HAZELCAST_JOIN_MEMBERS": "your-value",
"DATAPRISM_HAZELCAST_MEMBER_PORT": "your-value",
"DATAPRISM_OPERATOR_ENABLED": "your-value",
"DATAPRISM_OPERATOR_PORT": "your-value",
"DATAPRISM_OPERATOR_REQUIREDAUDIENCE": "your-value",
"DATAPRISM_OPERATOR_REQUIREDSCOPE": "your-value",
"DATAPRISM_SOURCES_CUSTOMER_BASE_URL": "your-value",
"DATAPRISM_SOURCES_CUSTOMER_TIMEOUT": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
- Directory Spring Boot's PropertiesLauncher scans for extension jars; already set to /app/adapters by the image, but startup still fails with MISSING_SOURCE_ADAPTER until you bind-mount a reviewed Dat…
- OAuth2/OIDC issuer that mints the caller's JWT; required for every protected deployment
- Expected JWT audience claim for this deployment; required for every protected deployment
- HTTPS JWKS location used to verify caller JWTs; exactly one of this or DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URI is required, never both
DATAPRISM_SECURITY_JWT_ISSUER_DISCOVERY_URIenvAlternative HTTPS OIDC issuer-discovery location; set this instead of DATAPRISM_SECURITY_JWT_JWK_SET_URI, never both- JWT claim name that carries the caller's principal identifier; required, must differ from the roles and investigation claims
- JWT claim name that carries the caller's roles; required, must differ from the principal and investigation claims
- JWT claim name that carries the trusted investigation/case identifier; required, must differ from the principal and roles claims
- Comma-separated list of permitted purposes; at least one is required
- Example only — declare DATAPRISM_SECURITYPOLICY_ROLES_ per operator-defined role (no underscore between SECURITY and POLICY: Spring Boot's map-key enumeration under a hyphenated dataprism.security-po…
- Name of the reviewed privacy profile implementation to apply; required
- Positive duration (e.g. 8h) a privacy scope's synthetic identities remain valid; required
- Identifier of the pinned HMAC key used to derive synthetic identities; required
- Name of the environment variable holding the HMAC key material; exactly one of this or DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCE is required, never both, and never a literal key value
DATAPRISM_PRIVACY_HMAC_KEY_PROVIDER_REFERENCEenvReference to an approved secret provider holding the HMAC key material; set this instead of DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE, never both- Audit sink implementation: one of approved-sink, slf4j, hash-chained; required, never downgraded to no-op
- Writer/instance identity recorded on every audit entry; required
DATAPRISM_AUDIT_FILE_PATHenvPath to the durable, hash-chained audit log; required when DATAPRISM_AUDIT_SINK=hash-chained, refused as MISSING_AUDIT_FILE_PATH if absent for that sink, ignored otherwise- Metrics sink binding, currently only micrometer; required in production, never the framework no-op
- Cluster read-budget topology: embedded (shared across members that have joined one cluster; set cluster name and join mode) or single-node (enforced per process); required, never defaulted
DATAPRISM_HAZELCAST_CLUSTERNAMEenvHazelcast cluster name; required when DATAPRISM_HAZELCAST_TOPOLOGY=embedded, never dev, refused if set with single-nodeDATAPRISM_HAZELCAST_JOIN_MODEenvHow cluster members find each other: tcp-ip, kubernetes or none; required when DATAPRISM_HAZELCAST_TOPOLOGY=embedded (none is an explicit single member bound to 127.0.0.1), refused if set with single…DATAPRISM_HAZELCAST_JOIN_MEMBERSenvComma-separated member addresses (host or host:port); required when DATAPRISM_HAZELCAST_JOIN_MODE=tcp-ip, otherwise unusedDATAPRISM_HAZELCAST_MEMBER_PORTenvHazelcast member port, default 5701, never auto-incremented; must differ from the server, management and operator ports. Member traffic is unencrypted, so keep it on a private network. OptionalDATAPRISM_OPERATOR_ENABLEDenvEnables the operator surface; optional, off by defaultDATAPRISM_OPERATOR_PORTenvPort of the operator listener; required when DATAPRISM_OPERATOR_ENABLED=true, must differ from the server, management (OPERATOR_PORT_SHARED otherwise) and member ports, and has no fixed default (publ…DATAPRISM_OPERATOR_REQUIREDAUDIENCEenvJWT audience an operator token must carry; required when DATAPRISM_OPERATOR_ENABLED=trueDATAPRISM_OPERATOR_REQUIREDSCOPEenvJWT scope an operator token must carry; required when DATAPRISM_OPERATOR_ENABLED=true- Example only — declare DATAPRISM_SOURCES_ _BASE_URL (HTTPS) per configured source; at least one source, each with its own reviewed DataSourceAdapter bean, is required
- Example only — declare DATAPRISM_SOURCES_ _TIMEOUT (positive duration) per configured source; required alongside its base URL
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 AindriuB 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5837 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5837 个服务器的 68% 更新
- 基础检查结果等于或优于此分类中其他 5837 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Data Prism 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:LOADER_PATH, DATAPRISM_SECURITY_JWT_ISSUER, DATAPRISM_SECURITY_JWT_AUDIENCE, DATAPRISM_SECURITY_JWT_JWK_SET_URI, DATAPRISM_SECURITY_CALLER_CLAIMS_PRINCIPAL, DATAPRISM_SECURITY_CALLER_CLAIMS_ROLES, DATAPRISM_SECURITY_CALLER_CLAIMS_INVESTIGATION, DATAPRISM_SECURITY_POLICY_PURPOSES, DATAPRISM_SECURITYPOLICY_ROLES_INVESTIGATOR, DATAPRISM_PRIVACY_PROFILE, DATAPRISM_PRIVACY_SCOPE_LIFETIME, DATAPRISM_PRIVACY_HMAC_KEY_KEY_ID, DATAPRISM_PRIVACY_HMAC_KEY_ENVIRONMENT_VARIABLE, DATAPRISM_AUDIT_SINK, DATAPRISM_AUDIT_WRITER_ID, DATAPRISM_METRICS_SINK, DATAPRISM_HAZELCAST_TOPOLOGY, DATAPRISM_SOURCES_CUSTOMER_BASE_URL, DATAPRISM_SOURCES_CUSTOMER_TIMEOUT
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.7.1)于19天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Data Prism
Fail-closed privacy layer that pseudonymises enterprise API data for LLM agents and MCP clients.
Data Prism is an open-source privacy layer for Java/Spring teams putting LLM agents or MCP clients in front of internal APIs holding customer data. It pseudonymises personal data per privacy scope, refuses anything unclassified, and can keep a hash-chained audit trail.
What it is. A privacy enforcement layer for enterprise AI. It gives LLM agents useful, correlated business context — one consistent synthetic identity per entity within a privacy scope — while controlling which personal data crosses the AI boundary, and in what form.
Who it's for. Java/Spring platform and backend teams putting LLM agents or MCP clients in front of internal APIs that hold customer data. If nothing you run exposes personal data to a model, you don't need this.
Status: the walking skeleton and every slice through S9a are built, with 18 Maven submodules (19 Maven projects in the reactor counting the root pom-packaged aggregator itself) and a passing test suite. The privacy engine, correlation and consistency findings, parallel mTLS connectors, an embedded Hazelcast identity cache and read budget (shared only across members that have joined one cluster; see multiple instances), an OAuth2 resource server with session-derived PrivacyContext, audit and metrics are all real and exercised end to end. The standalone server is the primary deployment surface; the Spring Boot starter is the embedded option. A one-command local Compose quickstart also exists: see "Try it" below. Two MCP tools ship today, get_entity_context and compare_entity_sources — the other two named in the design review, search_entity_data and describe_entity_model, are not yet built (docs/tools.md "Not yet built"). A durable, append-only, hash-chained audit sink and an offline AuditChainVerifier ship as of 0.3.0, opt-in via dataprism.audit.sink: hash-chained; the verifier catches an edit or deletion inside a writer's chain, but cannot detect truncation of a writer's most recent records or the deletion of a whole process boot's records, and the trail does not resist an operator, or anyone else, who already has write access to the file (docs/audit.md "What this does and does not prove"). Not built: the re-identification operator surface (deferred past V1 by decision, see docs/architecture.md#decisions-worth-knowing) and the Elasticsearch connector and its search tools. See docs/plan/PLAN.md for what is open.
The problem
An organisation wants an LLM to investigate live business data spread across several systems. Giving the model direct API access is not acceptable: those APIs carry personal and confidential data, each system represents the same entity differently, and raw identifiers let anything downstream correlate across sessions.
The obvious fix — redact everything sensitive — destroys the investigation. Once three systems' names for one person are all [REDACTED], the model cannot tell whether it is looking at one person or three.
What Data Prism does
It sits between the two and does two things that are easy to confuse:
It makes identity consistent. One subject gets one synthetic identity across every source, derived deterministically from (scope, subject, namespace, algorithm version, key) — never random, never stored in plaintext, and reproducible without the cache. The same person in three systems reads as one person to the model.
It leaves the data inconsistent, and says so. If those three systems disagree about a name, the answer carries a finding that says they disagree. The platform never makes enterprise data look cleaner than it is. That distinction is the point of the project:
Identity representation becomes consistent. Underlying data inconsistencies
become *more* visible, not less.
Pseudonyms are scoped. The same person in two different investigations gets two different synthetic identities, so nothing correlates across cases by accident.
What it is not
Not an API gateway, not an ETL platform, not a master-data system, not an identity provider, and not an entity-resolution engine — correlation requires a key the sources already share, behind a documented SPI. It carries no business domain: no Customer, Taxpayer or Employee type exists outside the example application.
It is not anonymisation. Under GDPR Art. 4(5), pseudonymised data is still personal data. Sending Data Prism output to a third-party model is still processing, and still needs a lawful basis, a DPIA, and a transfer mechanism where the provider is outside the EU. The platform reduces exposure; it does not remove the obligation.
Try it
The fastest way to see a real MCP call answered by the real privacy engine — no local JDK, no Maven install, one command:
docker compose up
pulls the published ghcr.io/aindriub/data-prism-quickstart- images (pin one with QUICKSTART_IMAGE_TAG=0.7.0; run docker compose -f compose.yaml -f compose.build.yaml up --build instead to build every image from source) and brings up the standalone server, a synthetic fixture API and a local HTTPS JWT issuer, proving an agent-compatible get_entity_context call returns a pseudonymised response. Walk through it in docs/quickstart.md; connect your own agent client to either that stack or a real deployment via docs/agents/.
Once you have seen the demo, protect your own API: docs/quickstart.md ends with a "What next" section pointing at docs/protect-your-own-api.md, a YAML-only walkthrough from a real JSON REST API to a working get_entity_context call.
If you found this on the MCP registry
The ghcr.io/aindriub/data-prism-server image listed there is published as a multi-architecture manifest list covering linux/amd64 and linux/arm64, each built and verified natively — docker run on Apple Silicon or any other arm64 host pulls the arm64 image directly, no emulation required.
It is not a one-command install, on either architecture. docker run alone yields a server that refuses to start: DataPrismContractValidator demands a reviewed DataSourceAdapter bean for every configured source, and DataPrismProperties.validate() demands a full deployment configuration (JWT issuer/audience/JWKS, caller-claim mappings, security policy, HMAC key reference, audit sink, metrics sink, Hazelcast topology). Neither ships in the image. Two things an operator must supply themselves before it serves anything:
- A reviewed `DataSourceAdapter` (and `IdentityResolver`) jar for each API you are protecting, mounted onto the image's loader path.
- A deployment configuration satisfying the
dataprism.*vocabulary.
docs/configuration.md is the authoritative, complete contract for both. The "Try it" section above is a local Compose fixture for evaluation, not this image or that configuration.
Documentation
The full set of user docs is also published, rendered and searchable, at https://aindriub.github.io/data-prism/.
User docs
Each row links the site page and the repo file it is built from.
| Doc | Site | What it covers |
|---|---|---|
docs/quickstart.md | quickstart/ | One-command local Compose demonstration — start here |
docs/protect-your-own-api.md | protect-your-own-api/ | Pointing Data Prism at your own API instead of the fixture |
docs/configuration.md | configuration/ | The authoritative, complete dataprism.* deployment configuration contract |
docs/tools.md | tools/ | What each shipped MCP tool takes and returns, worked examples |
docs/extending.md | extending/ | Protecting a new source: a reviewed Java adapter, or the configuration-driven JSON REST mode |
docs/audit.md | audit/ | What the hash-chained audit trail records, and how to verify it |
docs/architecture.md | architecture/ | Module map, dependency rules, the boundaries that must not be crossed, dated decisions |
docs/agents/ | agents/ | Connecting an MCP agent client, local fixture or authenticated remote |
docs/agents/stdio.md | agents/stdio/ | The local stdio fixture workflow: a real MCP tool call with no JWT, network call or source system |
docs/agents/remote-http.md | agents/remote-http/ | The authenticated Streamable HTTP workflow against a real MCP endpoint; no development bypass |
docs/faq.md | faq/ | Direct answers on pseudonymisation, PII detection, Java requirements, the audit trail and prompt injection |
docs/comparison.md | comparison/ | How Data Prism compares to Presidio, LLM Guard, NeMo Guardrails and MCP gateways or proxies |
docs/use-cases/pseudonymise-customer-data-spring-boot.md | use-cases/pseudonymise-customer-data-spring-boot/ | Pseudonymising customer data from a Spring Boot API before an LLM agent sees it |
docs/use-cases/gdpr-data-minimisation-mcp.md | use-cases/gdpr-data-minimisation-mcp/ | GDPR data minimisation for MCP tools |
docs/use-cases/consistent-pseudonyms-across-systems.md | use-cases/consistent-pseudonyms-across-systems/ | Keeping one customer recognisable across systems without exposing identity |
CHANGELOG.md | changelog/ | Every notable Data Prism change by version, in Keep a Changelog format |
Internal / project working docs
Not published on the site.
| Doc | What it covers |
|---|---|
docs/design-review.md | Amendments to the specification, with reasoning. Authoritative |
docs/development-plan.md | Slice order, sizing, and the decisions that block the first one |
docs/pack.md | The original specification. Superseded and historical; describes tools that were never built |
| [docs/conventions.md](docs/conventio
只显示了开头部分;其余内容请在仓库中阅读