io.github.faulknerwayne73-droid/kojiru-mcp
NPM · KOJIRU-AGENTKIT · 3 COMPONENTS
Kojiru Recourse Layer — agent credit primitives (ACS, stake, draw, anchor) live on Base mainnet
Last scanned (12 hours ago)
Scores higher than 2% of npm servers
Category Crypto and Web3
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 uuid 8.3.2, reached via @coinbase/agentkit > @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 823 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 66 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
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.
- 17 Oct 26 −2
No change was recorded against any check on this day. Supply Chain Security went from 87 to 81.
- 16 Oct 26 +2
No change was recorded against any check on this day. Supply Chain Security went from 82 to 87.
- 15 Oct 26 −2
- CVE-2026-104182 affects this package: high ▼ security
- CVE-2026-71429 affects this package: high ▼ security
- CVE-2026-104183 affects this package: high ▼ security
- 14 Oct 26 +2
- CVE-2026-104183 no longer affects this package ▲ security
- CVE-2026-71429 no longer affects this package ▲ security
- CVE-2026-104182 no longer affects this package ▲ security
- 11 Oct 26 −2
- CVE-2026-104183 affects this package: high ▼ security
- CVE-2026-104182 affects this package: high ▼ security
- CVE-2026-71429 affects this package: high ▼ security
- 5 Oct 26 +2
- CVE-2026-71429 no longer affects this package ▲ security
- 30 Sept 26 −1
No change was recorded against any check on this day. Supply Chain Security went from 83 to 81.
- 28 Sept 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 18 Oct 2026 · Analysed npm/kojiru-agentkit@0.1.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 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3gc7-fjrx-p6mg | CVE-2025-3194 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-848j-6mx2-7j84 | CVE-2025-14505 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | no |
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-58qx-3vcg-4xpx | CVE-2026-45736 | medium | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-96hv-2xvq-fx4p | CVE-2026-48779 | 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 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 5 |
| Stale | 62 |
| No linked repository | 9 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the io.github.faulknerwayne73-droid/kojiru-mcp server?
io.github.faulknerwayne73-droid/kojiru-mcp runs locally as an npm package, launched with npx -y kojiru-agentkit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kojiru-agentkit
claude mcp add faulknerwayne73-droid-kojiru-mcp -- npx -y kojiru-agentkit
What is the io.github.faulknerwayne73-droid/kojiru-mcp server?
io.github.faulknerwayne73-droid/kojiru-mcp is listed in the public MCP registry as io.github.faulknerwayne73-droid/kojiru-mcp. Kojiru Recourse Layer, agent credit primitives (ACS, stake, draw, anchor) live on Base mainnet. This page covers its npm package (kojiru-agentkit).
Is the io.github.faulknerwayne73-droid/kojiru-mcp server safe to use?
io.github.faulknerwayne73-droid/kojiru-mcp scores 28 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 18 October 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.
Is the io.github.faulknerwayne73-droid/kojiru-mcp server still maintained?
io.github.faulknerwayne73-droid/kojiru-mcp is still listed as active in the MCP registry. We last reached this channel on 18 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 io.github.faulknerwayne73-droid/kojiru-mcp server under?
io.github.faulknerwayne73-droid/kojiru-mcp 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.