x402-btc-radar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_PAYMENT_USD | No | Maximum single payment amount. Default is 0.05; payments above this are refused. | 0.05 |
| X402_PRIVATE_KEY | No | Your own Base wallet private key (0x + 64 hex chars). Required for paid tools. The wallet only needs a small amount of USDC; signs an EIP-3009 authorization and does not need ETH. Recommended to use a dedicated small wallet. | |
| BTC_RADAR_API_URL | No | Override the upstream API URL (for testing only, must be https). |
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 |
|---|---|
| healthA | FREE. Checks the upstream x402 API (network, mainnet flag, whether radar data is loaded). No payment. |
| token_riskA | PAID $0.01 USDC on Base via x402 (paid from the caller's own wallet). Pre-trade safety check for one Base or BSC token: honeypot buy/sell simulation, buy/sell tax, mint/pause/blacklist/proxy/owner flags, holder concentration, liquidity, pool age. Returns verdict low|medium|high|honeypot, 0-100 score, action and reasons. Invalid input returns 400 and is not charged. Not investment advice. |
| token_risk_batchA | PAID $0.05 USDC per call (up to 10 tokens) on Base via x402, from the caller's own wallet. Same checks as token_risk. Pass either chain+addresses (single chain) or tokens[] (mixed chains). If no token can be checked you are not charged. Not investment advice. |
| btc_radar_latestA | PAID $0.01 USDC on Base via x402, from the caller's own wallet. Latest list of newly launched Bitcoin L1 tokens/inscriptions (BRC-20, Runes, Alkanes, Stamps) with stage, verdict, risk flags and sources. If no data is published the API returns 503 before payment. Not investment advice. |
| project_infoA | PAID $0.05 USDC on Base via x402, from the caller's own wallet. Structured analysis of one radar project by slug (what it is, entry, signature needs, risks, verdict). Use slugs from btc_radar_latest. Unknown slug returns 404 before payment. Not investment advice. |
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 5 tools
Each tool targets a distinct action: single-token risk check, batch risk check, BTC radar listing, per-project detail by slug, and a free health probe. The only near-pair is token_risk vs token_risk_batch, but the batch description clearly scopes it (up to 10 tokens, mixed chains) so misselection is unlikely.
All names use consistent snake_case and are domain-descriptive (token_risk, token_risk_batch, btc_radar_latest, project_info), with a predictable prefix family around token_risk and btc_radar. There is no verb_noun convention and 'health' is a bare outlier, but the set reads coherently.
Five tools is a tight, well-scoped surface for a paid risk/radar API, and each entry earns its place (single vs batch risk, listing vs detail, free health). Nothing looks redundant or bolted on.
Core workflows are covered end to end: discover new BTC L1 launches, drill into a project by slug, and screen individual or batched tokens for risk, plus a free health check. Minor gaps exist around historical/archived radar data and searching rather than only fetching the latest list.