JustHandled Agent Utility Gateway
LocalAbout JustHandled Agent Utility Gateway
The JustHandled Agent Utility Gateway client provides a guarded CLI, JavaScript client, and local MCP server for 32 agent utilities and maintained-data lookups. Before paid calls, it checks pinned payment terms and returns a versioned evidence receipt.
Key features
- 01Catalog inspection and unpaid previews
- 0232 preflights, data lookups, and evidence products
- 03Payment-term checks before signing
- 04Versioned receipts for paid calls
- 05CLI, JavaScript client, and local MCP server
Use cases
- 01Inspect the catalog and preview a call
- 02Run a filename portability preflight
- 03Retrieve run or distribution evidence packs
- 04Call paid utilities with a dedicated wallet
MCP support
The local MCP server provides a free catalog tool and one paid tool for each gateway utility. If wallet configuration is missing, it returns an error without attempting payment; paid execution begins with a free preview and payment-term checks.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @justhandledlabs/agent-clientJH_EVM_PRIVATE_KEYSecretPrivate key for a dedicated Base wallet funded with USDC. Never use a primary wallet.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEJustHandled Agent Client
A guarded CLI, JavaScript client, and local MCP server for the JustHandled Agent Utility Gateway. The package exposes thirty-two preflights, maintained-data lookups, and evidence products. Twenty-two products cost $0.05 USDC; ten evidence-heavy or maintained-data products cost $0.25, including the live Chicago Contract Change Packet. Every paid call returns a versioned evidence receipt.
The client fails closed before signing. It accepts only the pinned JustHandled gateway, Base mainnet, canonical Base USDC, the exact per-product price, and the published merchant receiver. Customer inputs and complete customer results are not persisted by the gateway; maintained public-source snapshots are labeled in the receipt.
Inspect without a wallet
npx --package @justhandledlabs/agent-client justhandled-agent catalog
npx --package @justhandledlabs/agent-client justhandled-agent preview filename-portability-preflight --json '{"paths":["CON.txt"]}'
npx --package @justhandledlabs/agent-client justhandled-agent preview agent-run-evidence-pack --file agent-run-evidence-pack.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview agent-distribution-readiness-pack --file agent-distribution-readiness-pack.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview community-rule-credibility-preflight --file community-rule-credibility-preflight.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview qualified-demand-ledger --file qualified-demand-ledger.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview channel-fit-evidence-matrix --file channel-fit-evidence-matrix.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview proof-to-channel-evidence-packet --file proof-to-channel-evidence-packet.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview channel-experiment-postmortem --file channel-experiment-postmortem.sample.json
npx --package @justhandledlabs/agent-client justhandled-agent preview chicago-contract-change-packet --file chicago-contract-change-packet.sample.json
Preview performs an unpaid request and validates the returned x402 terms. It does not sign or spend.
The catalog includes API-response contract drift, webhook contract and replay, and policy-change evidence products. Packaged example inputs are available in examples/.
Machine-readable products, exact payment terms, and free deterministic fixtures are available from the gateway's product catalog, OpenAPI document, and sandbox index.
Execute one paid utility
Use a dedicated low-balance Base wallet. Never provide a primary wallet key.
export JH_EVM_PRIVATE_KEY=0x...
npx --package @justhandledlabs/agent-client justhandled-agent call filename-portability-preflight --json '{"paths":["CON.txt"]}'
PowerShell:
$env:JH_EVM_PRIVATE_KEY = "0x..."
npx.cmd --package @justhandledlabs/agent-client justhandled-agent call filename-portability-preflight --json '{"paths":["CON.txt"]}'
MCP configuration
{
"mcpServers": {
"justhandled": {
"command": "npx",
"args": ["-y", "@justhandledlabs/agent-client"],
"env": {
"JH_EVM_PRIVATE_KEY": "0xDEDICATED_LOW_BALANCE_WALLET_KEY"
}
}
}
}
The MCP server exposes a free catalog tool plus one paid tool per gateway utility. Missing wallet configuration produces an error instead of a payment attempt.
The package declares the official MCP Registry identity io.github.justhandledlabs/agent-gateway. Registry identity is discovery metadata only: installing or listing the server does not spend funds, and paid execution still requires a dedicated wallet plus the client's exact-term checks.
Security model
- Price, chain, asset, receiver, and gateway origin are pinned in code.
- The ten $0.25 products' 250,000-base-unit price is pinned separately from 50,000-base-unit checks.
- Every execution starts with an unpaid 402 preview.
- A mismatched term aborts before signing.
- The package never prints the private key.
- The gateway does not persist customer inputs or complete customer results. Maintained-data products may retain normalized public-source snapshots and disclose that state in the receipt.
- Treat all crypto transfers as irreversible and fund only a dedicated wallet.
Development
npm install
npm run check
The gateway implementation is intentionally not included in this client repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.