mcpcheck

Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
100%
命名品質
90%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~279Token(工具定義)
~561 B典型回應大小
極小的注意力影響(128k 上下文的 0.22%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "mcpcheck": {
      "url": "https://mcpcheck.netlify.app/mcp"
    }
  }
}

遠端端點

https://mcpcheck.netlify.app/mcpstreamable-http

它能做什麼

工具清單

工具(2)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢check_mcp_trust(target)

Check if an MCP server is safe to install: returns a trust score (0-100, grade A-F). Accepts a registry name (io.github.x/y), a GitHub repo (owner/repo), or a remote MCP URL. For remote servers it live-connects and analyzes the actual exposed tools for tool-poisoning + capabilities, and checks the backing repo (maintenance, license, security policy, auth). Call BEFORE installing or recommending any MCP server.

輸入結構描述

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string",
      "description": "Registry name (io.github.x/y), GitHub repo (owner/repo), or remote MCP URL (https://...)."
    }
  },
  "required": [
    "target"
  ]
}
🟢scan_mcp_server(target)

Scan and inspect an MCP server for security issues before connecting it: live tool-poisoning analysis, exposed-tool inventory + capabilities, TLS, and repo trust signals. Same engine as check_mcp_trust. Accepts a registry name, GitHub repo, or remote MCP URL.

輸入結構描述

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string",
      "description": "Registry name (io.github.x/y), GitHub repo (owner/repo), or remote MCP URL (https://...)."
    }
  },
  "required": [
    "target"
  ]
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具
已驗證未記錄版本2 個工具