io.github.giachi85it-ux/mcp-judge
REMOTE · MCP-JUDGE.ONRENDER.COM · SCANNED SEP 20
Scores any MCP server before you trust it: free quick check, full paid report, 2-5 way compare.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.giachi85it-ux/mcp-judge server?
io.github.giachi85it-ux/mcp-judge is a hosted endpoint at https://mcp-judge.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp-judge.onrender.com
claude mcp add --transport http giachi85it-ux-mcp-judge 'https://mcp-judge.onrender.com/mcp'
{
"mcpServers": {
"giachi85it-ux-mcp-judge": {
"url": "https://mcp-judge.onrender.com/mcp"
}
}
} {
"servers": {
"giachi85it-ux-mcp-judge": {
"type": "http",
"url": "https://mcp-judge.onrender.com/mcp"
}
}
} [mcp_servers.giachi85it-ux-mcp-judge] url = "https://mcp-judge.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"giachi85it-ux-mcp-judge": {
"type": "remote",
"url": "https://mcp-judge.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add giachi85it-ux-mcp-judge --url 'https://mcp-judge.onrender.com/mcp' --transport streamable-http
mcp_servers:
giachi85it-ux-mcp-judge:
url: "https://mcp-judge.onrender.com/mcp" {
"McpServers": {
"giachi85it-ux-mcp-judge": {
"Transport": "http",
"Url": "https://mcp-judge.onrender.com/mcp"
}
}
} assistant mcp add giachi85it-ux-mcp-judge -t streamable-http -u 'https://mcp-judge.onrender.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Sept 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.33 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 −10
- Stability: pass → 0.33 functional
- 1 Sept 26 +55
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: 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. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Destructive annotations: pass functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.33 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Aug 26 0
- 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. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp-judge.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 756bcb97dcf1455f0ebf70e5dbe07256 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-judge.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-judge.onrender.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://mcp-judge.onrender.com/mcp | HTTPS enforced | 301 | https://mcp-judge.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_mcps ~273
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"].
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | 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. |
No output schema declared.
No examples provided.
evaluate_mcp ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The target MCP server endpoint (Streamable HTTP), e.g. https://motherwise-api.onrender.com/mcp. Required. |
No output schema declared.
No examples provided.
list_criteria ~93
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
quick_check ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The target MCP server endpoint (Streamable HTTP), e.g. https://motherwise-api.onrender.com/mcp. Required. |
No output schema declared.
No examples provided.
What is the io.github.giachi85it-ux/mcp-judge server?
io.github.giachi85it-ux/mcp-judge is listed in the public MCP registry as io.github.giachi85it-ux/mcp-judge. Scores any MCP server before you trust it: free quick check, full paid report, 2-5 way compare. This page covers its hosted endpoint (https://mcp-judge.onrender.com/mcp).
Is the io.github.giachi85it-ux/mcp-judge server safe to use?
io.github.giachi85it-ux/mcp-judge scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.giachi85it-ux/mcp-judge server expose?
io.github.giachi85it-ux/mcp-judge exposes 4 tools: list_criteria, quick_check, evaluate_mcp, compare_mcps. Their descriptions and schemas cost roughly 831 tokens of context every time the server is loaded.
Does the io.github.giachi85it-ux/mcp-judge server require authentication?
No. We connected to io.github.giachi85it-ux/mcp-judge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.giachi85it-ux/mcp-judge server still maintained?
io.github.giachi85it-ux/mcp-judge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.