x402-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X402_NETWORK | No | CAIP-2 network id. Use eip155:84532 for Base Sepolia testnet. | eip155:8453 |
| X402_BASE_URL | No | Base URL of the seller API. | https://x402-api.fly.dev |
| X402_MAX_PRICE_USD | No | Spending guard: max USD per single paid call. | 0.10 |
| X402_BUYER_PRIVATE_KEY | No | Private key of the paying wallet. Omit to run in challenge-only mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | Free. Fetches the live product catalog from the x402-tools seller API (prices, ids and schemas are never hardcoded here). |
| package_trust_checkA | Install-safety signals for an npm or PyPI package: registry metadata, install-script usage, OSV advisories, typosquat risk, and a 0-100 trust score. (price: $0.05 USDC per call) [catalog: bundled fallback, API was unreachable at startup] |
| repo_merge_lookupA | Predicts whether a GitHub repository will merge an AI-authored or external pull request, based on its stated AI/contribution policy and historical merge rates. (price: $0.05 USDC per call) [catalog: bundled fallback, API was unreachable at startup] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool addresses a completely distinct task: fetching product catalog, checking package trust, and predicting PR merges. There is zero functional overlap, so an agent would never confuse which tool to select.
Naming mixes conventions: 'list_products' follows verb_noun, while 'package_trust_check' and 'repo_merge_lookup' are noun_verb (object+verb). All use underscores, but the verb placement is inconsistent, which slightly reduces predictability.
With only 3 tools, the server is lean and each tool serves a clear, standalone purpose. The count is appropriate for a specialized utility server, though it borders on minimal.
The tools are independent utilities, not part of a lifecycle workflow, so there are no obvious missing CRUD operations. Each tool appears self-contained, though the domain is broad and could potentially support additional related functions (e.g., package details, repo history), but nothing critical is missing.