cache-proxy
LLM caching proxy (x402 USDC on Base) - exact + semantic cache. Free health.
我該用這個嗎
品質與安全性
A
根據工具定義與協定合規性的自動化分析。
上下文成本
~240Token(工具定義)
~1.1 KB典型回應大小
極小的注意力影響(128k 上下文的 0.19%)
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"cache-proxy": {
"url": "https://cache.api.ainode.tech/mcp"
}
}
}遠端端點
https://cache.api.ainode.tech/mcpstreamable-http它能做什麼
工具清單
工具(2)
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
⚪health(echo)
Health check. Returns server status and optional echo.
輸入結構描述
{
"type": "object",
"properties": {
"echo": {
"type": "string",
"description": "Optional string to echo back"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡cache_query(provider, path, body, api_key, cache_ttl)
Send an LLM request through the caching proxy. Returns cached response if available, otherwise proxies to upstream LLM.
輸入結構描述
{
"type": "object",
"properties": {
"provider": {
"type": "string",
"enum": [
"openai",
"anthropic"
],
"description": "LLM provider to proxy to"
},
"path": {
"type": "string",
"description": "API path (e.g. /v1/chat/completions)"
},
"body": {
"type": "string",
"description": "JSON request body as string"
},
"api_key": {
"type": "string",
"description": "API key for the upstream provider"
},
"cache_ttl": {
"type": "number",
"description": "Cache TTL in seconds (default 86400)"
}
},
"required": [
"provider",
"path",
"body",
"api_key"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}社群
證據
近期觀測
已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具