Ai Vendor Data Trust Index

io.github.oscarlopez-gif由 GitHub 帳號 oscarlopez-gif 發布v0.1.0更新於 Oct 24, 2026

Source-cited data-handling comparison of 11 AI vendors: training, retention, opt-out.

已驗證Streamable HTTP可網頁執行安全與監控AI 與機器學習

概覽

AI 產生的概覽

遠端 MCP 伺服器,提供附來源引用的答案,說明 11 家 AI 供應商如何處理你的資料:是否用輸入訓練、保留期限與退出選項。

可以做什麼
取得某家供應商資料處理方式的淺白結論,涵蓋訓練、保留與退出等欄位,並附原文引用、來源連結、信心程度與查核日期;模糊情況標示為不明確而非猜測。跨所有已收錄供應商比較單一資料信任欄位,例如是否用你的輸入進行訓練,並附引用。透過付費工具取得某家供應商的完整引用紀錄。涵蓋的供應商包括 OpenAI、Anthropic、Google Vertex 與 Gemini、Azure OpenAI、AWS Bedrock、Microsoft 365 Copilot、GitHub Copilot、Mistral 和 Meta Llama。
適用情境
適合在選擇或比較 AI 供應商時,快速取得可引用的資料處理政策證據;也適合助理需要附引用地回答關於輸入訓練、資料保留或退出選項的問題。
執行需求
遠端 streamable-HTTP 端點;未宣告需要本機執行環境、帳號、API 金鑰或請求標頭。完整紀錄工具為付費,需要回應 x402 式付款挑戰。
安裝前請注意
完整供應商紀錄工具為付費,使用可能產生費用。README 稱付款流程為模擬 x402,真實結算尚未建置,付款行為可能不可靠。內容為政策摘要而非法律意見,且索引僅涵蓋 11 家供應商。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Ai Vendor Data Trust Index,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.oscarlopez-gif%2Fai-vendor-data-trust-index/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "ai-vendor-data-trust-index": {
      "type": "http",
      "url": "https://trust.oscar-lopez.com/mcp"
    }
  }
}

README

AI Vendor Data-Trust Index

[License: MIT] [Data: CC BY 4.0] [MCP]

A source-cited record of how AI products handle your data — whether the vendor trains on your inputs, whether zero data retention is available, and whether you can opt out — across 11 products (OpenAI, Anthropic, Google Vertex & Gemini, Azure OpenAI, AWS Bedrock, Microsoft 365 Copilot, GitHub Copilot, Mistral, Meta Llama). Every value carries a verbatim quote from the vendor's live policy, a source URL, a confidence level, and the date it was checked. Ambiguous cases are marked unclear rather than guessed. An automated verifier re-checks the policies weekly and only publishes a value when a verbatim quote supports it — otherwise it holds the last human-verified value.

For AI agents (MCP)

This is a remote MCP server (streamable-http). Add it to your MCP client:

json
{  "mcpServers": {    "ai-vendor-data-trust": {      "type": "streamable-http",      "url": "https://trust.oscar-lopez.com/mcp"    }  }}

Tools: get_ai_vendor_trust_headline (free — verdict + cited fields for one vendor), get_ai_vendor_trust_compare (free — one field across all vendors), get_ai_vendor_trust (paid, x402 — full cited record). Vendor IDs: openai-api, openai-consumer, anthropic-api, google-vertex, google-gemini-consumer, microsoft-copilot, azure-openai, aws-bedrock, mistral-api, meta-llama, github-copilot.

Endpoints

Free (CORS-enabled):

  • GET /v1/ai-trust/headline?vendor=openai-api — verdict + 3 cited headline fields
  • GET /v1/ai-trust/compare?field=trains_on_your_data — one field across all vendors

Paid (mock x402 — 402 challenge → echo {resource,nonce,mac} in X-PAYMENT):

  • GET /v1/ai-trust/vendor?vendor=openai-api — full cited record
  • GET /v1/ai-trust/all — bulk export

Other: POST /mcp (JSON-RPC: 2 free tools + 1 paid), GET /openapi.json, GET /.well-known/x402, GET /admin/config?key=<STATS_TOKEN> (config lever).

Deploy

bash
cd ai-trust-indexnpm installnpm run db:create                 # → paste the returned database_id into wrangler.jsoncnpm run schema:remote             # create tables (drops existing)npm run seed:remote               # load the 6-vendor provisional seednpx wrangler deploy --dry-run --outdir dist   # verify build (no auth)npm run deploy                    # deploy the Worker# In Cloudflare: add custom domain trust.oscar-lopez.com to this Worker.# Set real secrets before public use:npx wrangler secret put MOCK_PAYMENT_SECRETnpx wrangler secret put STATS_TOKEN

Verifier (v1) — automated weekly re-check

Pipeline in src/verifier.ts: fetch each vendor's pinned policy URLs → content-hash diff (skip if unchanged) → model extraction of {value, quote} (Workers AI by default; frontier via AI Gateway if configured) → verbatim quote-verification (the candidate quote must be a literal substring of the fetched source, else rejected) → confidence gate. Only a quote-verified DEFINITE value auto-publishes (verified_by='auto'); anything else is queued in review_queue and the last good published value is held (never auto-downgraded to unclear). A failed fetch holds the last good value and flags the URL. Runs weekly via cron (0 12 * * 1) and on demand.

Admin endpoints (key-gated by STATS_TOKEN):

  • GET /admin/verify?key=…[&force=1][&vendor=ID] — run the verifier now
  • GET /admin/review?key=… — list open review-queue candidates
  • GET /admin/review-resolve?key=…&id=N&action=approve|reject — approve (publishes as human) or reject
  • GET /admin/verify-selftest?key=… — proves the quote gate rejects a fabricated quote / accepts a verbatim one

Extractor: defaults to Workers AI (EXTRACTOR_MODEL, needs no external key). To use a frontier model, set AI_GATEWAY_URL + AI_GATEWAY_TOKEN (secret) and point EXTRACTOR_MODEL at the provider model.

Not yet built

The /ai-trust site page's changelog view, real x402 settlement, breadth expansion into new vendors (free tier) and the depth/channel schema (paid tier). See ../AI-Trust-Index_v1-Spec_Verifier-and-Depth.md.

來源:README.md,提交 2f7360f

工具

3

get_ai_vendor_trust_headline

FREE. Plain-language, source-cited verdict on how an AI vendor handles your data (trains-on-data, zero-retention, opt-out).

輸入參數vendor必填

get_ai_vendor_trust_compare

FREE. Compare one data-trust field (default trains_on_your_data) across all tracked vendors, with citations.

輸入參數field

get_ai_vendor_trust

PAID (x402). Full source-cited data-trust record for one vendor: every field, quote, source URL, confidence, date.

輸入參數vendor必填

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。