Server Details
Per-transaction crypto trade validator for AI agents. Returns deterministic PROCEED / CAUTION / BLOCK verdicts using WaveGuard anomaly detection, history checks, and rug-pull risk analysis.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
7 toolscryptoguard_counterfactual_tradeInspect
Stateless what-if sensitivity analysis. Submit baseline + counterfactual variants in one request and receive tipping-point guidance.
| Name | Required | Description | Default |
|---|---|---|---|
| training | Yes | Reference normal samples. | |
| base_test | Yes | Baseline sample under evaluation. | |
| field_level | No | 0=real field, 1=complex field (default: 1). | |
| sensitivity | No | Anomaly sensitivity (default: 1.0). | |
| counterfactual_tests | Yes | What-if variants of the baseline sample. |
cryptoguard_healthInspect
Check CryptoGuard API health, version, and service status. No payment required. Use this to verify the service is running.
| Name | Required | Description | Default |
|---|---|---|---|
| verbose | No | Return detailed health info including uptime and version details (default: false). |
cryptoguard_rug_checkInspect
Assess rug pull risk for a specific DEX trading pair. Scores 6 risk factors (0-100): liquidity depth, pair age, volume/liquidity ratio, price action, buy/sell imbalance, and metadata.
Example: check if a new Solana pair is a potential rug pull.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | Yes | Blockchain (solana, ethereum, base, bsc). | |
| pair_address | Yes | DEX pair contract address. |
cryptoguard_scan_tokenInspect
Scan a single token for anomalous market behavior using WaveGuard physics-based anomaly detection. Compares the token to TIER-MATCHED peers (microcaps vs microcaps, large-caps vs large-caps). Returns anomaly scores, risk level, and explanations.
Example: scan 'solana' to check if its metrics are unusual.
| Name | Required | Description | Default |
|---|---|---|---|
| coin_id | Yes | CoinGecko coin ID (e.g., 'bitcoin', 'solana', 'pepe'). | |
| sensitivity | No | Anomaly sensitivity multiplier (default: 1.0). Higher = more sensitive. |
cryptoguard_searchInspect
Search for a token's CoinGecko coin ID by name, symbol, or contract address. Use this first if you're unsure of the correct coin_id for scan_token or validate_trade.
Example: search 'pepe' to find the correct coin ID.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Token name, symbol, or contract address to search. |
cryptoguard_validate_tradeInspect
Validate a crypto trade BEFORE execution. Returns a verdict: PROCEED, CAUTION, or BLOCK. Runs 5 checks: peer anomaly scan via WaveGuard physics engine, self-history comparison, rug pull risk assessment, CEX/DEX price cross-check, and concentration risk analysis. Accepts token name, symbol, or contract address.
Example: validate buying $500 of PEPE before executing.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | Blockchain for contract address resolution (ethereum, solana, base, bsc, polygon, avalanche, arbitrum). | |
| token | Yes | Token to validate. Can be a name (bitcoin), symbol (BTC), or contract address (0x...). | |
| action | No | Trade action type (default: buy). | |
| amount_usd | No | Trade amount in USD for concentration risk analysis. | |
| pair_address | No | DEX pair address for rug pull check. |
cryptoguard_validate_trade_plusInspect
Premium stateless decision bundle for one-shot trade gating. Caller provides full context (training/test + optional what-if blocks) and receives verdict, risk score, instability/mechanism signals, and recommendation.
| Name | Required | Description | Default |
|---|---|---|---|
| test | Yes | Trade candidate sample to evaluate. | |
| sequence | No | Optional ordered sequence for trajectory/regime checks. | |
| training | Yes | Reference normal samples. | |
| field_level | No | 0=real field, 1=complex field (default: 1). | |
| sensitivity | No | Anomaly sensitivity (default: 1.0). | |
| intervention_tests | No | Optional intervention variants for mechanism probing. | |
| intervention_labels | No | Optional labels for intervention tests. | |
| counterfactual_tests | No | Optional what-if variants for sensitivity analysis. |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!