cryptoguard
https://gpartin--cryptoguard-api-fastapi-app.modal.run
Registry code: 018cbcabab865a1a
CryptoGuard validates crypto trades before execution. Use cryptoguard_search to find token IDs, then cryptoguard_validate_trade or cryptoguard_scan_token to assess risk. cryptoguard_rug_check requires a chain and pair address.
- endpoint
- https://gpartin--cryptoguard-api-fastapi-app.modal.run/mcp
- door code
- 9a536c59d3b7433e
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is cryptoguard live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is cryptoguard free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does cryptoguard have?
- 7 tools: cryptoguard_validate_trade_plus, cryptoguard_counterfactual_trade, cryptoguard_search, cryptoguard_rug_check, cryptoguard_scan_token, cryptoguard_health, cryptoguard_validate_trade.
- Is cryptoguard safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.9%· all time 99.1%
last good check
of 7 tools
- down → live
- degraded → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- used for
- validate a crypto trade before execution
- check a dex pair for rug pull risk
- scan a token for anomalies
- find a token's coingecko id
- takes → gives
- text, data → data
- tools
- 7 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
cryptoguard_health reads open 16h ago
Check CryptoGuard API health, version, and service status. No payment required. Use this to verify the service is running.
{ "type": "object", "properties": { "verbose": { "type": "boolean", "default": false, "description": "Return detailed health info including uptime and version details (default: false)." } }, "additionalProperties": false }arguments 11 linescryptoguard_validate_trade reads auth-required 10h ago
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.
{ "type": "object", "required": [ "token" ], "properties": { "chain": { "type": "string", "description": "Blockchain for contract address resolution (ethereum, solana, base, bsc, polygon, avalanche, arbitrum)." }, "token": { "type": "string", "description": "Token to validate. Can be a name (bitcoin), symbol (BTC), or contract address (0x...)." }, "action": { "enum": [ "buy", "sell", "swap" ], "type": "string", "description": "Trade action type (default: buy)." }, "amount_usd": { "type": "number", "description": "Trade amount in USD for concentration risk analysis." }, "pair_address": { "type": "string", "description": "DEX pair address for rug pull check." } } }arguments 33 linescryptoguard_validate_trade_plus reads unknown 16h ago
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.
{ "type": "object", "required": [ "training", "test" ], "properties": { "test": { "description": "Trade candidate sample to evaluate." }, "sequence": { "type": "array", "description": "Optional ordered sequence for trajectory/regime checks." }, "training": { "type": "array", "minItems": 2, "description": "Reference normal samples." }, "field_level": { "enum": [ 0, 1 ], "type": "integer", "description": "0=real field, 1=complex field (default: 1)." }, "sensitivity": { "type": "number", "description": "Anomaly sensitivity (default: 1.0)." }, "intervention_tests": { "type": "array", "description": "Optional intervention variants for mechanism probing." }, "intervention_labels": { "type": "array", "items": { "type": "string" }, "description": "Optional labels for intervention tests." }, "counterfactual_tests": { "type": "array", "description": "Optional what-if variants for sensitivity analysis." } } }arguments 48 linescryptoguard_counterfactual_trade reads unknown 16h ago
Stateless what-if sensitivity analysis. Submit baseline + counterfactual variants in one request and receive tipping-point guidance.
{ "type": "object", "required": [ "training", "base_test", "counterfactual_tests" ], "properties": { "training": { "type": "array", "minItems": 2, "description": "Reference normal samples." }, "base_test": { "description": "Baseline sample under evaluation." }, "field_level": { "enum": [ 0, 1 ], "type": "integer", "description": "0=real field, 1=complex field (default: 1)." }, "sensitivity": { "type": "number", "description": "Anomaly sensitivity (default: 1.0)." }, "counterfactual_tests": { "type": "array", "minItems": 1, "description": "What-if variants of the baseline sample." } } }arguments 35 linescryptoguard_search reads unknown 12h ago
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.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Token name, symbol, or contract address to search." } } }arguments 12 linescryptoguard_rug_check reads unknown 12h ago
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.
{ "type": "object", "required": [ "chain", "pair_address" ], "properties": { "chain": { "type": "string", "description": "Blockchain (solana, ethereum, base, bsc)." }, "pair_address": { "type": "string", "description": "DEX pair contract address." } } }arguments 17 linescryptoguard_scan_token reads unknown 12h ago
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.
{ "type": "object", "required": [ "coin_id" ], "properties": { "coin_id": { "type": "string", "description": "CoinGecko coin ID (e.g., 'bitcoin', 'solana', 'pepe')." }, "sensitivity": { "type": "number", "description": "Anomaly sensitivity multiplier (default: 1.0). Higher = more sensitive." } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id018cbcabab865a1a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/018cbcabab865a1a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/018cbcabab865a1a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.