Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Wicked MCP

REMOTE · MCP.WICKEDAPI.COM · 2 COMPONENTS · SCANNED OCT 7

The whole Wicked suite for agents: trading, DeFi/token risk, identity, reputation, memory. x402.

65 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 8282 tokens (~108/item across 76 items; 70 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 5 days we've observed: 3 tool removals, 27 breaking changes, 0 auth/transport breaks, 43 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 99% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "memory_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 71 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Wicked MCP server?

Wicked MCP is a hosted endpoint at https://mcp.wickedapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.wickedapi.com

# add to Claude Code
claude mcp add --transport http choaticpixels-wicked-mcp 'https://mcp.wickedapi.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "choaticpixels-wicked-mcp": {
      "url": "https://mcp.wickedapi.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "choaticpixels-wicked-mcp": {
      "type": "http",
      "url": "https://mcp.wickedapi.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.choaticpixels-wicked-mcp]
url = "https://mcp.wickedapi.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "choaticpixels-wicked-mcp": {
      "type": "remote",
      "url": "https://mcp.wickedapi.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add choaticpixels-wicked-mcp --url 'https://mcp.wickedapi.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  choaticpixels-wicked-mcp:
    url: "https://mcp.wickedapi.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "choaticpixels-wicked-mcp": {
      "Transport": "http",
      "Url": "https://mcp.wickedapi.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add choaticpixels-wicked-mcp -t streamable-http -u 'https://mcp.wickedapi.com/mcp'
// mcp.json
{
  "mcpServers": {
    "choaticpixels-wicked-mcp": {
      "type": "http",
      "url": "https://mcp.wickedapi.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Oct 26 +5

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Stability: unverified → fail ▼ security
    • Tool “wickedapi_momentum” was removed ▼ security
    • Tool “wickedapi_funding_oi” was removed ▼ security
    • Tool “wickedapi_price” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: wicked-reputation → wickedapi security
    • Tool “memory_store” rewrote its description, which is the text the model reads security
    • Tool “reputation_transparency” rewrote its description, which is the text the model reads security
    • Tool “registry_featured_tools” rewrote its description, which is the text the model reads security
    • Tool “reputation_tiers” rewrote its description, which is the text the model reads security
    • Tool “memory_prepare” rewrote its description, which is the text the model reads security
    • Tool “registry_tool_detail” rewrote its description, which is the text the model reads security
    • Tool “memory_delete” rewrote its description, which is the text the model reads security
    • Tool “reputation_status” rewrote its description, which is the text the model reads security
    • Tool “memory_search” rewrote its description, which is the text the model reads security
    • Tool “registry_search_tools” rewrote its description, which is the text the model reads security
    • Tool “reputation_query” rewrote its description, which is the text the model reads security
    • Tool “registry_register_tool” rewrote its description, which is the text the model reads security
    • Tool “identity_jwks” rewrote its description, which is the text the model reads security
    • Tool “identity_status” rewrote its description, which is the text the model reads security
    • Tool “registry_report_tool” rewrote its description, which is the text the model reads security
    • Tool “reputation_statement” rewrote its description, which is the text the model reads security
    • Tool “identity_register” rewrote its description, which is the text the model reads security
    • Tool “memory_get” rewrote its description, which is the text the model reads security
    • Tool “identity_get_challenge” rewrote its description, which is the text the model reads security
    • Tool “sanity_check” rewrote its description, which is the text the model reads security
    • Tool “identity_get_nonce” rewrote its description, which is the text the model reads security
    • Tool “memory_deletions” rewrote its description, which is the text the model reads security
    • Tool “memory_history” rewrote its description, which is the text the model reads security
    • Tool “memory_update” rewrote its description, which is the text the model reads security
    • Tool “registry_tool_badge” rewrote its description, which is the text the model reads security
    • Tool “identity_submit_response” rewrote its description, which is the text the model reads security
    • Tool “sanity_check_batch” rewrote its description, which is the text the model reads security
    • “reputation_query” changed the type of “limit”: integer → number ▼ functional
    • “registry_search_tools” changed the type of “limit”: integer → number ▼ functional
    • Tool “memory_delete” dropped its output schema ▼ functional
    • Tool “registry_search_tools” dropped its output schema ▼ functional
    • Tool “memory_history” dropped its output schema ▼ functional
    • Tool “memory_search” dropped its output schema ▼ functional
    • Tool “reputation_statement” dropped its output schema ▼ functional
    • Tool “identity_get_nonce” dropped its output schema ▼ functional
    • Tool “reputation_status” dropped its output schema ▼ functional
    • Tool “sanity_check_batch” dropped its output schema ▼ functional
    • Tool “registry_tool_detail” dropped its output schema ▼ functional
    • Tool “memory_store” dropped its output schema ▼ functional
    • Tool “sanity_check” dropped its output schema ▼ functional
    • Tool “registry_featured_tools” dropped its output schema ▼ functional
    • Tool “identity_status” dropped its output schema ▼ functional
    • Tool “memory_deletions” dropped its output schema ▼ functional
    • Tool “memory_update” dropped its output schema ▼ functional
    • Tool “memory_prepare” dropped its output schema ▼ functional
    • Tool “memory_get” dropped its output schema ▼ functional
    • Tool “registry_register_tool” dropped its output schema ▼ functional
    • Tool “registry_tool_badge” dropped its output schema ▼ functional
    • Tool “reputation_transparency” dropped its output schema ▼ functional
    • Tool “reputation_query” dropped its output schema ▼ functional
    • Tool “registry_report_tool” dropped its output schema ▼ functional
    • Tool “identity_get_challenge” dropped its output schema ▼ functional
    • Tool “identity_submit_response” dropped its output schema ▼ functional
    • Tool “identity_jwks” dropped its output schema ▼ functional
    • Tool “identity_register” dropped its output schema ▼ functional
    • Tool “reputation_tiers” dropped its output schema ▼ functional
    • Schema quality: 193 → 108 ▲ functional
    • Tool coverage: 0% → 99% ▲ functional
    • First check of Schema quality: 100 functional
    • Schema quality: excellent → good functional
    • MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
    • New prompt “verify_agent” functional
    • New prompt “find_reliable_tool” functional
    • New prompt “agent_memory_guide” functional
    • New prompt “fact_check” functional
    • New prompt “rug_check” functional
    • New prompt “morning_briefing” functional
    • New prompt “vet_dependency” functional
    • MCP protocol version: 2026-07-28 → 2025-11-25 functional
    • New resource “platform-services” functional
    • New resource “token_risk-status” functional
    • New resource “trading-status” functional
    • New resource “broker_sync-status” functional
    • New resource “protocol_health-status” functional
    • New resource “platform-llms-txt” functional
    • Server version: 0.3.1 → 0.4.0 functional
    • New tool “defi_tvl” functional
    • New tool “basis” functional
    • New tool “broker_sync_prop_firms” functional
    • New tool “orderbook” functional
    • New tool “gas” functional
    • New tool “long_short_ratio” functional
    • New tool “protocol_health_refresh_all” functional
    • New tool “macro_calendar” functional
    • New tool “market_overview” functional
    • New tool “kalshi_probability” functional
    • New tool “protocol_health_sync_universe” functional
    • New tool “paywall_list_settlements” functional
    • New tool “atr” functional
    • New tool “paywall_import_routes” functional
    • New tool “ohlcv” functional
    • New tool “earnings_calendar” functional
    • New tool “broker_sync_transactions” functional
    • New tool “protocol_health_track_protocol” functional
    • New tool “broker_sync_register_user” functional
    • New tool “protocol_health_scoreboard” functional
    • New tool “token_risk” functional
    • New tool “momentum_score” functional
    • New tool “paywall_update_route” functional
    • New tool “broker_sync_connections” functional
    • New tool “protocol_health_list_protocols” functional
    • New tool “kalshi_market” functional
    • New tool “hyperliquid” functional
    • New tool “paywall_signup” functional
    • New tool “market_clock” functional
    • New tool “paywall_delete_route” functional
    • New tool “liquidity_levels” functional
    • New tool “funding_oi” functional
    • New tool “broker_sync_balances” functional
    • New tool “price” functional
    • New tool “broker_sync_positions” functional
    • New tool “sentiment” functional
    • New tool “paywall_get_tenant” functional
    • New tool “protocol_health_score” functional
    • New tool “rates” functional
    • New tool “paywall_create_route” functional
    • New tool “volatility” functional
    • New tool “fvg” functional
    • New tool “paywall_list_routes” functional
    • “memory_store” reworded the description of “metadata” cosmetic
    • “memory_store” reworded the description of “signature” cosmetic
    • “memory_search” reworded the description of “limit” cosmetic
    • “memory_history” reworded the description of “nonce” cosmetic
    • “identity_get_challenge” reworded the description of “wallet” cosmetic
    • “reputation_query” reworded the description of “sort” cosmetic
    • “reputation_query” reworded the description of “max_stake” cosmetic
    • “registry_search_tools” reworded the description of “protocol” cosmetic
    • “reputation_query” reworded the description of “min_stake” cosmetic
    • “memory_delete” reworded the description of “timestamp” cosmetic
    • “memory_search” reworded the description of “wallet” cosmetic
    • “memory_update” reworded the description of “tags” cosmetic
    • “memory_update” reworded the description of “memory_id” cosmetic
    • “memory_history” reworded the description of “timestamp” cosmetic
    • “identity_submit_response” reworded the description of “response_text” cosmetic
    • “memory_search” reworded the description of “payment_signature” cosmetic
    • “identity_get_challenge” reworded the description of “signature” cosmetic
    • “memory_update” reworded the description of “source” cosmetic
    • “registry_tool_detail” reworded the description of “tool_id” cosmetic
    • “memory_search” reworded the description of “q” cosmetic
    • “memory_update” reworded the description of “timestamp” cosmetic
    • “registry_report_tool” reworded the description of “evidence” cosmetic
    • “sanity_check_batch” reworded the description of “mode” cosmetic
    • “identity_register” reworded the description of “nonce” cosmetic
    • “sanity_check_batch” reworded the description of “context” cosmetic
    • “memory_delete” reworded the description of “wallet” cosmetic
    • “registry_register_tool” reworded the description of “endpoint_url” cosmetic
    • “memory_delete” reworded the description of “nonce” cosmetic
    • “memory_history” reworded the description of “signature” cosmetic
    • “memory_get” reworded the description of “signature” cosmetic
    • “memory_prepare” reworded the description of “params” cosmetic
    • “memory_prepare” reworded the description of “wallet” cosmetic
    • “memory_get” reworded the description of “timestamp” cosmetic
    • “memory_delete” reworded the description of “reason” cosmetic
    • “memory_history” reworded the description of “memory_id” cosmetic
    • “registry_register_tool” reworded the description of “owner_wallet” cosmetic
    • “memory_update” reworded the description of “wallet” cosmetic
    • “memory_search” reworded the description of “created_before” cosmetic
    • “identity_register” reworded the description of “wallet” cosmetic
    • “memory_delete” reworded the description of “memory_id” cosmetic
    • “memory_get” reworded the description of “memory_id” cosmetic
    • “memory_store” reworded the description of “timestamp” cosmetic
    • “memory_delete” reworded the description of “scope” cosmetic
    • “reputation_query” reworded the description of “min_reputation” cosmetic
    • “memory_prepare” reworded the description of “operation” cosmetic
    • “registry_register_tool” reworded the description of “signature” cosmetic
    • “identity_register” reworded the description of “signature” cosmetic
    • “registry_search_tools” reworded the description of “category” cosmetic
    • “memory_store” reworded the description of “wallet” cosmetic
    • “registry_search_tools” reworded the description of “limit” cosmetic
    • “registry_search_tools” reworded the description of “sort” cosmetic
    • “memory_search” reworded the description of “timestamp” cosmetic
    • “memory_search” reworded the description of “created_after” cosmetic
    • “memory_store” reworded the description of “tags” cosmetic
    • “memory_deletions” reworded the description of “wallet” cosmetic
    • “memory_get” reworded the description of “nonce” cosmetic
    • “memory_update” reworded the description of “signature” cosmetic
    • “reputation_status” reworded the description of “wallet” cosmetic
    • “memory_store” reworded the description of “content” cosmetic
    • “memory_delete” reworded the description of “signature” cosmetic
    • “memory_deletions” reworded the description of “nonce” cosmetic
    • “registry_report_tool” reworded the description of “reason” cosmetic
    • “registry_report_tool” reworded the description of “tool_id” cosmetic
    • “identity_get_nonce” reworded the description of “wallet” cosmetic
    • “identity_status” reworded the description of “wallet” cosmetic
    • “memory_history” reworded the description of “wallet” cosmetic
    • “memory_search” reworded the description of “nonce” cosmetic
    • “reputation_query” reworded the description of “min_slash_count” cosmetic
    • “identity_get_challenge” reworded the description of “nonce” cosmetic
    • “identity_submit_response” reworded the description of “challenge_id” cosmetic
    • “reputation_query” reworded the description of “limit” cosmetic
    • “memory_store” reworded the description of “source” cosmetic
    • “registry_register_tool” reworded the description of “protocol” cosmetic
    • “registry_tool_badge” reworded the description of “tool_id” cosmetic
  • 2 Oct 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 8 Oct 2026 · Probed https://mcp.wickedapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.wickedapi.com CN=YE1,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA384 6b1e7ec523588f6e69ebab54e88a87683e4
SANs: mcp.wickedapi.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.wickedapi.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
wickedapi.com. present 2371 13 Verified
mcp.wickedapi.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.wickedapi.com/mcp Verified 200
http (plaintext) http://mcp.wickedapi.com/mcp HTTPS enforced 301 https://mcp.wickedapi.com/mcp
MCP tools · 75 exposed · ~9,038 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
protocol_health_refresh_all ~38

[Protocol Health Oracle] Force an immediate live re-score of all tracked protocols. — Force an immediate live re-score of all tracked protocols.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

protocol_health_score ~114

[Protocol Health Oracle] Latest health score for one protocol: components (GitHub activity, TVL trend, treasury), source details, and score history. — Latest health score for one protocol: components (GitHub activity, TVL trend, treasury), source details, and score history.

NameTypeReqDescription
historynumber–Optional. Number of historical scores to include (default 10, max 100).
slugstringyesRequired (path). The protocol's defillama_slug, e.g. lido.

No output schema declared.

No examples provided.

protocol_health_scoreboard ~180

[Protocol Health Oracle] Public teaser: protocol name, score, and verdict only (no components/history) across the full tracked universe — auto-ingested from DefiLlama (TVL > $1M) plus curated protocols. — Public teaser: protocol name, score, and verdict only (no components/history) across the full tracked universe — auto-ingested from DefiLlama (TVL > $1M) plus curated protocols.

NameTypeReqDescription
categorystring–Optional. Filter by DefiLlama category, e.g. "Liquid Staking".
limitnumber–Optional. Rows to return (default 100, max 2000).
min_tvlstring–Optional. Only protocols with TVL >= this USD amount.
offsetstring–Optional. Pagination offset (default 0).

No output schema declared.

No examples provided.

protocol_health_sync_universe ~76

[Protocol Health Oracle] Force an immediate sync of the tracked-protocol universe from DefiLlama (TVL > $1M) — Force an immediate sync of the tracked-protocol universe from DefiLlama (TVL > $1M). Runs automatically once/day; use this to trigger it on demand.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

protocol_health_track_protocol ~130

[Protocol Health Oracle] Track a new protocol — Track a new protocol. Scored immediately from live GitHub + DeFiLlama data.

NameTypeReqDescription
chainstring–Optional. Default "ethereum".
defillama_slugstringyesDeFiLlama protocol slug, e.g. lido.
github_repostringyesowner/repo, e.g. lidofinance/core.
namestringyesDisplay name, e.g. "Lido".
treasury_addressstring–Optional. On-chain treasury address to score (Etherscan balance).

No output schema declared.

No examples provided.

rates ~117

[Trading Data API] US Treasury yield curve (1M–30Y) + recession-indicator spreads (10y-2y, 10y-3m), from FRED. — US Treasury yield curve (1M–30Y) + recession-indicator spreads (10y-2y, 10y-3m), from FRED. **Example:** `/v1/rates`

NameTypeReqDescription
seriesstring–Optional. A specific FRED series id (e.g. DGS10) for a single value.

No output schema declared.

No examples provided.

registry_create_api_key ~153

[Wicked Registry] Step 2 of getting a free API key. Submit the wallet, the timestamp and YOUR signature over the message from registry_onboarding_message(action=api_key). The key (wr_...) is returned once - store it and pass it as api_key to registry_search_tools / registry_tool_detail. Up to 3 active keys per wallet; past the daily cap calls fall back to x402.

NameTypeReqDescription
labelstring–Optional label for the key.
signaturestringyes0x-prefixed ECDSA signature over the message.
timestampstringyesThe timestamp returned with the message.
walletstringyes0x wallet that signed the message.

No output schema declared.

No examples provided.

registry_featured_tools ~24

[Wicked Registry] Top scored active tools. Public and free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

registry_lookup ~127

[Wicked Registry] Free lookup: find a tool's id and headline reliability score by name or URL fragment (q), exact endpoint URL (endpoint) or category. No key or payment. Use it to check a tool before your agent pays it; follow with registry_tool_badge or registry_tool_detail.

NameTypeReqDescription
categorystring––
endpointstring–Exact endpoint URL of the tool you are about to call.
limitnumber–1-25, default 10.
qstring–Name or URL fragment, at least 2 characters.

No output schema declared.

No examples provided.

registry_onboarding_message ~138

[Wicked Registry] Step 1 of self-onboarding. Returns the exact message YOU must sign (EIP-191 personal_sign) plus its timestamp, valid for about an hour. action=api_key (needs wallet) for a free API key, or action=register (needs name and endpoint_url) to list your own tool. This tool never signs anything.

NameTypeReqDescription
actionstringyes–
endpoint_urlstring–Tool endpoint URL (required for register).
namestring–Tool name (required for register).
walletstring–Your 0x wallet address (required for api_key).

No output schema declared.

No examples provided.

registry_register_tool ~191

[Wicked Registry] Register a tool you own so it gets real synthetic checks and a live score. Get the exact message to sign from registry_onboarding_message(action=register), sign it with owner_wallet, then call this. This tool never signs.

NameTypeReqDescription
categorystringyes–
descriptionstringyes–
endpoint_urlstringyesLive, publicly reachable endpoint.
namestringyes–
owner_walletstringyes0x wallet that signed the registration message.
protocolstringyes"x402", "mcp" or "rest".
schema_urlstring–Optional JSON Schema URL enabling the schema-conformance score.
signaturestringyes0x-prefixed ECDSA signature over the registration message.
timestampstringyesISO 8601 timestamp used in the signed message (within an hour of the call).

No output schema declared.

No examples provided.

registry_report_tool ~111

[Wicked Registry] File a complaint about a tool's reliability or behaviour. Public, rate-limited; reviewed manually, never auto-suspends.

NameTypeReqDescription
evidencestring–Optional note or URL.
reasonstringyes"downtime", "incorrect_response", "scam_or_abuse", "schema_violation" or "other".
reporterstringyesYour wallet address or another best-effort identifier.
tool_idstringyesThe tool's Wicked Registry id.

No output schema declared.

No examples provided.

registry_search_tools ~207

[Wicked Registry] Search x402/MCP tools by real reliability data (uptime, latency, schema conformance). Works via x402 (402 carries payment instructions) or a free API key (pass api_key, or set REGISTRY_API_KEY). No key yet? Call registry_onboarding_message then registry_create_api_key to get one yourself. For a quick free check of a known tool, use registry_lookup.

NameTypeReqDescription
api_keystring–Free Wicked Registry API key (wr_...). Overrides REGISTRY_API_KEY.
categorystring–e.g. "data", "crypto".
limitnumber–1-200, default 50.
min_scorenumber–Minimum composite score 0-100; unchecked tools are excluded once set.
protocolstring–"x402", "mcp" or "rest".
sortstring–"score" (default), "latency" or "recency".

No output schema declared.

No examples provided.

registry_tool_badge ~41

[Wicked Registry] A tool's current composite reliability score. Public and free.

NameTypeReqDescription
tool_idstringyesThe tool's Wicked Registry id.

No output schema declared.

No examples provided.

registry_tool_detail ~81

[Wicked Registry] One tool's full score breakdown, component history and recent real health checks. x402 or a free API key.

NameTypeReqDescription
api_keystring–Free Wicked Registry API key (wr_...). Overrides REGISTRY_API_KEY.
tool_idstringyesRegistry id from registry_lookup / registry_search_tools / registry_featured_tools.

No output schema declared.

No examples provided.

reputation_query ~174

[Wicked Reputation] Search/rank registered agents by tier, stake, reputation or slash history. Every filter is a typed query param.

NameTypeReqDescription
founding_memberboolean–True to only show founding members.
limitnumber–1-200, default 20.
max_stakenumber–Maximum active stake (USDC).
min_reputationnumber–Minimum reputation score.
min_slash_countnumber–Minimum slash events (1 finds agents ever slashed).
min_stakenumber–Minimum active stake (USDC).
sortstring–stake_amount | reputation_score | slash_count | registered_at, prefixed "-" (desc, default) or "+" (asc).
tierstring–Exact tier name, e.g. "gold".

No output schema declared.

No examples provided.

reputation_statement ~63

[Wicked Reputation] An agent's full position plus real event ledger (stakes, unstakes, withdrawals, slashes). Does not include WickedAPI call volume or fees — see the `note` field.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_status ~67

[Wicked Reputation] An agent's current reputation: tier, active/unbonding stake, score, slash count, founding-member badge. http_status 404 means the wallet never registered — treat as tier 'unranked'.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_tiers ~41

[Wicked Reputation] Live tier thresholds and benefits (min stake, rate-limit multiplier, fee discount). Read at call time — thresholds are admin-configurable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reputation_transparency ~41

[Wicked Reputation] Live transparency numbers: treasury address, custody model, unbonding cooldown, total stake, agents, slash events, founding-slot counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sanity_check ~176

[Wicked Sanity] Verify one claim before acting on it. Verdicts: supported | contradicted | unsupported | insufficient_evidence (see `data`). confidence_score is raw consistency (a "contradicted" verdict scores near 0). Policy: act on supported; treat unsupported/insufficient_evidence as unverified; reject contradicted. x402 or SANITY_API_KEY; 429 means a rate limit — see retry_after.

NameTypeReqDescription
claimstringyesThe single statement to verify (max 5,000 chars).
context––Source text the claim(s) must be faithful to. Required for mode "grounded".
modestring–"grounded" (default; check against context) or "open" (check against live web evidence — consistency with the web, not objective truth).

No output schema declared.

No examples provided.

sanity_check_batch ~133

[Wicked Sanity] Verify up to 50 claims against one shared context in a single call — prefer this over one sanity_check per sentence. `data` is a list in the same order as `claims`.

NameTypeReqDescription
claimsarrayyes1-50 statements, each up to 5,000 chars.
context––Source text the claim(s) must be faithful to. Required for mode "grounded".
modestring–"grounded" (default; check against context) or "open" (check against live web evidence — consistency with the web, not objective truth).

No output schema declared.

No examples provided.

sentiment ~76

[Trading Data API] Free, no signup required — Free, no signup required. Crypto Fear & Greed Index (alternative.me), current reading + optional history. **Example:** `/v1/sentiment?limit=7`

NameTypeReqDescription
limitnumber–Optional. Number of days of history (default 1, max 90).

No output schema declared.

No examples provided.

token_risk ~174

[Token Risk Oracle] Free, public, no signup — Free, public, no signup. Aggregates real on-chain risk signals from GoPlus Security for a token contract — honeypot detection, mint/ownership authority, holder & LP concentration, buy/sell tax, trust-list status — into one transparent risk score. Never a bare safe/unsafe claim: every flag GoPlus didn't return data for stays null, and the raw source data ships alongside the score.

NameTypeReqDescription
addressstringyesRequired. The token contract address (EVM) or mint address (Solana).
chainstringyesRequired. ethereum, bsc, base, polygon, arbitrum, optimism, avalanche, fantom, zksync, linea, scroll, or solana. A numeric EVM chain_id also works.

No output schema declared.

No examples provided.

volatility ~90

[Trading Data API] Deribit volatility: DVOL implied-vol index (30d forward) + latest realized volatility, for BTC or ETH. — Deribit volatility: DVOL implied-vol index (30d forward) + latest realized volatility, for BTC or ETH. **Example:** `/v1/volatility?currency=BTC`

NameTypeReqDescription
currencystring–Optional. BTC (default) or ETH.

No output schema declared.

No examples provided.

Common questions

What is the Wicked MCP server?

Wicked MCP is listed in the public MCP registry as io.github.choaticpixels/wicked-mcp. The whole Wicked suite for agents: trading, DeFi/token risk, identity, reputation, memory. x402. This page covers its hosted endpoint (https://mcp.wickedapi.com/mcp).

Is the Wicked MCP server safe to use?

Wicked MCP scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Wicked MCP server expose?

Wicked MCP exposes 75 tools: kalshi_probability, kalshi_market, funding_oi, long_short_ratio, orderbook, and 70 more. Their descriptions and schemas cost roughly 9,038 tokens of context every time the server is loaded.

Does the Wicked MCP server require authentication?

No. We connected to Wicked MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Wicked MCP server still maintained?

Wicked MCP is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.