TypeSafe Jev
NPM · JEVCORE-MCP
MCP server over TypeSafe Jev: typed ask, rank and check judgments return calibrated probabilities.
Available components
Last scanned (15 hours ago)
Scores higher than 49% of npm servers
Category AI and Machine Learning
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 61 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 761 tokens (~253/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −2
- Stability: pass → 0.90 functional
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/jevcore-mcp@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
jev_ask Ask Jev typed questions ~285
Ask TypeSafe Jev one or more typed questions about a single piece of state. Jev does not generate text: it returns a selected option and calibrated probabilities. Use it for judgments the rest of the work branches on — routing, classifying, scoring, triaging. Do NOT use it to write prose, explain, summarize, or generate code. Question types: "noul" is yes/no and returns the probability of true; "choice" picks one of the criteria keys you declare; "score" places the state on an ordered scale whose levels you declare in ascending order. A noul may also declare "boundary" — what true means and what false means — which is worth supplying whenever the line between them is not obvious. Batch related questions into one call: they are answered against the same state in one round-trip. A score question answers with a numeric "score" that may fall between levels, a "legend" mapping each level index to its description, and probabilities per level. This tool returns probabilities, not decisions — apply your own confidence threshold before acting, and treat a low-confidence answer as unknown rather than picking for it.
| Name | Type | Req | Description |
|---|---|---|---|
| questions | object | yes | Map of question id to question. Ids are the keys of the response. |
| state | – | – | The evidence to judge. This is transmitted to TypeSafe when a live key is configured. |
No output schema declared.
No examples provided.
jev_check Check a claim against evidence ~132
Check whether a piece of evidence supports a specific claim. Returns "supported", "contradicted", "conflicted", "insufficient", or "unknown", with the underlying probabilities. The distinction between "not supported" and "contradicted" is the reason to use this rather than reading the evidence yourself. It judges one claim against the evidence you give it. It does not search for evidence, and it cannot detect that you omitted the decisive passage.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The single claim to check. |
| evidence | string | yes | The evidence to judge it against. Quote rather than paraphrase. |
No output schema declared.
No examples provided.
jev_rank Rank candidates with Jev ~344
Rank a list of candidates by how well each satisfies one stated criterion. Returns every candidate with an independent relevance probability, sorted. Use it to order search hits, triage a backlog, or find the one item that answers a question. The probabilities are independent per-candidate judgments, NOT a distribution that sums to 1. A flat set of scores means "none of these stands out", not a fine-grained ordering. What you send is capped, and the two caps behave differently. The candidate list is truncated at 16,000 characters, and the reply carries `truncated: true` when that happens — check for it, because a cut list is still ranked and the scores then describe what Jev actually read rather than what you sent. The generated questions are refused at 4,000 characters instead: exceeding that gives you an error asking for fewer or smaller items, never a silent best-N, so retrying the same call cannot help. Because the criterion is repeated into every candidate's question, that second cap is what bounds the candidate count — measured, an ordinary criterion fits 20 candidates and a 400-character criterion fits 7, while candidate length does not change the count at all and only starts truncating the list past roughly 1,600 characters per candidate.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | One string per candidate. The serialized list is truncated at 16,000 characters, and the reply reports `truncated: true` when it was cut. |
| criterion | string | – | What "relevant" means, as a yes/no question about one candidate. |
| query | string | yes | The task or question the candidates are ranked against. |
No output schema declared.
No examples provided.
How do I install the TypeSafe Jev MCP server?
TypeSafe Jev runs locally as an npm package, launched with npx -y jevcore-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · jevcore-mcp
claude mcp add perrylink-jevcore -- npx -y jevcore-mcp
What is the TypeSafe Jev MCP server?
TypeSafe Jev is an MCP server listed in the public MCP registry as io.github.PerryLink/jevcore. MCP server over TypeSafe Jev: typed ask, rank and check judgments return calibrated probabilities. This page covers its npm package (jevcore-mcp).
Is the TypeSafe Jev MCP server safe to use?
TypeSafe Jev scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 TypeSafe Jev MCP server expose?
TypeSafe Jev exposes 3 tools: jev_ask, jev_rank, jev_check. Their descriptions and schemas cost roughly 761 tokens of context every time the server is loaded.
Is the TypeSafe Jev MCP server still maintained?
TypeSafe Jev is still listed as active in the MCP registry. We last reached this channel on 21 November 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 TypeSafe Jev MCP server under?
TypeSafe Jev 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.
What did VerifyMCP test on the TypeSafe Jev MCP server?
VerifyMCP ran 16 checks on TypeSafe Jev, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.