AgentUtility Agentops — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Agentops trace and tool-permission review tools: Do probe findings distinguish measured execution evidence from generated red-team and cost briefs?

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

Best fit

Run paid agent-operations utilities from the AgentUtility cluster.

What we know

MCP server for the @agentutility agentops cluster — pay-per-call x402 tools, USDC on… Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Maintenance / activity evidence

@agentutility/mcp-agentops 0.1.4 published 2026-08-06T19:02:30.811Z

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: Agent metadata, Payment credentials

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

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

All limitations / Review context

Do probe findings distinguish measured execution evidence from generated red-team and cost briefs?

The bounded review of the publisher's documented Agentops trace and tool-permission review 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.

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.
Sensitive access: Agent metadata, Payment credentials
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.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
writeActions: exact exposed tool mutation authority
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
transport and actual executable entry point
Tool inventory, execution side effects and wallet custody are not established
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Original activity observations

@agentutility/mcp-agentops 0.1.4 published 2026-08-06T19:02:30.811Z

Technical identity

npm/@agentutility/mcp-agentops

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

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 ↗
@agentutility/mcp-agentops
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

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

Official Documentation & Sources

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

What it does

MCP server for the @agentutility agentops cluster — pay-per-call x402 tools, USDC on… Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Run paid agent-operations utilities from the AgentUtility cluster.

Representative uses

Invoke agentops tasks
Review pay-per-call price

Limitations

Tool inventory, execution side effects and wallet custody are not established
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

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: Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Access scope and cautions

Write actions: Not verified
Sensitive access: Agent metadata Payment credentials
Risk level: high

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 available discovery description lists: Invoke agentops tasks; Review pay-per-call price. These descriptions do not establish a fully verified tool inventory.

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?

Recorded sensitive-access context: Agent metadata; Payment credentials.

What limitations and risks should I check before use?

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent. Tool inventory, execution side effects and wallet custody are not established. 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.