io.github.taimiralain/stackguide-mcp
NPM · @STACKGUIDE/MCP-SERVER
Dynamic context loading for AI assistants with TDD workflow and AST analysis
Available components
Last scanned (21 hours ago)
Scores higher than 66% of npm servers
Category Developer Tools
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 53 of 139 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 (GPL-3.0).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2248 tokens (~51/item across 44 items; 16 tools + 28 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- CVE-2026-118764 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/@stackguide/mcp-server@4.2.0
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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 139 packages
| Packages resolved | 139 |
|---|---|
| Deprecated | 1 |
| Stale | 52 |
| 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 →
agent ~450
Active agent workflow actions: intake/plan/verify/release plus Jira ticket creation from strict MAIN DESCRIPTION templates.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | Acceptance criteria list for strict Jira template |
| action | string | – | Active workflow action |
| brief | string | – | Structured or plain brief text for planning |
| createFromDescription | boolean | – | When action is intake, create Jira ticket first from MAIN DESCRIPTION template |
| createPullRequest | boolean | – | If true, release action opens PR/MR when provider is configured |
| createTag | boolean | – | If true, release action creates annotated git tag when CI is green |
| dataTransformation | string | – | DATA TRANSFORMATION section content |
| destinationController | string | – | DESTINATION section value: Controller |
| destinationModel | string | – | DESTINATION section value: Model |
| destinationRoute | string | – | DESTINATION section value: Route |
| destinationView | string | – | DESTINATION section value: View |
| issueType | string | – | Optional Jira issue type override (Task/Story/Bug) |
| labels | array | – | Optional labels to set when creating Jira tickets |
| mainDescription | string | – | MAIN DESCRIPTION body used to create Jira tickets |
| originComponent | string | – | ORIGIN section value: Component |
| originKeyLogic | string | – | ORIGIN section value: Key Logic |
| originOldQuery | string | – | ORIGIN section value: Old Query |
| path | string | – | Project path (default: current directory) |
| projectKey | string | – | Optional Jira project key override |
| prototypeDesignPattern | string | – | PROTOTYPES section value: Design Pattern |
| prototypeProps | string | – | PROTOTYPES section value: Props |
| prototypeRelatedFiles | array | – | PROTOTYPES related files list |
| prototypeView | string | – | PROTOTYPES section value: View |
| summary | string | – | Optional Jira summary (defaults to first line of MAIN DESCRIPTION) |
| ticket | string | – | Ticket key for intake/plan actions (e.g. PROJ-123) |
| version | string | – | Target release version for release action (e.g. v1.2.0) |
No output schema declared.
No examples provided.
analyze ~108
Project Intelligence: Comprehensive analysis of project structure, configuration, and dependencies. Provides smart recommendations, generates optimal configs, and suggests improvements based on framework best practices.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Type of analysis to perform |
| autoFix | boolean | – | Automatically apply safe fixes (default: false) |
| configType | string | – | Config type to generate (for action:"generate") |
| format | string | – | Output format |
| path | string | – | Project path to analyze (default: current directory) |
No output schema declared.
No examples provided.
config ~72
Manage saved configurations: save, load, list, delete, export, or import.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| id | string | – | Configuration ID (for load/delete/export) |
| json | string | – | JSON string (for import) |
| name | string | – | Configuration name (for save) |
No output schema declared.
No examples provided.
context ~47
Get current context with all loaded rules and knowledge. Use this to see what StackGuide has configured.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | Include full rule/knowledge content (default: false, shows summary) |
No output schema declared.
No examples provided.
cursor ~53
Browse, search, and import rules from cursor.directory community.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| query | string | – | Category to browse or search term |
| slug | string | – | Rule slug for import |
No output schema declared.
No examples provided.
custom_rule ~86
Create, update, delete, or list custom rules for your project.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| category | string | – | Rule category |
| content | string | – | Rule content in markdown |
| id | string | – | Rule ID (for update/delete) |
| json | string | – | JSON string (for import) |
| name | string | – | Rule name |
No output schema declared.
No examples provided.
docs ~67
Fetch and manage web documentation. Fetch URLs, search cached docs, or list available.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| query | string | – | Search query |
| url | string | – | URL to fetch or document ID |
| urls | array | – | Multiple URLs to fetch |
No output schema declared.
No examples provided.
generate ~81
Generate boilerplate code from templates. Create components, hooks, services, tests, API routes, models, and utilities with best practices built in.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the generated code (e.g., UserCard, useAuth, ApiService) |
| options | object | – | Generation options |
| type | string | yes | Type of code to generate |
No output schema declared.
No examples provided.
health ~76
Get a comprehensive health score for your project. Analyzes configuration, code quality, structure, documentation, and testing readiness. Returns a grade (A-F) with detailed recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | boolean | – | Include detailed breakdown by category (default: true) |
| projectPath | string | – | Project path to analyze (default: current project) |
No output schema declared.
No examples provided.
help ~28
Get help about StackGuide tools and how to use them.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Help topic |
No output schema declared.
No examples provided.
init ~207
Initialize a project with the StackGuide TDD workflow. Auto-detects your stack and scaffolds a .stackguide/ directory with only the relevant agents, skills, hooks and scripts (including the optional OJ health gate).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| applyMcpTemplates | boolean | – | If true, writes MCP integration templates into selected manifests |
| integrations | array | – | External MCP integrations to scaffold in local manifests |
| jiraIssueType | string | – | Default Jira issue type (Task by default) |
| jiraProjectKey | string | – | Default Jira project key for ticket creation |
| mcpSyncTargets | array | – | Target manifest files for MCP synchronization |
| model | string | – | Preferred model identifier saved for adaptive TDD |
| path | string | – | Project path (default: current directory) |
| tokenMode | string | – | Token profile for adaptive TDD |
| type | string | – | Force a project type instead of auto-detecting |
No output schema declared.
No examples provided.
knowledge ~54
Manage knowledge base: list, search, or get architecture patterns and solutions.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| category | string | – | Filter by category |
| query | string | – | Search term or knowledge ID |
No output schema declared.
No examples provided.
review ~100
Analyze code for issues using pattern matching. Detects security vulnerabilities, performance problems, coding standard violations, and architecture issues. Returns a score (0-100) and detailed report with suggestions. Works on files, URLs, or entire projects.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | File path to review |
| focus | string | – | Focus area for review |
| project | boolean | – | Review entire project structure |
| url | string | – | URL to fetch and review |
No output schema declared.
No examples provided.
rules ~75
Manage rules: list, search, get, or select rules for your project.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| category | string | – | Filter by category |
| ids | array | – | Rule IDs to select (for select action) |
| query | string | – | Search term or rule ID (for search/get actions) |
No output schema declared.
No examples provided.
setup ~189
Configure StackGuide for your project. Auto-detects project type or lets you specify one manually.
| Name | Type | Req | Description |
|---|---|---|---|
| enableAdaptiveTdd | boolean | – | Enable the adaptive TDD setup wizard that asks for model and integration preferences |
| integrations | array | – | External MCP integrations to scaffold as templates |
| jiraIssueType | string | – | Default Jira issue type (Task, Story, Bug...) |
| jiraProjectKey | string | – | Default Jira project key used when creating tickets from descriptions |
| mcpSyncTargets | array | – | Where MCP template servers should be synchronized |
| model | string | – | Preferred model identifier for TDD runs (saved in .stackguide/config.json) |
| path | string | – | Project path (default: current directory) |
| tokenMode | string | – | Token profile for prompts and workflow responses |
| type | string | – | Project type to use (auto-detected if not specified) |
No output schema declared.
No examples provided.
workflow ~110
TDD agentic workflow with lazy loading. Load agents, skills, hooks, commands, scripts and the OJ policy on demand to save tokens. Five roles: Intake → Planner → Implementer → Verifier → Releaser.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform |
| category | string | – | Filter list by category |
| name | string | – | Name of the item to load (e.g. "tdd-planner", "tdd-core", "verify", "oj-verify") |
No output schema declared.
No examples provided.
How do I install the io.github.taimiralain/stackguide-mcp server?
io.github.taimiralain/stackguide-mcp runs locally as an npm package, launched with npx -y @stackguide/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 · @stackguide/mcp-server
claude mcp add taimiralain-stackguide-mcp -- npx -y @stackguide/mcp-server
What is the io.github.taimiralain/stackguide-mcp server?
io.github.taimiralain/stackguide-mcp is listed in the public MCP registry as io.github.taimiralain/stackguide-mcp. Dynamic context loading for AI assistants with TDD workflow and AST analysis. This page covers its npm package (@stackguide/mcp-server).
Is the io.github.taimiralain/stackguide-mcp server safe to use?
io.github.taimiralain/stackguide-mcp scores 80 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 4 November 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.taimiralain/stackguide-mcp server expose?
io.github.taimiralain/stackguide-mcp exposes 16 tools: setup, context, rules, knowledge, review, and 11 more. Their descriptions and schemas cost roughly 1,803 tokens of context every time the server is loaded.
Is the io.github.taimiralain/stackguide-mcp server still maintained?
io.github.taimiralain/stackguide-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 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.taimiralain/stackguide-mcp server under?
io.github.taimiralain/stackguide-mcp declares the GPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.