MindDory Brain MCP server

• capture_grammar_mistakeFree

  Log a grammar mistake the user just made in the target language, creating a grammar point in their Minddory deck. Use it proactively whenever the user writes a target-language sentence with a clear, correctable error (wrong tense, agreement, word_choice, word_order, missing or wrong article, preposition, gender, conjugation, spelling, pluralization). By connecting Minddory the user opted IN to automatic capture, so log it as you go - do not ask permission first or turn it into a yes/no question. The user connected Minddory to catch and review these patterns; you do not need to announce each log. Pass the original text + correction + error_type. Multiple mistakes in one message = multiple calls. VARIANT RULE: Always pass the user's full BCP-47 variant in the lang field (e.g. en-gb, not en) - get it from get_system_instructions on first turn. Before logging, check that the "error" is not actually a valid regional variant form (US past-simple vs UK present-perfect with "just/already", US "in the hospital" vs UK "in hospital", US "color" vs UK "colour", BR gerund vs PT "a + infinitive", etc.). When the variant is unspecified (base ISO only), treat ALL regional forms as valid. Better to skip a borderline call than to mark a valid variant form as wrong. error_type must be one of: tense, agreement, word_choice, word_order, article, preposition, spelling, pluralization, conjugation, gender, other. Feeds the user's Grammar Patterns view at app.minddory.com/grammar.

• capture_wordFree

  Capture a target-language word or phrase to the user's Minddory vocabulary deck (a flashcard in the "Chat Discoveries" folder when the word is new, otherwise a context encounter). The user connected Minddory so their assistant builds their deck from real conversations, so use this proactively to log notable target-language vocabulary they encounter, use, or ask about. By connecting Minddory the user opted IN to automatic capture, so just capture as you chat - do not pause to ask permission for each word, and do not turn capturing into a yes/no question. You do not need to announce each capture, but answer honestly if the user asks what you have saved. Use the `words` array to capture several from one message; include a `gloss` (short source-language translation) and `context` (the sentence) when you can. Skip stop words, proper nouns, numbers, and words shorter than 3 characters (CJK / Hangul exempt). ALWAYS pass `lang` — the ISO code of the captured word's own language (you know it from the conversation); the call is rejected without it and the target language is never guessed. `source_lang` (the user's native language) is optional and defaults to their deck. This is the primary tracking signal of Minddory, so capture diligently.

• check_wordsFree

  Batch lookup: for a list of target-language words, tell me which ones are already in the user's Minddory deck and how well they know each. Use this BEFORE glossing or capturing vocabulary from a message - it answers "which of these are actually new to this user" in one call, so you can skip words they have already mastered, gloss only the genuinely new ones, and notice when a word they are currently failing shows up in conversation. Each result is {word, in_deck, mastery, translation, next_review_at, due}; mastery is one of not_in_deck, new, review, struggling, mastered. The response also pulls out the three lists you usually act on - `not_in_deck`, `known` and `struggling` - so you do not have to sort them yourself; words in mid-review are in `words` only. Entries that could not be answered as sent are listed in `skipped` as {input, reason: blank|duplicate, answered_as?} - a duplicate WAS answered, under the entry named by `answered_as`. Omit `lang` and it resolves to the user's own primary learning language (`lang_defaulted: true` in the response says so); pass it whenever you know which language you are in. Prefer this over calling get_card once per word.

• get_active_vocabFree

  Get the user's most actively encountered target-language words (from past capture_word + log_interaction events), ranked by frequency over a lookback window. Use to surface "frontier" words the user keeps touching when they ask "what should I learn next" or when you want context-aware suggestions.

• get_cardFree

  Single card detail by word (case-insensitive). Returns translation, mastery, and last 10 events.

• get_known_wordsFree

  Words the user has verified known via flashcard practice. Paginated keyset on flashcards.id.

• get_queueFree

  Cards due now and due within the next 24 hours.

• get_recent_activityFree

  Event log slice with optional surface filter and keyset pagination on answers.id.

• get_system_instructionsFree

  Call this at the START of every new conversation, before your first reply, to load the user's Minddory setup and your role as their proactive language partner: CEFR level, target/source languages, due-card count, weak words, and how to capture. The user connected Minddory to actively improve their language through this chat, so use it to tailor your help to their level and goals. Pass `lang` when you know which language the user wants to practice right now - the language they are conversing in, or one they named explicitly (including a regional variant like en-us or en-gb) - so the returned profile is scoped to that language. Re-call this tool with the new `lang` if the user switches practice language or requests a specific variant mid-conversation.

• get_user_profileFree

  Profile snapshot: CEFR level, target/source languages, due card count, weak words, recent lookups. Pass `lang` to scope the snapshot to one learning language (for users learning several); omit it for the user's primary language.

• log_interactionFree

  Append a generic interaction event to the answers log. Use for lookups, AI discussions, and reading-in-context signals.

• mark_demonstratedFree

  Confidence-weighted spaced-repetition boost when the user has used a word correctly: the card moves further out in the review schedule. Logs an answer row even if no flashcard exists.

• mark_struggledFree

  Spaced-repetition degrade for a word the user just got wrong: the card comes back sooner. ease_factor drops, interval resets, repetitions reset.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1343ms20/20
• Tool poisoning13 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 51 days ago12/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

87/100

higher than 73% of 48,255 servers

Tools

13

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

306 ms

faster than 47% of 30,031 servers

MindDory Brain: common questions

Is MindDory Brain MCP server safe?

Yes, by our scan: it is graded A (87/100). Read the MindDory Brain safety report

How do I install MindDory Brain?

It runs remotely at api.minddory.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does MindDory Brain need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is MindDory Brain maintained?

The last commit was 54 days ago (2026-09-11). The latest release is v1.0.2.

Is MindDory Brain up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does MindDory Brain compare with other MCP servers?

safety score 87/100 (higher than 73% of 48,255 servers); tools 13 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.