Artifyde MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Artifyde publishing and reviewing HTML artifacts: Do permanent hosted artifacts and pulled copies retain explicit sharing and account boundaries?

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

Best fit

Store, publish, pull and review agents’ HTML artifacts.

What we know

A home for your agent's HTML artifacts - publish, pull, share and review them over MCP. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

artifyde-mcp 0.1.2 published 2026-07-11T04:50:31.298Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Writes: Publish/share artifacts (per source description).
Authentication not yet verified.
Sensitive access: Generated HTML content, Share links

Potential high-impact side effects: Publish/share artifacts (per source description).

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

All limitations / Review context

Do permanent hosted artifacts and pulled copies retain explicit sharing and account boundaries?

The bounded review of the publisher's documented Artifyde publishing and reviewing HTML artifacts and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Publish/share artifacts (per source description).
Reviewed write actions: Publish/share artifacts (per source description)
Sensitive access: Generated HTML content, Share links
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
Public sharing defaults, auth and deletion/update scope are unverified

Original activity observations

artifyde-mcp 0.1.2 published 2026-07-11T04:50:31.298Z

Technical identity

npm/artifyde-mcp

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

Evidence & Sources

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

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
artifyde-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Repository document ↗
kennethkoontz/artifyde-mcp
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Per-user token via artifyde CLI login; separate admin API key is higher privilege
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Per-user token via artifyde CLI login; separate admin API key is higher privilege | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions · Review before use
```
claude mcp add artifyde --scope user -e ARTIFYDE_TOKEN=<TOKEN> -- npx -y artifyde-mcp
```
Configure / authenticate
MCP100 setup guide
ARTIFYDE_TOKEN from `artifyde login` preferred; ARTIFYDE_API_KEY is alternate admin key. Claude Desktop .mcpb option.
Required environment variables: ARTIFYDE_TOKEN
Check connection
Suggested check
Verify connected tools; avoid publishing content as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `artifyde`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove artifyde

Official Documentation & Sources

What it does

A home for your agent's HTML artifacts - publish, pull, share and review them over MCP. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Store, publish, pull and review agents’ HTML artifacts.

Representative uses

Publish generated HTML artifacts
Retrieve and review saved artifacts
Share public artifact links

Limitations

Public sharing defaults, auth and deletion/update scope are unverified

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Not documented in the reviewed sources
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Publish/share artifacts (per source description).

Access scope and cautions

Write actions: Publish/share artifacts (per source description)
Sensitive access: Generated HTML content Share links
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Publish generated HTML artifacts; Retrieve and review saved artifacts; Share public artifact links.

Can it modify data or perform write operations?

Documented write actions include: Publish/share artifacts (per source description).

What data-handling boundary should I consider?

Recorded sensitive-access context: Generated HTML content; Share links.

What limitations and risks should I check before use?

Potential high-impact side effects: Publish/share artifacts (per source description). Public sharing defaults, auth and deletion/update scope are unverified. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.