Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Jev-Style

PYPI · JEV-STYLE · SCANNED OCT 3

Local 2B and 0.8B decision models: calibrated yes/no, choice and score answers for your agent.

Available components

pypi · jev-style 80
80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to lawrence3699/jev-style). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 772 tokens (~154/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Jev-Style MCP server?

Jev-Style runs locally as a PyPI package, launched with uvx jev-style. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · jev-style

# add to Claude Code
claude mcp add lawrence3699-jev-style -- uvx jev-style
// .cursor/mcp.json
{
  "mcpServers": {
    "lawrence3699-jev-style": {
      "command": "uvx",
      "args": [
        "jev-style"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lawrence3699-jev-style": {
      "command": "uvx",
      "args": [
        "jev-style"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add lawrence3699-jev-style -- uvx jev-style
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lawrence3699-jev-style": {
      "type": "local",
      "command": [
        "uvx",
        "jev-style"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lawrence3699-jev-style --command uvx --arg jev-style
# ~/.hermes/config.yaml
mcp_servers:
  lawrence3699-jev-style:
    command: "uvx"
    args: ["jev-style"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lawrence3699-jev-style": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "jev-style"
      ]
    }
  }
}
# add to Vellum
assistant mcp add lawrence3699-jev-style -t stdio -c uvx -a jev-style
// mcp.json
{
  "mcpServers": {
    "lawrence3699-jev-style": {
      "command": "uvx",
      "args": [
        "jev-style"
      ]
    }
  }
}
Changelog

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.

  • 3 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Oct 26 +2
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.17 ▲ functional
    • Package version: 0.3.0 → 0.4.0 functional
  • 28 Sept 26 +11
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 51

    First indexed and scored.

Diagnostics

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 3 Oct 2026 · Analysed pypi/jev-style@0.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo lawrence3699/jev-style
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/lawrence3699/jev-style/.github/workflows/release.yml@refs/tags/v0.4.0
Rekor log index 3063654531
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:00bdf1ab24ca0f766a84c1b779c1b7ec594dba8106e07818ffdc78919d3dd04e

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 45 packages
Packages resolved 45
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~566 tokens

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 →

Tool Tokens
choice ~112

Pick the best option for the state. options: a list of option names, or {option: description or null} (1..255 options, order kept). Returns {"choice", "probabilities": {option: p}, "confidence": 0..1, ...}. confidence = (k * p_max - 1) / (k - 1) for k options: 0 = uniform, 1 = certain.

NameTypeReqDescription
options–yes–
questionstringyes–
state–yes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

decide ~208

Ask several typed questions about one state in a single call (the state is read once). state: text, or a JSON object/array (serialised for the model). questions: {id: question}. A question is {"type": "noul", "instructions": "<statement or yes/no question>", "criteria"?: {"true": "...", "false": "..."}} {"type": "choice", "instructions": "...", "criteria": {"<option>": "<description or null>", ...}} {"type": "score", "instructions": "...", "criteria": ["<lowest level>", ..., "<highest level>"]} Score levels can also be {"label": "...", "description": "..."}. Returns the systemone-compatible response: answers per id (noul -> p_true; choice -> choice, probabilities, confidence; score -> score, legend, probabilities, confidence), usage and timing.

NameTypeReqDescription
questionsobjectyes–
state–yes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

model_info ~24

Model id, context and question budgets, and which backend this MCP server uses.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

noul ~113

Probability that a yes/no statement about the state is true. question: e.g. "The customer asks for a refund." or "Is the invoice overdue?" true_means / false_means: optional descriptions of what counts as true / false. Returns {"p_true": 0..1, "answer": p_true >= 0.5, ...}. Gate with your own thresholds.

NameTypeReqDescription
false_means–––
questionstringyes–
state–yes–
true_means–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

score ~109

Place the state on an ordered scale. levels: 2..10 levels, lowest first; each a label or {"label": ..., "description": ...}. Returns {"score": expected level index (0 = first level, may fall between levels), "level": label of the most likely level, "legend": {index: label}, "probabilities": {index: p}, "confidence", ...}.

NameTypeReqDescription
levelsarrayyes–
questionstringyes–
state–yes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

Common questions

What is the Jev-Style MCP server?

Jev-Style is an MCP server listed in the public MCP registry as io.github.lawrence3699/jev-style. Local 2B and 0.8B decision models: calibrated yes/no, choice and score answers for your agent. This page covers its PyPI package (jev-style).

Is the Jev-Style MCP server safe to use?

Jev-Style scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. Its build provenance is signed and verified. 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 Jev-Style MCP server expose?

Jev-Style exposes 5 tools: decide, noul, choice, score, model_info. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.

Is the Jev-Style MCP server still maintained?

Jev-Style is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Jev-Style MCP server under?

Jev-Style declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.