Anki Connect MCP Server

@spacholski1225/anki-connect-mcp npm v1.0.6

Published by @spacholski1225 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Anki Connect integration

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 46

Each tool and what it can reach — statically extracted from the published source.

  • gui_browseingests untrusted input
  • add_noteno sensitive capability
  • add_notesno sensitive capability
  • add_tagsno sensitive capability
  • are_dueno sensitive capability
  • are_suspendedno sensitive capability
  • can_add_notesno sensitive capability
  • cards_infono sensitive capability
  • cards_to_notesno sensitive capability
  • change_deckno sensitive capability
Show 36 more tools ↓
  • clone_deck_config_idno sensitive capability
  • create_flashcardno sensitive capability
  • deck_namesno sensitive capability
  • deck_names_and_idsno sensitive capability
  • delete_decksno sensitive capability
  • find_cardsno sensitive capability
  • find_notesno sensitive capability
  • get_deck_configno sensitive capability
  • get_decksno sensitive capability
  • get_intervalsno sensitive capability
  • get_tagsno sensitive capability
  • gui_add_cardsno sensitive capability
  • gui_answer_cardno sensitive capability
  • gui_current_cardno sensitive capability
  • gui_deck_browserno sensitive capability
  • gui_deck_overviewno sensitive capability
  • gui_deck_reviewno sensitive capability
  • gui_exit_ankino sensitive capability
  • gui_show_answerno sensitive capability
  • gui_show_questionno sensitive capability
  • gui_start_card_timerno sensitive capability
  • model_field_namesno sensitive capability
  • model_fields_on_templatesno sensitive capability
  • model_namesno sensitive capability
  • model_names_and_idsno sensitive capability
  • multino sensitive capability
  • notes_infono sensitive capability
  • remove_deck_config_idno sensitive capability
  • remove_tagsno sensitive capability
  • save_deck_configno sensitive capability
  • set_deck_config_idno sensitive capability
  • suspendno sensitive capability
  • unsuspendno sensitive capability
  • update_note_fieldsno sensitive capability
  • upgradeno sensitive capability
  • versionno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.6 latest A 96/100 0 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/spacholski1225-anki-connect-mcp/badge.svg)](https://mcptrustchecker.com/registry/spacholski1225-anki-connect-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/spacholski1225-anki-connect-mcp"><img src="https://mcptrustchecker.com/registry/spacholski1225-anki-connect-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/spacholski1225-anki-connect-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @spacholski1225/anki-connect-mcp --online

Use the free API → How scoring works

More in Web, Search & Scraping