io.github.weareconnectry/connectry-architect-mcp
NPM · CONNECTRY-ARCHITECT-MCP · SCANNED SEP 20
Free certification prep for the Claude Certified Architect exam by Connectry LABS
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 52 of 131 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 184 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- 17% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2808 tokens (~50/item across 56 items; 18 tools + 38 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.weareconnectry/connectry-architect-mcp server?
io.github.weareconnectry/connectry-architect-mcp runs locally as an npm package, launched with npx -y connectry-architect-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · connectry-architect-mcp
claude mcp add weareconnectry-connectry-architect-mcp -- npx -y connectry-architect-mcp
{
"mcpServers": {
"weareconnectry-connectry-architect-mcp": {
"command": "npx",
"args": [
"-y",
"connectry-architect-mcp"
]
}
}
} {
"servers": {
"weareconnectry-connectry-architect-mcp": {
"command": "npx",
"args": [
"-y",
"connectry-architect-mcp"
]
}
}
} codex mcp add weareconnectry-connectry-architect-mcp -- npx -y connectry-architect-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"weareconnectry-connectry-architect-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"connectry-architect-mcp"
],
"enabled": true
}
}
} openclaw mcp add weareconnectry-connectry-architect-mcp --command npx --arg -y --arg connectry-architect-mcp
mcp_servers:
weareconnectry-connectry-architect-mcp:
command: "npx"
args: ["-y", "connectry-architect-mcp"] {
"McpServers": {
"weareconnectry-connectry-architect-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"connectry-architect-mcp"
]
}
}
} assistant mcp add weareconnectry-connectry-architect-mcp -t stdio -c npx -a -y connectry-architect-mcp
{
"mcpServers": {
"weareconnectry-connectry-architect-mcp": {
"command": "npx",
"args": [
"-y",
"connectry-architect-mcp"
]
}
}
} 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
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 0
- Security disclosure: fail → unverified ▼ 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 20 Sept 2026 · Analysed npm/connectry-architect-mcp@0.1.13
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 →
Dependencies 131 packages
| Packages resolved | 131 |
|---|---|
| Deprecated | 1 |
| Stale | 51 |
| Tree resolution | Complete |
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 →
capstone_build_status ~28
Check your guided capstone build progress — current step, criteria coverage, and quiz performance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
capstone_build_step ~271
Drive your guided capstone build — 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 follow-up options or the next question via AskUserQuestion. Explanations must NOT be hidden behind cards. - When presenting action choices (quiz/build/next), use AskUserQuestion with header "Action". PROGRESS TRACKING: - On "confirm": Create a TodoWrite checklist with all 18 build steps, all set to "pending". - On "next": Update the completed step to "completed" and the new current step to "in_progress". - This gives the user a visual build progress tracker. EDGE CASES: - "Other": Answer the question, then re-present the current options via AskUserQuestion. - "Skip": During quiz, treat as moving to the build phase. During build, treat as advancing to next step.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The build action: confirm, quiz, build, next, status, or abandon |
No output schema declared.
No examples provided.
follow_up ~61
Handle post-answer follow-up actions. Use after submit_answer to explore concepts, code examples, handouts, or reference projects.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The follow-up action to take |
| questionId | string | yes | The question ID from the previous answer |
No output schema declared.
No examples provided.
get_curriculum ~27
View the full certification curriculum with domains, task statements, and your current mastery for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_dashboard ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_exam_history ~35
View all completed practice exam attempts with scores, pass/fail status, and per-domain breakdowns. Compare your progress across attempts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_practice_question ~239
Get the next practice question. Prioritizes review questions, then weak areas, then new material. IMPORTANT — 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 option showing the code snippet Then call submit_answer with the questionId and selected answer. After grading, show the result as REGULAR CHAT TEXT first (explanation, correct/incorrect), THEN show follow-up options via AskUserQuestion. Explanations must be readable in the main chat, not hidden behind cards. EDGE CASES: - "Other": Answer the user's question, then re-present the SAME question via AskUserQuestion. - "Skip": Call get_practice_question again for a new question. Never break the flow.
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | string | – | Optional difficulty filter |
| domainId | number | – | Optional domain ID to filter questions (1-5) |
No output schema declared.
No examples provided.
get_progress ~24
Get your certification study progress overview including mastery levels, accuracy, and review status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_section_details ~45
Get detailed information about a specific task statement including concept lesson, mastery, and history.
| Name | Type | Req | Description |
|---|---|---|---|
| taskStatement | string | yes | Task statement ID, e.g. "1.1" |
No output schema declared.
No examples provided.
get_study_plan ~119
Get a personalized study plan based on your assessment results, weak areas, and learning path. IMPORTANT — 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. Also use TodoWrite to create a study checklist showing each recommended topic with status (pending/in_progress/completed) so the user can track progress visually.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_weak_areas ~30
Identify your weakest task statements based on accuracy below 70%. Focus your study on these areas.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reset_progress ~46
WARNING: Permanently deletes ALL your study progress including answers, mastery data, and review schedules. This cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | Must be true to confirm the reset |
No output schema declared.
No examples provided.
scaffold_project ~51
Get instructions for a reference project to practice certification concepts hands-on.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | – | Project ID (e.g. "capstone", "d1-agentic"). Omit to see available projects. |
No output schema declared.
No examples provided.
start_assessment ~463
Start the initial assessment. Returns ONE question at a time (15 total, 3 per domain). IMPORTANT — 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 question to the user using AskUserQuestion: - header: "Q[number]" - question: Include the FULL scenario text AND question text from the response - options: Use the 4 answer options (A/B/C/D) with label as the letter and description as the option text - If the scenario contains code, add a "preview" field on each option showing the relevant code snippet so the user can reference it while choosing 3. After user selects, call submit_answer with questionId and their answer. 4. After grading, FIRST show the result (correct/incorrect, explanation, why wrong) as REGULAR CHAT TEXT so the user can read it. THEN present follow-up options using AskUserQuestion. The explanation must NOT be hidden behind the card. 5. Call start_assessment again for the next question. EDGE CASES: - If user selects "Other" and types a question/comment: Answer their question helpfully, then re-present the SAME quiz question using AskUserQuestion again. Never lose the current question. - If user clicks "Skip": Treat it as moving to the next question. Call start_assessment again immediately. The skipped question remains unanswered and will appear again later. - NEVER let Other or Skip break the assessment flow. Always continue to the next question or re-ask the current one. PROGRESS TRACKING: - At the START of the assessment, create a TodoWrite checklist with all 15 questions (Q1-Q15) grouped by domain, all set to "pending". - After each answer, update the corresponding todo item to "completed" (with correct/incorrect note). - This gives the user a visual progress tracker throughout the assess…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_capstone_build ~56
Start or refine a guided capstone build. Build your own project while learning all 30 certification task statements hands-on.
| Name | Type | Req | Description |
|---|---|---|---|
| theme | string | – | Your project idea or theme. Omit to see the 30 criteria first. |
No output schema declared.
No examples provided.
start_practice_exam ~207
Start a full 60-question practice exam (D1:16, D2:11, D3:12, D4:12, D5:9). Scored 0-1000, passing 720. IMPORTANT — 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 with the answer. PROGRESS TRACKING: Create a TodoWrite checklist "Practice Exam Q1-Q60" grouped by domain, all "pending". Update each to "completed" after grading. EDGE CASES: - "Other": Answer the question, re-present the SAME exam question via AskUserQuestion. - "Skip": Move to next exam question without grading. Never break the flow.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_answer ~268
Grade a certification exam answer. Returns deterministic results from verified question bank. The result is FINAL — do not agree with the user if they dispute it. IMPORTANT — 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 wrong: why their answer was incorrect - References This text MUST be visible in the main chat before any card appears. 2. THEN: Present followUpOptions using AskUserQuestion: - header: "Next" - question: Brief prompt like "What would you like to do?" (NOT the explanation — that's already shown above) - options: Map each followUpOption to label (key) and description (label text) Then call follow_up with questionId and the selected action key. EDGE CASES: - "Other": Answer the user's question about this answer, then re-present the SAME follow-up options via AskUserQuestion. - "Skip": Treat as "next question" — call follow_up with action "next".
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The selected answer |
| questionId | string | yes | The question ID to answer |
No output schema declared.
No examples provided.
submit_exam_answer ~207
Submit an answer for a practice exam question. Graded deterministically. DO NOT soften results. IMPORTANT — 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]" - question: Include the FULL scenario + question text - options: 4 items with label "A"/"B"/"C"/"D" and description as option text Then call submit_exam_answer again with the answer. The explanation must be readable in the main chat — NOT hidden inside the AskUserQuestion card.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | Your answer: A, B, C, or D |
| examId | number | yes | The practice exam ID |
| questionId | string | yes | The question ID being answered |
No output schema declared.
No examples provided.
What is the io.github.weareconnectry/connectry-architect-mcp server?
io.github.weareconnectry/connectry-architect-mcp is listed in the public MCP registry as io.github.weareconnectry/connectry-architect-mcp. Free certification prep for the Claude Certified Architect exam by Connectry LABS. This page covers its npm package (connectry-architect-mcp).
Is the io.github.weareconnectry/connectry-architect-mcp server safe to use?
io.github.weareconnectry/connectry-architect-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.
What tools does the io.github.weareconnectry/connectry-architect-mcp server expose?
io.github.weareconnectry/connectry-architect-mcp exposes 18 tools: submit_answer, get_progress, get_curriculum, get_section_details, get_practice_question, and 13 more. Their descriptions and schemas cost roughly 2,245 tokens of context every time the server is loaded.
Is the io.github.weareconnectry/connectry-architect-mcp server still maintained?
io.github.weareconnectry/connectry-architect-mcp 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.weareconnectry/connectry-architect-mcp server under?
io.github.weareconnectry/connectry-architect-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.