Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.IamNishant51/atlas-pipeline

NPM · ATLAS-PIPELINE-MCP

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

Available components

0 this week 0 Trust /100

Last scanned (18 hours ago)

Scores higher than 0% of npm servers

Category Developer Tools

Recent critical change

CVE-2026-102828 affects this package (11 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security73
Provenance & Transparency44
Schema Quality & AI Usability69
  • 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 Management67
  • Stability observed for 20 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 3 Nov 26 0
    • Stability: pass → 0.63 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.83 → pass security
  • 15 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → 0.80 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Oct 26 0
    • Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed npm/atlas-pipeline-mcp@1.0.2

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 15 findings
ID CVE Severity Vector Fix available
GHSA-v5rq-49vh-5v5c CVE-2026-102829 critical 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-4mh8-r7rc-xpvc CVE-2026-92081 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-667r-xxjv-c9mm CVE-2026-84504 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-9q9j-q6p8-xq58 CVE-2026-84428 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-hwr6-493r-vm6h CVE-2026-84469 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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-p68q-wchp-6fh7 CVE-2026-76169 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-w2qp-rph6-63g4 CVE-2026-18504 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N 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
GHSA-858h-whjf-mvg5 CVE-2026-102827 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-g4wm-2vf7-vfgr CVE-2026-102826 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-x6jw-m9v5-85vh CVE-2026-102828 critical 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 193 packages
Packages resolved 193
Deprecated 1
Stale 61
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. 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 →

Tool Tokens
atlas_context ~65

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

NameTypeReqDescription
filePathsarray–Specific files to analyze
projectPathstringyesPath to the project root
querystring–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.

NameTypeReqDescription
codestringyesThe code to review
focusarray–Areas to focus on: security, performance, readability, maintainability
languagestring–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.

NameTypeReqDescription
contextstring–Additional context about the codebase
maxDepthnumber–Maximum decomposition depth (default: 3)
taskstringyesThe 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.

NameTypeReqDescription
filePathstring–Specific file to get history for
maxCommitsnumber–Maximum commits to analyze (default: 50)
repoPathstringyesPath 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.

NameTypeReqDescription
conversationHistoryarray–Optional conversation history for context
messagestringyesThe 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.

NameTypeReqDescription
codestringyesThe code to optimize
critiquestring–Critique feedback to address
languagestring–Programming language
preserveApiboolean–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

NameTypeReqDescription
messagestringyesThe user request
optionsobject––
projectPathstringyesPath to the project

No output schema declared.

No examples provided.

atlas_providers ~18

Check available LLM providers and their status.

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.

NameTypeReqDescription
contextstring–Code context and constraints
languagestring–Programming language
numVariantsnumber–Number of variants to generate (default: 3)
taskstringyesThe coding task description

No output schema declared.

No examples provided.

Install

How do I install the io.github.IamNishant51/atlas-pipeline MCP server?

io.github.IamNishant51/atlas-pipeline runs locally as an npm package, launched with npx -y atlas-pipeline-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 · atlas-pipeline-mcp

# add to Claude Code
claude mcp add iamnishant51-atlas-pipeline -- npx -y atlas-pipeline-mcp
Common questions

What is the io.github.IamNishant51/atlas-pipeline MCP server?

io.github.IamNishant51/atlas-pipeline is an MCP server listed in the public MCP registry as io.github.IamNishant51/atlas-pipeline. 7-stage AI pipeline MCP server: Intent→Context→Git→Decompose→Variants→Critique→Optimize. This page covers its npm package (atlas-pipeline-mcp).

What tools does the io.github.IamNishant51/atlas-pipeline MCP server expose?

io.github.IamNishant51/atlas-pipeline exposes 9 tools: atlas_intent, atlas_context, atlas_git, atlas_decompose, atlas_variants, and 4 more. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

Is the io.github.IamNishant51/atlas-pipeline MCP server still maintained?

io.github.IamNishant51/atlas-pipeline 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.IamNishant51/atlas-pipeline MCP server under?

io.github.IamNishant51/atlas-pipeline declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.