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.

io.github.nailuoGG/anki-mcp-server

NPM · ANKI-MCP-SERVER · SCANNED SEP 20

MCP server enabling LLMs to interact with Anki flashcard software through AnkiConnect

Available components

npm · anki-mcp-server 54
0 this week 54 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.18.2, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 38 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency69
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to nailuoGG/anki-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 354 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.Unverified
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Tool Safety0
  • Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 3 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.nailuoGG/anki-mcp-server server?

io.github.nailuoGG/anki-mcp-server runs locally as an npm package, launched with npx -y anki-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · anki-mcp-server

# add to Claude Code
claude mcp add nailuogg-anki-mcp-server -- npx -y anki-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "nailuogg-anki-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "anki-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nailuogg-anki-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "anki-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add nailuogg-anki-mcp-server -- npx -y anki-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nailuogg-anki-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "anki-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nailuogg-anki-mcp-server --command npx --arg -y --arg anki-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  nailuogg-anki-mcp-server:
    command: "npx"
    args: ["-y", "anki-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nailuogg-anki-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "anki-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add nailuogg-anki-mcp-server -t stdio -c npx -a -y anki-mcp-server
// mcp.json
{
  "mcpServers": {
    "nailuogg-anki-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "anki-mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 19 Sept 26 0
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
  • 18 Sept 26 +1
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
  • 17 Sept 26 0
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
  • 16 Sept 26 −3
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • Stability: 0.97 → pass security
  • 14 Sept 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
  • 13 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

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 20 Sept 2026 · Analysed npm/anki-mcp-server@0.1.8

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 nailuoGG/anki-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/nailuoGG/anki-mcp-server/.github/workflows/release.yml@refs/heads/master
Rekor log index 571971830
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:b6bfbf189c62546688e7aa50a5e92dc19fc2111186a96315e6a0ba1e7581cf184e920312be68cf4e715ff1b7052c2c145704642936e84b40ad48402ca

Background: How many MCP packages publish verified provenance →

Vulnerabilities 31 findings
ID CVE Severity Vector Fix available
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8r9q-7v3j-jr4g CVE-2026-0621 high yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-35jp-ww65-95wh CVE-2026-44494 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N yes
GHSA-3g43-6gmg-66jw CVE-2026-44495 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-3p68-rc4w-qgx5 CVE-2025-62718 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-3w6x-2g7m-8v23 CVE-2026-42044 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-42h9-826w-cgv3 CVE-2026-67313 medium yes
GHSA-43fc-jf86-j433 CVE-2026-25639 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-445q-vr5w-6q77 CVE-2026-42037 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-5c9x-8gcm-mpgx CVE-2026-42034 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-62hf-57xw-28j9 CVE-2026-42039 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6chq-wfr3-2hj9 CVE-2026-42035 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-777c-7fjr-54vf CVE-2026-44488 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7q8q-rj6j-mhjq CVE-2026-67319 medium yes
GHSA-898c-q2cr-xwhg CVE-2026-44490 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-fvcv-3m26-pcqx CVE-2026-40175 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-hfxv-24rg-xrqf CVE-2026-44496 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-j5f8-grm9-p9fc CVE-2026-44486 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-jqh4-m9w3-8hp9 CVE-2026-67317 medium yes
GHSA-m7pr-hjqh-92cm CVE-2026-42038 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-mmx7-hfxf-jppx CVE-2026-67316 medium yes
GHSA-p92q-9vqr-4j8v CVE-2026-44487 high yes
GHSA-pf86-5x62-jrwf CVE-2026-42033 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-pmv8-rq9r-6j72 CVE-2026-67312 medium yes
GHSA-pmwg-cvhr-8vh7 CVE-2026-42043 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-q8qp-cvcw-x6jj CVE-2026-42264 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vf2m-468p-8v99 CVE-2026-42036 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-w9j2-pvgh-6h63 CVE-2026-42041 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhjh-pmcv-23jw CVE-2026-42040 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-xx6v-rp6x-q39c CVE-2026-42042 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 114 packages
Packages resolved 114
Stale 38
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

The sandbox run completed and this package exposed no tools.

Common questions

What is the io.github.nailuoGG/anki-mcp-server server?

io.github.nailuoGG/anki-mcp-server is listed in the public MCP registry as io.github.nailuoGG/anki-mcp-server. MCP server enabling LLMs to interact with Anki flashcard software through AnkiConnect. This page covers its npm package (anki-mcp-server).

Is the io.github.nailuoGG/anki-mcp-server server safe to use?

io.github.nailuoGG/anki-mcp-server scores 54 out of 100 on VerifyMCP. We recorded 31 known advisories against it as of 20 September 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 io.github.nailuoGG/anki-mcp-server server expose?

io.github.nailuoGG/anki-mcp-server exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the io.github.nailuoGG/anki-mcp-server server still maintained?

io.github.nailuoGG/anki-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 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.nailuoGG/anki-mcp-server server under?

io.github.nailuoGG/anki-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.