‹ directory
84MCP SCORE
B
xquik
https://xquik.com/mcp
4 tools1 resources~2.1k tok/req100% annot.proto 2026-07-28
Score by pillar
Security ·2088
Tool design ·18100
Schemas / desc ·16100
Reliability ·14100
Context-cost ·1257
Compliance ·1272
Coverage ·860
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
2.1ktokens for
tools/listPaid on every request. Lean footprint for 4 tools.
this server2.1k
median≈ 3k
MCP primitive coverage
the quality score covers tools4
Tools
1
Resources
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Compliance · MEDIUM−3.4
JSON-RPC-compliant errors 0/2 → errors not compliant with the JSON-RPC spec → clients break unpredictably
Security · HIGH−2.4
[MCP05] execution + unconstrained free-string param -> command/shell injection → MCP security flaw → tool: execute
Security — OWASP MCP Top 10
MCP05HIGH
executeBadge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fxquik.com%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About xquik — FAQ
Is the xquik MCP server safe to use?+
CheckMCP audited xquik and gave it an MCP Score of 84/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 xquik?+
xquik scores 84/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 xquik expose, and what is its context cost?+
xquik exposes 4 tools, and its tools/list response costs roughly 2.1k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was xquik scored?+
By probing the live MCP endpoint (https://xquik.com/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.