‹ directory
86MCP SCORE
B
jagent
https://jev-agent.com/api/mcp
7 tools~1.7k tok/req100% annot.proto 2026-07-28
Score by pillar
Security ·20100
Tool design ·18100
Schemas / desc ·1658
Reliability ·14100
Context-cost ·1287
Compliance ·12100
Coverage ·850
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
1.7ktokens for
tools/listPaid on every request. Lean footprint for 7 tools.
this server1.7k
median≈ 3k
MCP primitive coverage
the quality score covers tools7
Tools
0
Resources · none
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Schemas / desc · HIGH−3.5
54% typed+described params → schema = the contract the agent fills in → more malformed calls
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
[](https://checkmcp.dev/report?url=https%3A%2F%2Fjev-agent.com%2Fapi%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About jagent — FAQ
Is the jagent MCP server safe to use?+
CheckMCP audited jagent and gave it an MCP Score of 86/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 jagent?+
jagent scores 86/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 jagent expose, and what is its context cost?+
jagent exposes 7 tools, and its tools/list response costs roughly 1.7k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was jagent scored?+
By probing the live MCP endpoint (https://jev-agent.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.