ChartForge MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to ChartForge chart and diagram generation: Do generated charts retain data input attribution and uncertainty rather than imply research verification?

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

Best fit

Generate charts/visualizations from structured data through ChartForge.

What we know

Radar identity is the `chartforge-mcp` package. It is clearly chart/visualization-oriented, but enough first-party documentation was not recovered in this pass to confirm exact rendering backends, auth, storage/publication and file-write semantics.

Maintenance / activity evidence

chartforge-mcp 0.1.4 published 2026-06-16T23:26:13.551Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Input datasets may be sensitive

Data used for charts may be confidential; storage boundary must be confirmed.

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

All limitations / Review context

Do generated charts retain data input attribution and uncertainty rather than imply research verification?

The bounded review of the publisher's documented ChartForge chart and diagram generation 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.

Data used for charts may be confidential; storage boundary must be confirmed.
Unknown.
Sensitive access: Input datasets may be sensitive
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.
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.
official docs/repository
auth
storage
export formats
write/publish actions
Exact supported chart types and export formats unresolved.
Whether generated assets are local or hosted is unresolved.
Authentication/storage/privacy are unresolved.

Original activity observations

chartforge-mcp 0.1.4 published 2026-06-16T23:26:13.551Z

Technical identity

npm/chartforge-mcp

Exact implementation source: https://www.npmjs.com/package/chartforge-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:chartforge-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 ↗
chartforge-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

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.
Official client config requires Chartforge key
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
Official client config requires Chartforge key | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y chartforge-mcp
Configure / authenticate
MCP100 setup guide
Publisher-documented connection/installation path shown under install.commands. Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim. Official client config requires Chartforge key Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Required environment variables: CHARTFORGE_API_KEY
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `chartforge-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove chartforge-mcp

Official Documentation & Sources

What it does

Radar identity is the `chartforge-mcp` package. It is clearly chart/visualization-oriented, but enough first-party documentation was not recovered in this pass to confirm exact rendering backends, auth, storage/publication and file-write semantics.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Generate charts/visualizations from structured data through ChartForge.

Representative uses

Generate charts from structured data
Produce visualization assets

Limitations

Exact supported chart types and export formats unresolved.
Whether generated assets are local or hosted is unresolved.
Authentication/storage/privacy are unresolved.

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: Unknown.
Cost: unknown
Risk and cautions: Data used for charts may be confidential; storage boundary must be confirmed.

Access scope and cautions

Write actions: Not verified
Sensitive access: Input datasets may be sensitive
Risk level: moderate

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-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Generate charts from structured data; Produce visualization assets.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Unknown. Recorded sensitive-access context: Input datasets may be sensitive.

What limitations and risks should I check before use?

Data used for charts may be confidential; storage boundary must be confirmed. Exact supported chart types and export formats unresolved. Whether generated assets are local or hosted is unresolved. Authentication/storage/privacy are unresolved. 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.