io.github.hoklims/stacksfinder
NPM · @STACKSFINDER/MCP-SERVER · SCANNED AUG 3
Deterministic tech stack recommendations, audits, and project estimates. No hallucinations.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 185 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2561 tokens (~111/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @stacksfinder/mcp-server
claude mcp add hoklims-stacksfinder -- npx -y @stacksfinder/mcp-server
codex mcp add hoklims-stacksfinder -- npx -y @stacksfinder/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hoklims-stacksfinder": {
"type": "local",
"command": [
"npx",
"-y",
"@stacksfinder/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add hoklims-stacksfinder --command npx --arg -y --arg @stacksfinder/mcp-server
mcp_servers:
hoklims-stacksfinder:
command: "npx"
args: ["-y", "@stacksfinder/mcp-server"] {
"mcpServers": {
"hoklims-stacksfinder": {
"command": "npx",
"args": [
"-y",
"@stacksfinder/mcp-server"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- 30 Jul 26 +21
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@stacksfinder/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_repo_mcps Analyze Repository MCPs ~191
Analyze your current repository to detect the tech stack and recommend relevant MCP servers. This tool examines your project files (package.json, .env, config files, etc.) to: 1. Detect frontend, backend, database, auth, hosting, and payment technologies 2. Find already installed MCP servers 3. Recommend new MCPs that would enhance your development workflow 4. Generate ready-to-use install configurations for Cursor, Claude Desktop, and Windsurf Example use cases: - "What MCPs would help with my project?" - "Analyze my repo and suggest useful MCP servers" - "Which MCPs am I missing based on my tech stack?"
| Name | Type | Req | Description |
|---|---|---|---|
| includeInstalled | boolean | — | Include already installed MCPs (default: false) |
| mcpConfigPath | string | — | Override path to MCP configuration file |
| workspaceRoot | string | — | Override workspace root directory (default: current directory) |
No output schema declared.
No examples provided.
analyze_tech Analyze Technology ~50
Detailed analysis of a technology with 6-dimension scores, strengths, weaknesses, and compatible technologies.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Context for scoring |
| technology | string | yes | Technology ID to analyze |
No output schema declared.
No examples provided.
check_mcp_compatibility Check MCP Compatibility ~270
Check compatibility between MCP servers. Detects conflicts (e.g., two database providers), redundancies (e.g., two ORMs), and synergies (e.g., GitHub + Vercel). Returns a health score (0-100) with grade (A/B/C/D) and detailed breakdown. **Examples:** - Check database compatibility: `["supabase-mcp", "neon-mcp"]` → conflict detected - Check ORM redundancy: `["prisma-mcp", "drizzle-mcp"]` → redundancy warning - Check synergies: `["stripe-mcp", "resend-mcp"]` → synergy detected **Supported MCP IDs include:** - supabase-mcp - neon-mcp - planetscale-mcp - turso-mcp - prisma-mcp - drizzle-mcp - clerk-mcp - auth0-mcp - stripe-mcp - paddle-mcp ...and more. **Aliases supported:** - "supabase" → "supabase-mcp" - "@neondatabase/mcp" → "neon-mcp" - "stripe" → "stripe-mcp"
| Name | Type | Req | Description |
|---|---|---|---|
| mcps | array | yes | Array of MCP server IDs to check compatibility between |
No output schema declared.
No examples provided.
compare_audits Compare Audit Reports ~74
Compare two audit reports to track technical debt trends over time. Shows new issues introduced, issues resolved, and health score change. Useful for measuring progress on debt reduction.
| Name | Type | Req | Description |
|---|---|---|---|
| baseAuditId | string | yes | Base (older) audit ID |
| compareAuditId | string | yes | Compare (newer) audit ID |
No output schema declared.
No examples provided.
compare_techs Compare Technologies ~49
Side-by-side comparison of 2-4 technologies with per-dimension winners and compatibility matrix.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Context for scoring |
| technologies | array | yes | Technologies to compare |
No output schema declared.
No examples provided.
create_audit Create Technical Debt Audit ~88
Create a technical debt audit for a list of technologies. Analyzes your stack for deprecated packages, security vulnerabilities, EOL versions, and upgrade recommendations. Returns findings with severity (critical/high/medium/low/info) and actionable suggestions. Requires API key with audit:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the audit report |
| technologies | array | yes | Technologies to audit |
No output schema declared.
No examples provided.
create_blueprint Create Blueprint ~207
Creates a new tech stack blueprint for a project. Requires API key with 'blueprint:write' scope. The blueprint generation is asynchronous. By default, this tool waits for completion and returns the full blueprint. Set waitForCompletion=false to get the job ID immediately for manual polling. Example usage: - Create a SaaS MVP: projectType="saas", scale="mvp", priorities=["time-to-market", "cost-efficiency"] - Create an enterprise API: projectType="api", scale="enterprise", priorities=["security", "scalability"]
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | — | Technology constraint IDs (optional) |
| priorities | array | — | Top 3 priorities (optional) |
| projectDescription | string | — | Brief description (optional) |
| projectName | string | — | Project name (optional) |
| projectType | string | yes | Type of project |
| scale | string | yes | Project scale |
| waitForCompletion | boolean | — | Wait for completion (default: true) |
No output schema declared.
No examples provided.
estimate_project Estimate Project ~217
Estimate scope, pricing, and analyze market for a software project. Provides: - Detailed hour breakdown by feature (with complexity assessment) - Price ranges by team seniority level (junior/mid/senior/expert) - Competitor analysis and market trends (real-time via Perplexity) [Pro tier] - Market size and gaps identification [Pro tier] - Risk identification with mitigation suggestions Perfect for freelancers and agencies creating quotes. Requires API key with estimate:write scope. **Pricing is 100% deterministic** - same inputs always produce same outputs. Market analysis is best-effort and may vary with web data changes.
| Name | Type | Req | Description |
|---|---|---|---|
| includeMarket | boolean | — | Include market analysis (default: true, Pro tier only) |
| region | string | — | Region for pricing (default: france) |
| seniorityLevel | string | — | Average team seniority (default: mid) |
| specs | string | yes | Project specifications (min 100 chars, max 10,000) |
| teamSize | number | — | Number of developers |
No output schema declared.
No examples provided.
execute_mcp_installation Execute MCP Installation ~302
Read a .env-mcp configuration file and generate installation commands for the MCPs. This tool: 1. Reads the .env-mcp file generated by prepare_mcp_installation 2. Validates that required environment variables are present 3. Generates installation commands for the target IDE/client 4. Returns post-installation instructions Prerequisites: - Run prepare_mcp_installation first to generate .env-mcp - Fill in the required API keys and credentials in .env-mcp - Set INSTALL_xxx=false for MCPs you want to skip Supported targets: - claude-code: Generates 'claude mcp add-json' commands - claude-desktop: Generates JSON config for claude_desktop_config.json - cursor: Generates JSON config for Cursor MCP settings - vscode: Generates JSON config for VS Code MCP extension - windsurf: Generates JSON config for Windsurf Output: - Individual commands/configs for each ready MCP - Aggregate command (for Claude Code) or config (for others) - List of MCPs missing required credentials - Post-installation instructions
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | — | Only generate commands without marking ready to execute (default: false) |
| envMcpPath | string | — | Path to .env-mcp file (default: .env-mcp in current directory) |
| targetClient | string | — | Target IDE/client for installation (default: claude-code) |
No output schema declared.
No examples provided.
generate_mcp_kit Generate MCP Kit ~218
Generate a complete project kit with optimal tech stack and MCP recommendations based on your project description. Describe your project and get: 1. **Optimal Tech Stack**: Best technologies for each category (frontend, backend, database, auth, hosting, payments) 2. **MCP Recommendations**: AI-assistant tools tailored to your chosen technologies 3. **Install Configurations**: Ready-to-use configs for Claude Desktop, Cursor, and Windsurf Example prompts: - "I'm building a SaaS for project management with real-time collaboration" - "Building an MVP for a marketplace connecting freelancers with clients" - "Creating an e-commerce platform with Stripe payments and PostgreSQL"
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | — | Tech constraints (e.g., must-use-postgresql) |
| priorities | array | — | Top priorities (max 3) |
| projectDescription | string | yes | Describe your project (50-5000 chars) |
| projectType | string | — | Project type (if known) |
| scale | string | — | Project scale (if known) |
No output schema declared.
No examples provided.
get_audit Get Audit Report ~35
Fetch a completed audit report by ID. Returns all findings and health score.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | Audit report UUID |
No output schema declared.
No examples provided.
get_audit_quota Get Audit Quota ~20
Check your remaining audit quota for this month.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_blueprint Get Blueprint ~43
Fetches an existing blueprint by ID. Blueprints are generated via the StacksFinder web UI. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprintId | string | yes | Blueprint UUID |
No output schema declared.
No examples provided.
get_estimate_quota Get Estimate Quota ~22
Check your remaining estimate quota for this week and month.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_migration_recommendation Get Migration Recommendation ~88
Analyze an audit report for migration opportunities. Returns a detailed migration recommendation including: - Technologies that should be replaced - Recommended modern alternatives - Migration roadmap with phases - Risk assessment - Builder constraints to pre-fill for generating a migration blueprint Use this after create_audit to get actionable migration guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | Audit report UUID to analyze for migration |
No output schema declared.
No examples provided.
list_api_keys List API Keys ~23
Lists your StacksFinder API keys. Requires a configured API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_audits List Audit Reports ~47
List your audit reports with pagination. Shows name, status, health score, and creation date.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results |
| offset | number | — | Pagination offset |
No output schema declared.
No examples provided.
list_technologies List Technologies ~38
Lists all available technology IDs for use with other tools. Essential for discovering valid technology identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Filter by category |
No output schema declared.
No examples provided.
prepare_mcp_installation Prepare MCP Installation ~303
Analyze your repository and generate a .env-mcp configuration file for MCP server installation. This tool: 1. Detects your tech stack from project files (package.json, .env, etc.) 2. Identifies which MCP servers would benefit your project 3. Finds already installed MCPs to avoid duplicates 4. Generates a .env-mcp template file with all required environment variables The generated .env-mcp file contains: - INSTALL_xxx flags to control which MCPs to install - Required and optional environment variables for each MCP - Documentation links and examples After running this tool: 1. Open the generated .env-mcp file 2. Fill in the API keys and configuration values 3. Set INSTALL_xxx=false for MCPs you don't want 4. Run execute_mcp_installation to complete the setup Example use cases: - "Prepare MCP installation for my project" - "Generate .env-mcp for my tech stack" - "What MCPs do I need and what credentials do they require?"
| Name | Type | Req | Description |
|---|---|---|---|
| envMcpPath | string | — | Path where .env-mcp will be created (default: .env-mcp in workspaceRoot) |
| includeInstalled | boolean | — | Include already installed MCPs in the preparation (default: false) |
| mcpConfigPath | string | — | Override path to existing MCP configuration file |
| workspaceRoot | string | — | Workspace root directory (default: current directory) |
No output schema declared.
No examples provided.
recommend_stack Recommend Stack ~72
Recommends the best tech stack for a project using real-time scoring with context adjustments. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | — | Project constraints |
| priorities | array | — | Top priorities (max 3) |
| projectType | string | yes | Type of project |
| scale | string | — | Project scale |
No output schema declared.
No examples provided.
recommend_stack_demo Recommend Stack (Demo) ~86
Try StacksFinder's tech stack recommendations for FREE - once per day, no account required. Returns the optimal technology for each category based on deterministic scoring. For unlimited access, priorities, constraints, and AI-generated narratives, upgrade to Pro at https://stacksfinder.com/pricing
| Name | Type | Req | Description |
|---|---|---|---|
| projectType | string | yes | Type of project |
| scale | string | — | Project scale |
No output schema declared.
No examples provided.
revoke_api_key Revoke API Key ~37
Revokes an API key. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | string | yes | The UUID of the API key to revoke |
No output schema declared.
No examples provided.
setup_api_key Setup API Key ~81
Authenticates with your StacksFinder account and creates an API key. Requires Pro or Team tier. The key is returned once and should be saved securely.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Your StacksFinder account email | |
| keyName | string | — | Optional name for the API key |
| password | string | yes | Your StacksFinder account password |
No output schema declared.
No examples provided.