
Jagent MCP server
Which MCP servers are Jagent's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-03
- Registry namecom.jev-agent/jagentverified in the MCP registry
The registry name sits under jev-agent.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-03
- Tools7
- Server calls itselfjagent
- Server version1.0.0
- Protocol version2025-06-18
On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 162 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 6 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer761 ms
- Space in an agent's context≈ 1,441 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsB · 86 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 6 of 7
What an agent can do with it
- not sure · triage support tickets into queues and severity levels
- cannot · route each prompt to the smallest capable model
- not sure · classify invoices by expense category and review flag
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
check_resumeScore a resume, optionally against a job posting: a 0-100 match score, the posting's keywords found and missing (matched literally, as an ATS search would), ATS format checks, the level fit, and the probability a recruiter would move it…
grade_essayGrade one essay against a built-in rubric. kind "essay": six criteria and a letter grade, for class essays at middle school, high school or college level. kind "common-app": a Common App personal statement (pass the prompt number, 1-7)…
grade_with_rubricGrade one or more submissions (up to 30, in parallel) against a rubric you supply: each criterion scored on a 3- to 6-point scale, summed per submission. Each submission is graded in its own call, so its score never depends on the others.
judge_yes_noAsk any yes/no question about a text and get the probability that the answer is yes. Use for checks and gates, e.g. 'Does this reply answer the customer's question?'.
judge_choicePick the option that best fits a text, with a probability for every option and a confidence. Options map an id to a description of when it applies.
judge_scorePlace a text on an ordered scale you define (lowest level first) and get the nearest level, the exact position and a probability for each level.
compare_versionsWhich of two versions is stronger for a stated purpose. Asked twice with the order swapped and averaged, because the model favors the second option on close calls; if the two orders disagree the result is a tie.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"jagent": {
"type": "http",
"url": "https://jev-agent.com/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http jev-agent https://jev-agent.com/api/mcpclaude.ai, ChatGPT and other clients: add https://jev-agent.com/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.