Jev Filter
NPM · @APIXLY/JEV-FILTER
Read-only semantic filtering, code search, log triage and traceable evidence for AI agents.
Available components
Last scanned (19 hours ago)
Scores higher than 52% of npm servers
Category Code Search and Documentation
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
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to apixly-ai/jev-filter). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability47
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 285 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 59
First indexed and scored.
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 24 Oct 2026 · Analysed npm/@apixly/jev-filter@0.4.2
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | apixly-ai/jev-filter |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/apixly-ai/jev-filter/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 3421903763 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9b737ca1cf18d98623a360688e76998befe9d1836bb05853af82926d6661d36ffbd97cc6b968b086b187936c4fca5acc743337d9d8d565716ac56674f |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
filter_records ~54
Filter supplied records with explicit task/context. Returns selected and unresolved IDs plus evidence receipts.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | object | – | – |
| budget_chars | integer | – | – |
| records | array | yes | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
read_evidence ~52
Read one bounded record from an unchanged receipt produced in this server session. A receipt never grants action authority.
| Name | Type | Req | Description |
|---|---|---|---|
| archive | string | yes | – |
| budget_chars | integer | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
search_code ~94
Collect bounded code candidates inside the configured workspace and judge relevance. Exact regex scope is always reported.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | object | – | – |
| budget_chars | integer | – | – |
| expand_callers | boolean | – | – |
| limit | integer | – | – |
| max_files | integer | – | – |
| pattern | string | yes | – |
| query | string | – | – |
| root | string | – | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
triage_events ~66
Redact and correlate supplied JSON events, then select relevant incidents. No log file or shell access.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | object | – | – |
| budget_chars | integer | – | – |
| events | array | yes | – |
| group_by | string | – | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Jev Filter MCP server?
Jev Filter runs locally as an npm package, launched with npx -y @apixly/jev-filter. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @apixly/jev-filter
claude mcp add apixly-ai-jev-filter -- npx -y @apixly/jev-filter
What is the Jev Filter MCP server?
Jev Filter is an MCP server listed in the public MCP registry as io.github.apixly-ai/jev-filter. Read-only semantic filtering, code search, log triage and traceable evidence for AI agents. This page covers its npm package (@apixly/jev-filter).
Is the Jev Filter MCP server safe to use?
Jev Filter scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. It declares no install or post-install scripts. 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 Filter MCP server expose?
Jev Filter exposes 4 tools: filter_records, search_code, triage_events, read_evidence. Their descriptions and schemas cost roughly 266 tokens of context every time the server is loaded.
Is the Jev Filter MCP server still maintained?
Jev Filter is still listed as active in the MCP registry. We last reached this channel on 24 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 Filter MCP server under?
Jev Filter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.