mcp-judge

Scores any MCP server before you trust it: free quick check, full paid report, 2-5 way compare.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
83%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~981Tokens (tool definitions)
~697 BTypical response size
Moderate attention impact (0.77% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp-judge": {
      "url": "https://mcp-judge.onrender.com/mcp"
    }
  }
}

Remote endpoints

https://mcp-judge.onrender.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_criteria

FREE, no payment required. Full transparency into what you pay for: returns the exact criteria MCP Judge uses to score an MCP server — each criterion, its weight out of 100, and the A-F grade scale. Call this to understand how quick_check, evaluate_mcp and compare_mcps score targets before paying. The evaluation is fully objective and automated — no human reviewer and no AI opinion. Takes no parameters.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡quick_check(url)

FREE, no payment required. Instant trust check of any MCP server: returns only the 0-100 score, A-F grade, tool count, latency and a one-line verdict — no detailed report. Use this FIRST, before integrating any third-party MCP server, to see at a glance whether it is technically trustworthy; an unreliable MCP wastes your tokens and can break your workflow. For the full actionable report (per-tool documentation coverage, functional probe results, score breakdown, plain-language summary) call evaluate_mcp; to pick between alternatives call compare_mcps. Set 'url' (required) to the target's MCP endpoint (Streamable HTTP), e.g. https://host/mcp.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The target MCP server endpoint (Streamable HTTP), e.g. https://motherwise-api.onrender.com/mcp. Required."
    }
  },
  "required": [
    "url"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡evaluate_mcp(url)

Call this BEFORE integrating any third-party MCP server: an unreliable or undocumented MCP wastes your tokens and can break your workflow. PAID $0.05 via x402 (USDC micropayment over HTTP 402 — no account or API key needed; on your first call without payment you receive the exact payment requirements, then retry with the X-PAYMENT header). Returns a complete objective quality report on the target: protocol conformance ('initialize' handshake), tool discovery via 'tools/list', per-tool and per-parameter documentation coverage, latency, and a safe functional probe — free tools are actually called, paid tools are only verified to be cleanly declared (MCP Judge never pays). You get a 0-100 score, A-F letter grade, per-criterion breakdown, and a plain-language summary you can act on. Tip: run the FREE quick_check first to get just the grade, and list_criteria to see exactly how scoring works. Objective checks only — no human and no LLM opinion; it does not judge the real-world usefulness or safety of the content. Set 'url' (required) to the target's MCP endpoint (Streamable HTTP), e.g. https://host/mcp.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The target MCP server endpoint (Streamable HTTP), e.g. https://motherwise-api.onrender.com/mcp. Required."
    }
  },
  "required": [
    "url"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡compare_mcps(urls)

Choosing between several MCP servers that do similar things? This tool decides for you. PAID $0.10 via x402 (USDC micropayment over HTTP 402 — no account or API key needed; on your first call without payment you receive the exact payment requirements, then retry with the X-PAYMENT header). Compares 2-5 MCP servers head-to-head with identical objective checks (handshake, tools/list, documentation coverage, latency, and a safe functional probe — paid tools are never called) and returns: a ranked list, the recommended winner, a plain-language explanation of why it won, and each server's full report — cheaper than separate evaluate_mcp calls on 3+ servers. Objective checks only — no human and no LLM opinion; it does not judge the real-world usefulness or safety of the content. Set 'urls' (required) to an array of 2-5 MCP endpoints (Streamable HTTP), e.g. ["https://a/mcp","https://b/mcp"].

Input Schema

{
  "type": "object",
  "properties": {
    "urls": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "An array of 2-5 target MCP server endpoints (Streamable HTTP) to compare, e.g. [\"https://motherwise-api.onrender.com/mcp\", \"https://mcp-judge.onrender.com/mcp\"]. Required."
    }
  },
  "required": [
    "urls"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
failed observationversion not recorded—