io.github.JayOfemi/byakugan
NPM · @JAYOFEMI/AI-CHECKER
Private, on-device AI-text analysis including detection, AI-tell spans, and reuse overlap.
Available components
Last scanned (58 minutes ago)
Scores higher than 66% of npm servers
Category Developer Tools
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
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 129 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 355 tokens (~88/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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@jayofemi/ai-checker@1.0.0
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 | 30 |
| 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 →
check_grammar Check grammar ~78
Run a rule-based grammar and style check over the text, fully on-device, and return each issue with its character span, a message, the flagged text, and suggested fixes. Use it to tidy grammar and phrasing, before or after rewriting the flagged AI tells. Deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to analyze. |
No output schema declared.
No examples provided.
check_reuse Check reuse overlap ~89
Compare the text against reference documents you provide, using word shingles, and return the share of overlap and the verbatim shared passages. This is a local check against the documents passed in. It does not search the web or any plagiarism database. Deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| references | array | yes | One or more of your own documents to compare against. |
| text | string | yes | The text to analyze. |
No output schema declared.
No examples provided.
detect_ai_text Detect AI text ~101
Score how likely a passage reads as AI-written, fully on-device, with a per-signal breakdown and a confidence band. Returns a 0 to 100 likelihood, never a yes/no verdict. The signal is directional and biased against non-native English writers, so treat it as a second opinion and not proof. Get a read here, then call find_ai_tells to locate the spans worth rewriting.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to analyze. |
No output schema declared.
No examples provided.
find_ai_tells Find AI tells ~87
Locate the exact character spans that read as AI, covering stock phrasing, long dashes, and formulaic sentence openers. Returns a list of spans with start, end, the matched text, and a note. Use these to rephrase only the flagged parts and leave the rest of the writing intact. Deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to analyze. |
No output schema declared.
No examples provided.
How do I install the io.github.JayOfemi/byakugan MCP server?
io.github.JayOfemi/byakugan runs locally as an npm package, launched with npx -y @jayofemi/ai-checker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @jayofemi/ai-checker
claude mcp add jayofemi-byakugan -- npx -y @jayofemi/ai-checker
What is the io.github.JayOfemi/byakugan MCP server?
io.github.JayOfemi/byakugan is an MCP server listed in the public MCP registry as io.github.JayOfemi/byakugan. Private, on-device AI-text analysis including detection, AI-tell spans, and reuse overlap. This page covers its npm package (@jayofemi/ai-checker).
Is the io.github.JayOfemi/byakugan MCP server safe to use?
io.github.JayOfemi/byakugan scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.JayOfemi/byakugan MCP server expose?
io.github.JayOfemi/byakugan exposes 4 tools: detect_ai_text, find_ai_tells, check_reuse, check_grammar. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Is the io.github.JayOfemi/byakugan MCP server still maintained?
io.github.JayOfemi/byakugan is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.JayOfemi/byakugan MCP server under?
io.github.JayOfemi/byakugan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.