io.github.IamNishant51/atlas-pipeline

NPM · ATLAS-PIPELINE-MCP · SCANNED AUG 3

7-stage AI pipeline MCP server: Intent→Context→Git→Decompose→Variants→Critique→Optimize

Available components

+38 this week 62 62 Trust /100

Trust breakdown (6 categories)

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 Security70

No malware found by supply-chain analysis.Pass
CVE check failed: a known high-severity CVE affects fastify 4.29.1, a direct dependency. A fixed version is available. View diagnostics → Fail
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (195 of 196), 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 178 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability66

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 552 tokens (~61/item across 9 items; 9 tools + 0 resources), lean.Pass
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 Coverage99

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
96% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

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 · atlas-pipeline-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add iamnishant51-atlas-pipeline -- npx -y atlas-pipeline-mcp

# add to Codex CLI

codex mcp add iamnishant51-atlas-pipeline -- npx -y atlas-pipeline-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iamnishant51-atlas-pipeline": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "atlas-pipeline-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add iamnishant51-atlas-pipeline --command npx --arg -y --arg atlas-pipeline-mcp

# ~/.hermes/config.yaml

mcp_servers:
  iamnishant51-atlas-pipeline:
    command: "npx"
    args: ["-y", "atlas-pipeline-mcp"]

// mcp.json

{
  "mcpServers": {
    "iamnishant51-atlas-pipeline": {
      "command": "npx",
      "args": [
        "-y",
        "atlas-pipeline-mcp"
      ]
    }
  }
}

Changelog

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.

2 Aug 26 +41
- CVE-2026-3635 affects this package: high ▼ security
- CVE-2026-6321 affects this package: high ▼ security
- CVE-2026-25224 affects this package: high ▼ security
- CVE-2026-6322 affects this package: high ▼ security
- CVE-2026-47219 affects this package: high ▼ security
- CVE-2026-25223 affects this package: high ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 96 functional
- First check of Schema quality: pass functional
- First check of Schema quality: unverified functional
27 Jul 26 24

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 6 findings

ID	CVE	Severity	Vector	Fix available
GHSA-q3j6-qgpj-74h6	CVE-2026-6321	high	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N	yes
GHSA-v39h-62p7-jpjc	CVE-2026-6322	high	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N	yes
GHSA-444r-cwp2-x5xf	CVE-2026-3635	medium	CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N	yes
GHSA-jx2c-rxcm-jvmq	CVE-2026-25223	high	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N	yes
GHSA-mrq3-vjjr-p77c	CVE-2026-25224	low	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L	yes
GHSA-c96f-x56v-gq3h	CVE-2026-47219	high	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H	yes

Dependencies 195 packages

195 packages in the resolved dependency tree · 191 deprecated · 62 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 9 exposed · ~552 tokens

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.

Tool Tokens

atlas_context ~65

Gather context about a project or codebase. Analyzes files, dependencies, and project structure.

Input Output Examples

Name	Type	Req	Description
filePaths	array	—	Specific files to analyze
projectPath	string	yes	Path to the project root
query	string	—	What context to focus on

No output schema declared.

No examples provided.

atlas_critique ~69

Review and critique code for quality, security, and best practices. Returns detailed feedback and scores.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The code to review
focus	array	—	Areas to focus on: security, performance, readability, maintainability
language	string	—	Programming language

No output schema declared.

No examples provided.

atlas_decompose ~70

Break down a complex task into smaller subtasks with dependencies. Creates a DAG of work items.

Input Output Examples

Name	Type	Req	Description
context	string	—	Additional context about the codebase
maxDepth	number	—	Maximum decomposition depth (default: 3)
task	string	yes	The task description to decompose

No output schema declared.

No examples provided.

atlas_git ~72

Analyze Git history and repository state. Returns recent commits, active branches, and file change history.

Input Output Examples

Name	Type	Req	Description
filePath	string	—	Specific file to get history for
maxCommits	number	—	Maximum commits to analyze (default: 50)
repoPath	string	yes	Path to the Git repository

No output schema declared.

No examples provided.

atlas_intent ~55

Analyze user intent from a natural language request. Extracts action type, target, context, and constraints.

Input Output Examples

Name	Type	Req	Description
conversationHistory	array	—	Optional conversation history for context
message	string	yes	The user message to analyze

No output schema declared.

No examples provided.

atlas_optimize ~68

Optimize code based on critique feedback. Applies improvements while maintaining functionality.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The code to optimize
critique	string	—	Critique feedback to address
language	string	—	Programming language
preserveApi	boolean	—	Whether to preserve the public API

No output schema declared.

No examples provided.

atlas_pipeline ~60

Run the full Atlas pipeline: Intent → Context → Git → Decompose → Variants → Critique → Optimize

Input Output Examples

Name	Type	Req	Description
message	string	yes	The user request
options	object	—	—
projectPath	string	yes	Path to the project

No output schema declared.

No examples provided.

atlas_providers ~18

Check available LLM providers and their status.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

atlas_variants ~75

Generate multiple solution variants for a coding task. Returns different approaches with pros/cons.

Input Output Examples

Name	Type	Req	Description
context	string	—	Code context and constraints
language	string	—	Programming language
numVariants	number	—	Number of variants to generate (default: 3)
task	string	yes	The coding task description

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug