AgentUtility Synthforge — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Synthforge paid generative-media tools: Do quoted prices and payment authorization remain aligned with model-specific media inputs?

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

Best fit

Pay-per-call generative media tools for agents shipping product and marketing assets.

What we know

x402-paid MCP cluster for image, video, voice/music and related creative generation. Calls are paid individually in USDC on Base from an agent-held wallet; AgentUtility states it does not hold API keys, balances or sessions.

Maintenance / activity evidence

@agentutility/mcp-synthforge 0.8.15 published 2026-08-31T22:45:35.078Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Creative generation plus per-call payment authority. Writes: Spend USDC per tool call; Submit generation jobs.
Agent-held EVM private key.
Sensitive access: Wallet private key, Creative prompts/uploads, Generated assets

Primary operational risk is wallet/payment authority plus uploaded creative content.

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

All limitations / Review context

Do quoted prices and payment authorization remain aligned with model-specific media inputs?

The bounded review of the publisher's documented Synthforge paid generative-media tools 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.

Primary operational risk is wallet/payment authority plus uploaded creative content.
Creative generation plus per-call payment authority.
Agent-held EVM private key.
Prompts/media inputs are sent to AgentUtility/upstream model endpoints; payment authorization is signed locally.
Reviewed write actions: Spend USDC per tool call; Submit generation jobs
Sensitive access: Wallet private key, Creative prompts/uploads, Generated assets
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.
Every paid call spends USDC.
Tool catalog/prices are live and may change.
A private EVM key is required locally for x402 signing.
Generated media may be subject to model/provider content and licensing constraints.

Original activity observations

@agentutility/mcp-synthforge 0.8.15 published 2026-08-31T22:45:35.078Z

Technical identity

npm/@agentutility/mcp-synthforge

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

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 metadata ↗
@agentutility/mcp-synthforge
Recorded package identity, distribution or download evidence.
Evidence source ↗
agentutility.ai/mcp/synthforge/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
agentutility.ai/mcp/
Source material retained for this review.
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

Financial risk: package may sign and pay for calls or buy tokens. Never use production wallet/private key to test. Obtain explicit spending approval.
A private key is not an API key; do not expose it in project files, screenshots, logs, or chat transcripts.
Chargeable by default for tool invocation: per-call USDC/x402 pricing. Tool listing or MCP registration is not a free-use guarantee.
Publisher baseline documentation retained; live recheck unavailable. This update does not establish a fresh publisher-source verification.
Reviewed actionability is baseline documentation only; client compatibility and runtime operation have not been verified.
Literal command/entry path confirmed against official README; does not validate runtime or host compatibility.
Prior reviewed safety note: Do not treat starting the MCP process as consent to transact.
Prior reviewed safety note: Do not invoke any tool merely to confirm connectivity: publisher prices its tools per call in USDC.
Prior reviewed safety note: Do not supply or fund X402_PRIVATE_KEY for initial registration.
Prior reviewed safety note: Do not delete user data or assume this cancels upstream authorizations.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · retained baseline · Publisher instructions
npx -y @agentutility/mcp-synthforge
Configure / authenticate
MCP100 setup guide
Register local stdio MCP JSON with command npx and args ["-y","@agentutility/mcp-synthforge"], env X402_PRIVATE_KEY. Publisher requires funded Base USDC wallet for paid x402 calls; DO NOT substitute an API key or include private key in public config.
Check connection
Suggested check
Confirm MCP registration and tool discovery only. Calling tools can charge USDC; do not call a paid tool for verification.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `agentutility-synthforge`, remove the client entry with `claude mcp remove agentutility-synthforge`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Separate credential guidance (provider revocation is not verified): Publisher uses X402_PRIVATE_KEY for x402 USDC payments. Removing this variable or the MCP registration prevents new calls from this host but does not revoke the wallet private key. If exposed, rotate by creating a new wallet and handling any funds with wallet-provider guidance; no invented vendor revoke CLI.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove agentutility-synthforge

Official Documentation & Sources

https://www.npmjs.com/package/@agentutility/mcp-synthforge ↗

What it does

x402-paid MCP cluster for image, video, voice/music and related creative generation. Calls are paid individually in USDC on Base from an agent-held wallet; AgentUtility states it does not hold API keys, balances or sessions.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Pay-per-call generative media tools for agents shipping product and marketing assets.

Representative uses

Generate ad creative images
Create app icons/store screenshots
Generate media assets across supported models
Expand/transform existing images

Limitations

Every paid call spends USDC.
Tool catalog/prices are live and may change.
A private EVM key is required locally for x402 signing.
Generated media may be subject to model/provider content and licensing constraints.

Reviewed access

Access & risk

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

Authentication: Agent-held EVM private key.
Permissions: Creative generation plus per-call payment authority.
Data handling: Prompts/media inputs are sent to AgentUtility/upstream model endpoints; payment authorization is signed locally.
Cost: pay_per_call_x402
Risk and cautions: Primary operational risk is wallet/payment authority plus uploaded creative content.

Access scope and cautions

Write actions: Spend USDC per tool call Submit generation jobs
Sensitive access: Wallet private key Creative prompts/uploads Generated assets
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: Generate ad creative images; Create app icons/store screenshots; Generate media assets across supported models; Expand/transform existing images.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @agentutility/mcp-synthforge. Recorded transport: stdio. Recorded environment-variable notes: X402_PRIVATE_KEY. No configuration values are supplied here. Prerequisites: MCP client; Base-compatible wallet with USDC. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local EVM private key holding USDC on Base signs EIP-3009 payments; no AgentUtility API key.

Can it modify data or perform write operations?

Documented write actions include: Spend USDC per tool call; Submit generation jobs. Recorded permission boundary: Creative generation plus per-call payment authority.

What data-handling boundary should I consider?

Prompts/media inputs are sent to AgentUtility/upstream model endpoints; payment authorization is signed locally. Recorded sensitive-access context: Wallet private key; Creative prompts/uploads; Generated assets.

What limitations and risks should I check before use?

Primary operational risk is wallet/payment authority plus uploaded creative content. Every paid call spends USDC. Tool catalog/prices are live and may change. A private EVM key is required locally for x402 signing. Generated media may be subject to model/provider content and licensing constraints. 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.

What cost model is recorded?

The reviewed cost model is pay per call x402. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.