io.github.BWB03/catalog-cli-pro

Name: io.github.BWB03/catalog-cli-pro
Rating: 60 (1 reviews)
Author: io.github.BWB03

MCPcommunity

v1.0.0io.github.BWB03UnknownUpdated 2mo agonpm GitHub

Amazon catalog auditing tool. 13 quality checks for your listings.

Agent-native Amazon catalog auditing tool The first AI-agent-friendly Amazon catalog analysis tool. Query your CLRs with structured input, integrate via MCP server, and automate catalog audits. Hosted API available at api.catalogcli.com — persistent storage, unlimited scans, and API access for $9.99/mo. Learn more Amazon title readiness - New check flags titles over 75 characters for Amazon's…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

2mo agoLast update

Package

Authorio.github.BWB03

LicenseUnknown

Version1.0.0

Sourcemcp-registry

npm@bwb03/catalog-cli-pro

GitHubBWB03/amazon-catalog-cli

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface—

Security scan✓ Cleanv1.0.0 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp