‹ directory
85MCP SCORE
B

jithox-engine

https://jithox.com/api/mcp
8 tools~4.4k tok/req100% annot.proto 2024-11-05
View public page ›
Xin
Raw JSON ›

Score by pillar

Security ·20100
Tool design ·1885
Schemas / desc ·1690
Reliability ·14100
Context-cost ·1259
Compliance ·1286
Coverage ·870

reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)

Context-cost

4.4ktokens for tools/list

Paid on every request. Lean footprint for 8 tools.

this server4.4k
median≈ 3k

MCP primitive coverage

the quality score covers tools
8
Tools
0
Resources · none
0
Prompts · none

Why this score — causal attribution

Each penalty: measure → mechanism → effect → Δscore.

Compliance · MEDIUM−1.6

proto 2024-11-05 (4 rev. behind 2025-11-25) → outdated protocol version → recent features unavailable, recent clients weakened

Compliance · LOW−0.6

no OAuth discovery (.well-known missing) → RFC 9728/8414 not exposed → auth not auto-discoverable by clients

Badge — paste it in your README

MCP Score badge — jithox-engine[![MCP Score](https://checkmcp.dev/badge/jithox-com.svg?url=https%3A%2F%2Fjithox.com%2Fapi%2Fmcp)](https://checkmcp.dev/report?url=https%3A%2F%2Fjithox.com%2Fapi%2Fmcp)

About jithox-engine — FAQ

Is the jithox-engine MCP server safe to use?+
CheckMCP audited jithox-engine and gave it an MCP Score of 85/100 (grade B) — good — only minor issues. The audit runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets, command injection, the lethal trifecta) against the live endpoint; see the per-pillar breakdown and the "why this score" attribution on this page, and re-audit anytime at checkmcp.dev.
What is the MCP Score of jithox-engine?+
jithox-engine scores 85/100 (grade B) on CheckMCP's vendor-neutral audit across six weighted pillars — security, tool design, schemas, context-cost, compliance and coverage — with reliability measured and shown but not yet credited.
How many tools does jithox-engine expose, and what is its context cost?+
jithox-engine exposes 8 tools, and its tools/list response costs roughly 4.4k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was jithox-engine scored?+
By probing the live MCP endpoint (https://jithox.com/api/mcp), inspecting its tools, schemas and protocol compliance, running an OWASP MCP Top 10 security pass, and measuring the token cost of tools/list — then attributing every penalty as measure → mechanism → effect. The methodology is open: checkmcp.dev/#methodology.