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.jigarkkarangiya/adobe-commerce-docs-mcp

NPM · ADOBE-COMMERCE-DOCS-MCP

MCP server for Adobe Commerce / Magento 2 documentation — search, browse, and read official docs.

0 this week 83 Trust /100

Last scanned (16 hours ago)

Scores higher than 76% of npm servers

Category Code Search and Documentation

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 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
  • 30 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
  • 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
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 54 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 487 tokens (~54/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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 24 Oct 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.93 functional
  • 22 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
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 5 Nov 2026 · Analysed npm/adobe-commerce-docs-mcp@2.0.3

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 100 packages
Packages resolved 100
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~487 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
get_code_examples ~47

Extract only code examples from a documentation page. Returns fenced code blocks without prose — much more token-efficient than full page fetch.

NameTypeReqDescription
urlstringyesFull URL of the documentation page
NameTypeReqDescription
countnumberyes–
examplesarrayyes–
urlstringyes–

No examples provided.

get_doc_content ~36

Fetch the full content of an Adobe Commerce documentation page as clean markdown.

NameTypeReqDescription
urlstringyesFull URL of the documentation page
NameTypeReqDescription
contentstringyes–
urlstringyes–

No examples provided.

get_page_toc ~51

Get the table of contents (heading hierarchy) of a documentation page. Useful for understanding structure before fetching the full (expensive) content.

NameTypeReqDescription
urlstringyesFull URL of the documentation page
NameTypeReqDescription
tocarrayyes–
urlstringyes–

No examples provided.

get_related_docs ~56

Find sibling/related documentation pages for a given page URL (same parent in the doc tree).

NameTypeReqDescription
limitnumber–Max related pages (default: 10)
urlstringyesFull URL of the documentation page
NameTypeReqDescription
countnumberyes–
relatedarrayyes–
urlstringyes–

No examples provided.

list_doc_sections ~19

List all Adobe Commerce documentation sections with page counts.

Input schema present but exposes no named parameters.

NameTypeReqDescription
sectionsarrayyes–
total_pagesnumberyes–

No examples provided.

lookup_error_code ~61

Look up an Adobe Commerce error code or message in the Knowledge Base. Auto-fetches the top result content for immediate answers.

NameTypeReqDescription
errorstringyesError code or message (e.g., 'MDVA-43395', 'Unable to serialize value')
NameTypeReqDescription
errorstringyes–
matched–yes–
othersarrayyes–

No examples provided.

multi_page_search ~85

Search documentation with multiple queries at once. Returns de-duplicated results from all queries — reduces round-trips when researching a topic from multiple angles.

NameTypeReqDescription
limit_per_querynumber–Max results per query (default: 5)
queriesarrayyesArray of search queries (1–5)
sectionstring–Optional section filter for all queries
NameTypeReqDescription
queriesarrayyes–
resultsarrayyes–
unique_countnumberyes–

No examples provided.

refresh_sitemap ~20

Force-refresh the cached sitemap data from Adobe Experience League.

Input schema present but exposes no named parameters.

NameTypeReqDescription
pages_indexednumberyes–

No examples provided.

search_adobe_commerce_docs ~112

Search Adobe Commerce / Magento documentation. Returns pages ranked by BM25 relevance with snippets. Supports synonym expansion (e.g. 'graphql' also matches 'gql') and fuzzy matching for typos.

NameTypeReqDescription
limitnumber–Max results (default: 15)
querystringyesSearch keywords (e.g., 'graphql product query', 'checkout configuration')
sectionstring–Filter by section slug (e.g., commerce-admin, commerce-cloud-service, commerce-on-cloud)
NameTypeReqDescription
countnumberyes–
querystringyes–
resultsarrayyes–

No examples provided.

Install

How do I install the io.github.jigarkkarangiya/adobe-commerce-docs-mcp server?

io.github.jigarkkarangiya/adobe-commerce-docs-mcp runs locally as an npm package, launched with npx -y adobe-commerce-docs-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 · adobe-commerce-docs-mcp

# add to Claude Code
claude mcp add jigarkkarangiya-adobe-commerce-docs-mcp -- npx -y adobe-commerce-docs-mcp
Common questions

What is the io.github.jigarkkarangiya/adobe-commerce-docs-mcp server?

io.github.jigarkkarangiya/adobe-commerce-docs-mcp is listed in the public MCP registry as io.github.jigarkkarangiya/adobe-commerce-docs-mcp. MCP server for Adobe Commerce / Magento 2 documentation, search, browse, and read official docs. This page covers its npm package (adobe-commerce-docs-mcp).

Is the io.github.jigarkkarangiya/adobe-commerce-docs-mcp server safe to use?

io.github.jigarkkarangiya/adobe-commerce-docs-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.jigarkkarangiya/adobe-commerce-docs-mcp server expose?

io.github.jigarkkarangiya/adobe-commerce-docs-mcp exposes 9 tools: search_adobe_commerce_docs, get_doc_content, list_doc_sections, refresh_sitemap, get_related_docs, and 4 more. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.

Is the io.github.jigarkkarangiya/adobe-commerce-docs-mcp server still maintained?

io.github.jigarkkarangiya/adobe-commerce-docs-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.jigarkkarangiya/adobe-commerce-docs-mcp server?

VerifyMCP ran 15 checks on io.github.jigarkkarangiya/adobe-commerce-docs-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.jigarkkarangiya/adobe-commerce-docs-mcp: License. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.