Witness
Production proofs for breaking JSON Schema/MCP changes; UNKNOWN/NO_WITNESS_FOUND not compatible.
我該用這個嗎
品質與安全性
A
根據工具定義與協定合規性的自動化分析。
上下文成本
~212Token(工具定義)
~1.7 KB典型回應大小
極小的注意力影響(128k 上下文的 0.17%)
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"witness": {
"url": "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
}
}
}遠端端點
https://witness-edge-phase-c-test.witness-test.workers.dev/mcpstreamable-httphttps://witness-contractwitness-production.witness-test.workers.dev/mcpstreamable-http它能做什麼
工具清單
工具(1)
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
⚪contract_witness(mode, old_schema, new_schema, options)
Produce a concrete independently revalidated JSON-Schema/MCP backward-compatibility witness before merge/deploy. UNKNOWN or NO_WITNESS_FOUND never means compatible.
輸入結構描述
{
"type": "object",
"properties": {
"mode": {
"type": "string",
"enum": [
"input_backward_compatibility",
"output_backward_compatibility"
]
},
"old_schema": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
]
},
"new_schema": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
]
},
"options": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
},
"required": [
"mode",
"old_schema",
"new_schema"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}社群
證據
近期觀測
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具