Data Prism
概要
作者による説明(英語の原文)
Fail-closed privacy layer that pseudonymises enterprise API data for LLM agents and MCP clients.
PopNx MCPの3つの柱
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
- 利用者の声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
必要なもの
- DockerDockerのインストール
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
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月9日にチェック
- ✓ 合格
作者とリポジトリが一致
レジストリ名は、リポジトリを所有するGitHubアカウント AindriuB で確認済みです
- … 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
- … 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
- – 対象外
エンドポイントが応答する
これはパソコンで動くため、インターネット上のエンドポイントはありません
- – 対象外
OAuthでサインイン
パソコンで動き、代わりにローカルの設定を使います
- … 未チェック
ツールの説明に隠れた指示がない
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
検索・AIの記憶のほかのサーバーとの比較i
- このカテゴリのほかの5744件のうち0%よりスターが多い
- このカテゴリのほかの5744件のうち69%より最近レジストリに公開
- 基本チェックの結果が、このカテゴリのほかの5744件のうち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)がレジストリに届いたのは17 日前です。
どのアプリで使えますか?
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにDockerも必要です。
代わりに使えるものは?
同じカテゴリには:Context7, Codebase Memory, Exa
代わりの候補
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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
冒頭だけを表示しています。続きはリポジトリで読めます