ai.shippp/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Shippp design-system to UI code tools

What we know

Pull Shippp components and Chakra UI design artifacts into coding-agent workflows. Deterministic Chakra UI code from your Shippp design files, straight into your IDE agent.

Maintenance / activity evidence

364 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Repository synchronization can write local project files; inspect diffs before accepting. Reported action classes: Synchronize component code. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Repository synchronization can write local project files; inspect diffs before accepting.

Repository synchronization can write local project files; inspect diffs before accepting.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 364 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @shippp/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have @shippp/mcp permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Repository synchronization can write local project files; inspect diffs before accepting.

Repository synchronization can write local project files; inspect diffs before accepting.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Reviewed write actions: Synchronize component code
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

364 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/@shippp/mcp

Exact implementation source: https://www.npmjs.com/package/@shippp/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@shippp/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@shippp/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Uses Shippp API key; optional repository sync may change project files, keep distinct from MCP installation.
publisher documented step or launch · Publisher instructions
npx -y @shippp/mcp
Configure / authenticate
MCP100 setup guide
SHIPPP_API_KEY required by package. Publisher documents `npx @shippp/mcp plan --root .` and `sync` commands that may act on files: do not run sync as a connection test.
Environment variables referenced by this route (respect the alternatives above): SHIPPP_API_KEY
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Pull Shippp components and Chakra UI design artifacts into coding-agent workflows. Deterministic Chakra UI code from your Shippp design files, straight into your IDE agent.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Shippp design-system to UI code tools

Representative uses

Retrieve design tokens
Synchronize component code

Limitations

Repository synchronization can write local project files; inspect diffs before accepting.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Repository synchronization can write local project files; inspect diffs before accepting.
Data handling: Repository synchronization can write local project files; inspect diffs before accepting.
Cost: Not verified; check vendor terms
Risk and cautions: Repository synchronization can write local project files; inspect diffs before accepting.

Access scope and cautions

Write actions: Not verified Synchronize component code
Risk level: medium
Security notes: Repository synchronization can write local project files; inspect diffs before accepting. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Retrieve design tokens; Synchronize component code.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Synchronize component code. Recorded permission context: Repository synchronization can write local project files; inspect diffs before accepting.

What data-handling boundary should I consider?

Repository synchronization can write local project files; inspect diffs before accepting.

What limitations and risks should I check before use?

Repository synchronization can write local project files; inspect diffs before accepting. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.