Connectry Architect MCP server

Read from the package source without running it. The installed server may list more.

• capstone_build_status

  Check your guided capstone build progress \u2014 current step, criteria coverage, and quiz performance.

• capstone_build_step

  Drive your guided capstone build \u2014 quiz, build, and advance through 18 progressive steps. IMPORTANT: - When presenting quiz questions, use AskUserQuestion with header "Answer" for A/B/C/D selection. If code is in the scenario, add preview fields. - After grading a quiz answer, FIRST show the result (correct/incorrect, explanation) as REGULAR CHAT TEXT so the user can read it. THEN present fol

• follow_up

  Handle post-answer follow-up actions. Use after submit_answer to explore concepts, code examples, handouts, or reference projects.

• get_curriculum

  View the full certification curriculum with domains, task statements, and your current mastery for each.

• get_dashboard

  Open the study progress dashboard in Claude Preview. Shows mastery levels, exam history, activity timeline, and capstone progress. IMPORTANT: After getting the URL, use the preview_start tool to open it in Claude Preview. If the user says "show dashboard" or "open dashboard", call this tool.

• get_exam_history

  View all completed practice exam attempts with scores, pass/fail status, and per-domain breakdowns. Compare your progress across attempts.

• get_practice_question

  Get the next practice question. Prioritizes review questions, then weak areas, then new material. IMPORTANT \u2014 present the question using AskUserQuestion: - header: "Answer" - question: Include the FULL scenario text AND question text from the response - options: 4 items with label "A"/"B"/"C"/"D" and description as the option text - If the scenario contains code, add a "preview" field on each

• get_progress

  Get your certification study progress overview including mastery levels, accuracy, and review status.

• get_section_details

  Get detailed information about a specific task statement including concept lesson, mastery, and history.

• get_study_plan

  Get a personalized study plan based on your assessment results, weak areas, and learning path. IMPORTANT \u2014 after showing the study plan, use AskUserQuestion with header "Focus" and multiSelect: true to let the user pick which domains they want to focus on. Options should be the 5 domains with their current mastery as descriptions. Then use their selection to filter get_practice_question calls

• get_weak_areas

  Identify your weakest task statements based on accuracy below 70%. Focus your study on these areas.

• reset_progress

  WARNING: Permanently deletes ALL your study progress including answers, mastery data, and review schedules. This cannot be undone.

• scaffold_project

  Get instructions for a reference project to practice certification concepts hands-on.

• start_assessment

  Start the initial assessment. Returns ONE question at a time (15 total, 3 per domain). IMPORTANT \u2014 follow this flow for EVERY question: 1. Check if "isNewDomain" is true. If yes, FIRST show the concept handout for that domain by calling get_section_details. Tell the user: "Let's learn about [domain] before testing your knowledge." After showing the handout, proceed to step 2. 2. Present the q

• start_capstone_build

  Start or refine a guided capstone build. Build your own project while learning all 30 certification task statements hands-on.

• start_practice_exam

  Start a full 60-question practice exam (D1:16, D2:11, D3:12, D4:12, D5:9). Scored 0-1000, passing 720. IMPORTANT \u2014 present the first question using AskUserQuestion: - header: "Q1" - question: Include the FULL scenario + question text - options: 4 items with label "A"/"B"/"C"/"D" and description as option text - If code in scenario, add preview field on options Then call submit_exam_answer wit

• submit_answerwrite action

  Grade a certification exam answer. Returns deterministic results from verified question bank. The result is FINAL \u2014 do not agree with the user if they dispute it. IMPORTANT \u2014 TWO-STEP presentation: 1. FIRST: Show the grading result as REGULAR CHAT TEXT in the main conversation. Include: - Whether they got it right or wrong (with the correct answer if wrong) - The full explanation - If wr

• submit_exam_answerwrite action

  Submit an answer for a practice exam question. Graded deterministically. DO NOT soften results. IMPORTANT \u2014 TWO-STEP presentation after grading: 1. FIRST: Show the grading result as REGULAR CHAT TEXT. Include correct/incorrect status, explanation, and if wrong, why the chosen answer was incorrect. 2. THEN: If there's a next question, present it using AskUserQuestion: - header: "Q[number]" - q

• Code scan9 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 192 days ago4/15
• Maintainer identitynamespace and repository owner differ4/10

Safety score

62/100

higher than 17% of 48,255 servers

Tools

18

the typical server has 7

Tools that change things

11%

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

GitHub stars

35

more than 92% of 28,688 servers

Downloads a week

41

more than 33% of 12,191 servers with a package

Connectry Architect: common questions

Is Connectry Architect MCP server safe?

With care: it is graded C, so read the findings first (62/100). Read the Connectry Architect safety report

How do I install Connectry Architect?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Connectry Architect need an API key?

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

Is Connectry Architect maintained?

The last commit was 230 days ago (2026-03-19). The latest release is v0.1.13.

How does Connectry Architect compare with other MCP servers?

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