# io.github.giachi85it-ux/mcp-judge (remote · mcp-judge.onrender.com)

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

- Trust score: 62/100 (medium)
- Change this week: +48
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp-judge.onrender.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/giachi85it-ux-mcp-judge/mcp-judge.md), [page](https://verifymcp.io/servers/giachi85it-ux-mcp-judge/mcp-judge)

## Channel facts

- Endpoint: `https://mcp-judge.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 831 tokens (~207/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http giachi85it-ux-mcp-judge https://mcp-judge.onrender.com/mcp
```

### Codex

```toml
[mcp_servers.giachi85it-ux-mcp-judge]
url = "https://mcp-judge.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "giachi85it-ux-mcp-judge": {
      "type": "remote",
      "url": "https://mcp-judge.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add giachi85it-ux-mcp-judge --url https://mcp-judge.onrender.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  giachi85it-ux-mcp-judge:
    url: "https://mcp-judge.onrender.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "giachi85it-ux-mcp-judge": {
      "type": "http",
      "url": "https://mcp-judge.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-01 (score 61, +38)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-07-31 (score 23, +9)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 14, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 14, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 14)

First indexed and scored.

## MCP tools (4)

### `list_criteria` (~93 tokens)

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.

### `quick_check` (~179 tokens)

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 parameters:

- `url` (string, required): The target MCP server endpoint (Streamable HTTP), e.g. https://motherwise-api.onrender.com/mcp. Required.

### `evaluate_mcp` (~286 tokens)

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 parameters:

- `url` (string, required): The target MCP server endpoint (Streamable HTTP), e.g. https://motherwise-api.onrender.com/mcp. Required.

### `compare_mcps` (~273 tokens)

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 parameters:

- `urls` (array, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/giachi85it-ux-mcp-judge/mcp-judge#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 61
- 2026-07-31: 23
- 2026-07-30: 14
- 2026-07-29: 14
- 2026-07-28: 14
- 2026-07-27: 14
- 2026-07-26: 14

## Links

- Remote endpoint: https://mcp-judge.onrender.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/giachi85it-ux-mcp-judge/mcp-judge/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/giachi85it-ux-mcp-judge/mcp-judge/changelog.json
- HTML version of this page: https://verifymcp.io/servers/giachi85it-ux-mcp-judge/mcp-judge