AgentUtility Compose — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Compose clustered paid API operations: Do merged results and single settlement retain attributable sub-operation evidence and failure boundaries?

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

Best fit

Bundle multi-step AgentUtility operations into paid x402 compositions with one settlement.

What we know

AgentUtility compose cluster exposes bundled operations across its wider endpoint portfolio; every call uses agent-held USDC on Base and requires no AgentUtility API key.

Maintenance / activity evidence

@agentutility/mcp-compose 0.18.3 published 2026-08-06T19:02:40.931Z

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.
Composite API execution plus per-call payment authority. Writes: Spend USDC; Trigger multi-endpoint composite operations.
EVM private key.
Sensitive access: Wallet key, Potentially broad workflow inputs

Composite surface inherits risks from underlying endpoints and adds real payment authority.

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

All limitations / Review context

Do merged results and single settlement retain attributable sub-operation evidence and failure boundaries?

The bounded review of the publisher's documented Compose clustered paid API operations 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.

Composite surface inherits risks from underlying endpoints and adds real payment authority.
Composite API execution plus per-call payment authority.
EVM private key.
Inputs may be sent across AgentUtility/upstream services selected by the composition.
Reviewed write actions: Spend USDC; Trigger multi-endpoint composite operations
Sensitive access: Wallet key, Potentially broad workflow inputs
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 call spends USDC.
Underlying composed operations span many domains and may inherit their data/risk boundaries.
Tool catalog/prices are live.
Private EVM payment key must be protected.

Original activity observations

@agentutility/mcp-compose 0.18.3 published 2026-08-06T19:02:40.931Z

Technical identity

npm/@agentutility/mcp-compose

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

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

Setup · Watchlist

Gateway setup

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.
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 · Publisher instructions
npx -y @agentutility/mcp-compose
Configure / authenticate
MCP100 setup guide
Register local stdio MCP JSON with command npx and args ["-y","@agentutility/mcp-compose"], 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-compose`, remove the client entry with `claude mcp remove agentutility-compose`. 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-compose

Official Documentation & Sources

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

What it does

AgentUtility compose cluster exposes bundled operations across its wider endpoint portfolio; every call uses agent-held USDC on Base and requires no AgentUtility API key.

Capability: Developer Tools
Resource type: Gateway
Best fit: Bundle multi-step AgentUtility operations into paid x402 compositions with one settlement.

Representative uses

Call multi-endpoint composite workflows
Use address/data/guard/utility bundles
Pay once for composed operations instead of multiple independent settlements

Limitations

Every call spends USDC.
Underlying composed operations span many domains and may inherit their data/risk boundaries.
Tool catalog/prices are live.
Private EVM payment key must be protected.

Reviewed access

Access & risk

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

Authentication: EVM private key.
Permissions: Composite API execution plus per-call payment authority.
Data handling: Inputs may be sent across AgentUtility/upstream services selected by the composition.
Cost: pay_per_call_x402
Risk and cautions: Composite surface inherits risks from underlying endpoints and adds real payment authority.

Access scope and cautions

Write actions: Spend USDC Trigger multi-endpoint composite operations
Sensitive access: Wallet key Potentially broad workflow inputs
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: Call multi-endpoint composite workflows; Use address/data/guard/utility bundles; Pay once for composed operations instead of multiple independent settlements.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @agentutility/mcp-compose. Recorded transport: stdio. Recorded environment-variable notes: X402_PRIVATE_KEY. No configuration values are supplied here. Prerequisites: MCP client; funded Base wallet. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Agent-held EVM private key holding USDC on Base signs x402 payment authorization.

Can it modify data or perform write operations?

Documented write actions include: Spend USDC; Trigger multi-endpoint composite operations. Recorded permission boundary: Composite API execution plus per-call payment authority.

What data-handling boundary should I consider?

Inputs may be sent across AgentUtility/upstream services selected by the composition. Recorded sensitive-access context: Wallet key; Potentially broad workflow inputs.

What limitations and risks should I check before use?

Composite surface inherits risks from underlying endpoints and adds real payment authority. Every call spends USDC. Underlying composed operations span many domains and may inherit their data/risk boundaries. Tool catalog/prices are live. Private EVM payment key must be protected. 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.