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

Whole Wicked suite for agents: market data, SEC filings, wallet checks, risk, identity, memory.

Available components

remote · mcp.wickedapi.com 73 npm · @wickedlabs/wicked-mcp 46
+4 this week 73 Trust /100

Last scanned (21 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (24 Oct 2026). See the changelog before you install this server.

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 Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 19374 tokens (~167/item across 116 items; 108 tools + 8 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 109 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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1
    • Server version: 0.7.3 → 0.7.4 functional
  • 24 Oct 26 +2
    • Authorization: unverified → fail ▼ critical
    • Tool “chain_token_balance” rewrote its description, which is the text the model reads security
    • Tool “chain_tx” rewrote its description, which is the text the model reads security
    • Tool “crypto_news” rewrote its description, which is the text the model reads security
    • Tool “defi_tvl” rewrote its description, which is the text the model reads security
    • Tool “earnings_calendar” rewrote its description, which is the text the model reads security
    • Tool “filings_8k_events” rewrote its description, which is the text the model reads security
    • Tool “filings_filing” rewrote its description, which is the text the model reads security
    • Tool “filings_freshness” rewrote its description, which is the text the model reads security
    • Tool “filings_insider_summary” rewrote its description, which is the text the model reads security
    • Tool “filings_insider_trades” rewrote its description, which is the text the model reads security
    • Tool “filings_latest_preview” rewrote its description, which is the text the model reads security
    • Tool “filings_search” rewrote its description, which is the text the model reads security
    • Tool “funding_oi” rewrote its description, which is the text the model reads security
    • Tool “fvg” rewrote its description, which is the text the model reads security
    • Tool “gas” rewrote its description, which is the text the model reads security
    • Tool “hyperliquid” 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 “identity_get_nonce” rewrote its description, which is the text the model reads security
    • Tool “identity_get_test_key” 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_register” rewrote its description, which is the text the model reads security
    • Tool “identity_sandbox_register” 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 “kalshi_market” rewrote its description, which is the text the model reads security
    • Tool “kalshi_probability” rewrote its description, which is the text the model reads security
    • Tool “liquidations” rewrote its description, which is the text the model reads security
    • Tool “liquidity_levels” rewrote its description, which is the text the model reads security
    • Tool “long_short_ratio” rewrote its description, which is the text the model reads security
    • Tool “macro_calendar” rewrote its description, which is the text the model reads security
    • Tool “market_clock” rewrote its description, which is the text the model reads security
    • Tool “market_overview” 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 “memory_deletions” 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 “memory_history” 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 “memory_search” rewrote its description, which is the text the model reads security
    • Tool “memory_store” 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 “momentum_score” rewrote its description, which is the text the model reads security
    • Tool “ohlcv” rewrote its description, which is the text the model reads security
    • Tool “orderbook” rewrote its description, which is the text the model reads security
    • Tool “paywall_create_route” rewrote its description, which is the text the model reads security
    • Tool “paywall_delete_route” rewrote its description, which is the text the model reads security
    • Tool “paywall_get_tenant” rewrote its description, which is the text the model reads security
    • Tool “paywall_import_routes” rewrote its description, which is the text the model reads security
    • Tool “paywall_list_routes” rewrote its description, which is the text the model reads security
    • Tool “paywall_list_settlements” rewrote its description, which is the text the model reads security
    • Tool “paywall_signup” rewrote its description, which is the text the model reads security
    • Tool “paywall_update_route” rewrote its description, which is the text the model reads security
    • Tool “polymarket” rewrote its description, which is the text the model reads security
    • Tool “price” rewrote its description, which is the text the model reads security
    • Tool “protocol_health_list_protocols” rewrote its description, which is the text the model reads security
    • Tool “protocol_health_refresh_all” rewrote its description, which is the text the model reads security
    • Tool “protocol_health_score” rewrote its description, which is the text the model reads security
    • Tool “protocol_health_scoreboard” rewrote its description, which is the text the model reads security
    • Tool “protocol_health_sync_universe” rewrote its description, which is the text the model reads security
    • Tool “protocol_health_track_protocol” rewrote its description, which is the text the model reads security
    • Tool “rates” rewrote its description, which is the text the model reads security
    • Tool “registry_create_api_key” 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 “registry_key_info” rewrote its description, which is the text the model reads security
    • Tool “registry_lookup” rewrote its description, which is the text the model reads security
    • Tool “registry_onboarding_message” 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 “registry_report_tool” rewrote its description, which is the text the model reads security
    • Tool “registry_revoke_key” 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 “registry_tool_badge” 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 “reputation_erc8004” rewrote its description, which is the text the model reads security
    • Tool “reputation_get_nonce” rewrote its description, which is the text the model reads security
    • Tool “reputation_history” rewrote its description, which is the text the model reads security
    • Tool “reputation_leaderboard” 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 “reputation_register” rewrote its description, which is the text the model reads security
    • Tool “reputation_stake” 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 “reputation_status” 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 “reputation_transparency” rewrote its description, which is the text the model reads security
    • Tool “reputation_unstake” rewrote its description, which is the text the model reads security
    • Tool “reputation_withdraw” 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 “sanity_check_batch” rewrote its description, which is the text the model reads security
    • Tool “sanity_get_check” rewrote its description, which is the text the model reads security
    • Tool “sentiment” rewrote its description, which is the text the model reads security
    • Tool “token_risk” rewrote its description, which is the text the model reads security
    • Tool “verdict” rewrote its description, which is the text the model reads security
    • Tool “volatility” rewrote its description, which is the text the model reads security
    • Tool “wallet_check” rewrote its description, which is the text the model reads security
    • Tool “wallet_sanctions_check” rewrote its description, which is the text the model reads security
    • Tool “web_search” 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 “atr” rewrote its description, which is the text the model reads security
    • Tool “basis” rewrote its description, which is the text the model reads security
    • Tool “broker_sync_balances” rewrote its description, which is the text the model reads security
    • Tool “broker_sync_connections” rewrote its description, which is the text the model reads security
    • Tool “broker_sync_positions” rewrote its description, which is the text the model reads security
    • Tool “broker_sync_prop_firms” rewrote its description, which is the text the model reads security
    • Tool “broker_sync_register_user” rewrote its description, which is the text the model reads security
    • Tool “broker_sync_transactions” rewrote its description, which is the text the model reads security
    • Tool “chain_balance” rewrote its description, which is the text the model reads security
    • Tool “chain_block” rewrote its description, which is the text the model reads security
    • Tool “chain_ens” rewrote its description, which is the text the model reads security
    • Tool “chain_nonce” rewrote its description, which is the text the model reads security
    • Tool “memory_delete” is now declared destructive security
    • Tool “paywall_delete_route” is now declared destructive security
    • Tool “registry_revoke_key” is now declared destructive security
    • Tool “reputation_unstake” is now declared destructive security
    • Tool “reputation_withdraw” is now declared destructive security
    • Schema quality: 122 → 167 ▼ functional
    • Schema quality: good → excellent functional
    • Destructive annotations: All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • New prompt “counterparty_check” functional
    • New prompt “trade_idea_check” functional
    • New prompt “insider_watch” functional
    • Server version: 0.7.2 → 0.7.3 functional
    • Server version: 0.7.1 → 0.7.2 functional
    • New tool “paywall_demo_weather” functional
    • New tool “wallet_portfolio” functional
  • 23 Oct 26 +1
    • Schema quality: 6926 → 14000 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 0.6.0 → 0.7.1 functional
    • New tool “broker_sync_register_user” functional
    • New tool “broker_sync_transactions” functional
    • New tool “chain_balance” functional
    • New tool “chain_block” functional
    • New tool “chain_ens” functional
    • New tool “chain_nonce” functional
    • New tool “chain_token_balance” functional
    • New tool “chain_tx” functional
    • New tool “crypto_news” functional
    • New tool “defi_tvl” functional
    • New tool “earnings_calendar” functional
    • New tool “funding_oi” functional
    • New tool “fvg” functional
    • New tool “gas” functional
    • New tool “hyperliquid” functional
    • New tool “kalshi_market” functional
    • New tool “kalshi_probability” functional
    • New tool “liquidations” functional
    • New tool “liquidity_levels” functional
    • New tool “long_short_ratio” functional
    • New tool “macro_calendar” functional
    • New tool “market_clock” functional
    • New tool “market_overview” functional
    • New tool “momentum_score” functional
    • New tool “ohlcv” functional
    • New tool “orderbook” functional
    • New tool “polymarket” functional
    • New tool “price” functional
    • New tool “protocol_health_list_protocols” functional
    • New tool “protocol_health_refresh_all” functional
    • New tool “protocol_health_score” functional
    • New tool “protocol_health_scoreboard” functional
    • New tool “protocol_health_sync_universe” functional
    • New tool “protocol_health_track_protocol” functional
    • New tool “rates” functional
    • New tool “registry_key_info” functional
    • New tool “registry_revoke_key” functional
    • New tool “reputation_erc8004” functional
    • New tool “reputation_get_nonce” functional
    • New tool “reputation_history” functional
    • New tool “reputation_leaderboard” functional
    • New tool “reputation_register” functional
    • New tool “reputation_stake” functional
    • New tool “reputation_unstake” functional
    • New tool “reputation_withdraw” functional
    • New tool “sanity_get_check” functional
    • New tool “sentiment” functional
    • New tool “token_risk” functional
    • New tool “verdict” functional
    • New tool “volatility” functional
    • New tool “broker_sync_connections” functional
    • New tool “broker_sync_balances” functional
    • New tool “basis” functional
    • New tool “atr” functional
    • New tool “web_search” functional
    • New tool “broker_sync_positions” functional
    • New tool “broker_sync_prop_firms” functional
  • 22 Oct 26 65

    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 4 Nov 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 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 6e6d2e811b6b1eb28f94363cbd5ca254d1d
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 308 https://mcp.wickedapi.com/mcp
MCP tools · 108 exposed · ~19,143 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
memory_store ~206

[Wicked Memory] Store a memory (free, fair-use rate limited). A real embedding is computed at write time. Run memory_prepare with operation 'store' and these same arguments first. Use when you want to save something for later, scoped to your wallet. Not for changing an existing memory (use memory_update). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
contentstringyesText to remember (max 16 KB).
metadataobject–Free-form JSON object (max 8 KB).
noncestringyesFrom memory_prepare (single use).
signaturestringyesYour wallet's signature over memory_prepare's message_to_sign.
sourcestring–Which agent/session wrote this.
tagsarray–Up to 20 short tags.
timestampstringyesFrom memory_prepare.
walletstringyesYour agent's 0x wallet address.

No output schema declared.

No examples provided.

memory_update ~229

[Wicked Memory] Update without overwriting: creates a new version and closes the old one (valid_until / superseded_by). Omitted fields carry over; only the current version can be updated (409 otherwise). Use when you want to change a memory while keeping its history (a new version supersedes the old). Not for removing it (use memory_delete). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
contentstring–New text (re-embedded). Provide at least one of content/tags/metadata/source.
memory_idstringyesUUID of the CURRENT version to supersede.
metadataobject–Replacement metadata object.
noncestringyesFrom memory_prepare (single use).
signaturestringyesYour wallet's signature over memory_prepare's message_to_sign.
sourcestring–New source label.
tagsarray–Replacement tags.
timestampstringyesFrom memory_prepare.
walletstringyesYour agent's 0x wallet address.

No output schema declared.

No examples provided.

momentum_score ~257

[Trading Data API] Alias of /v1/verdict. Multi-asset momentum verdict (bias, confidence, thesis, entry/invalidation/targets, signal readings) from the oracle.py pipeline, run on a separate Python service. Scoped to 10 assets. **Example:** `/v1/momentum-score?symbol=BTC&timeframe=1h` Use when you want a ready-made LONG/SHORT/NEUTRAL view with confidence, thesis and entry/invalidation/targets for a supported asset. Not for raw inputs (use price, atr, funding_oi). Same data as verdict, which is the newer name. Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

NameTypeReqDescription
symbolstringyesRequired. One of: BTC, ETH, SOL, SUI, NVDA, IBIT, COIN, QQQ, TQQQ, DIA.
timeframestring–Optional. 15m, 1h, 4h, 1D, 1W (default 1h).

No output schema declared.

No examples provided.

ohlcv ~257

[Trading Data API] OHLCV candles (oldest-first) for crypto or stocks. Routes to Alpaca SIP / Alpaca-crypto / Coinbase. **Example:** `/v1/ohlcv?symbol=NVDA&timeframe=1h&limit=100` Use when you need historical candles to chart or compute indicators yourself. Not for only the latest price (use price) or a ready-made indicator (atr, fvg, liquidity_levels). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

NameTypeReqDescription
classstring–Optional. stock|crypto for non-curated symbols.
limitnumber–Optional. Candles to return (default 100, max 300).
symbolstringyesRequired. e.g. BTC, NVDA, SPY.
timeframestring–Optional. 1m,5m,15m,30m,1h,2h,4h,6h,12h,1D,1W (default 1h).

No output schema declared.

No examples provided.

orderbook ~198

[Trading Data API] Top-of-book depth + spread (bps) from Binance, Bybit, or Hyperliquid. **Example:** `/v1/orderbook?symbol=BTC&exchange=binance&depth=10` Use when you need top-of-book depth and spread (bps) on Binance, Bybit or Hyperliquid. Not for a prediction-market book (use kalshi_market). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

NameTypeReqDescription
depthnumber–Optional. Levels per side (default 10, max 50).
exchangestring–Optional. binance (default), bybit, or hyperliquid.
symbolstringyesRequired. Base crypto symbol (e.g. BTC).

No output schema declared.

No examples provided.

paywall_create_route ~284

[x402 Paywall] Paywall a new endpoint with x402 pay-per-call, settled in USDC straight to payTo. With upstreamUrl, paid requests are proxied to your backend. Applies live within ~20s (needs PAYWALL_API_KEY). Use when you want to put one HTTP endpoint behind x402 pay-per-call, paid in USDC straight to your wallet. Not for many routes at once (use paywall_import_routes). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
assetstring–Payment token contract; defaults to USDC on the network.
descriptionstring–Up to 200 chars: letters, digits, space . _ -
methodstring–Default GET.
networkstringyesCAIP-2 id: Base mainnet eip155:8453, Base Sepolia eip155:84532.
pathstring–Route path, e.g. "/weather".
payTostringyesYour payout wallet (0x…). Settlement pays here directly; nothing is custodied.
pricestringyesDecimal USD amount, e.g. "0.01" or "$0.01".
upstreamUrlstring–Your https backend. Omit for the demo confirmation payload.

No output schema declared.

No examples provided.

paywall_delete_route ~88

[x402 Paywall] Remove a paywalled route; applies within ~20s (needs PAYWALL_API_KEY). Use when you want a route removed from the paywall. Not for changing its price (use paywall_update_route). Behavior: DESTRUCTIVE and not reversible; confirm intent before calling.

NameTypeReqDescription
idstringyesRoute id from paywall_list_routes.

No output schema declared.

No examples provided.

paywall_demo_weather ~134

[x402 Paywall] Call the live demo route on the paywall gateway (GET /wickedapi/weather) to see a real x402 challenge: unpaid, it returns HTTP 402 with the decoded price, network and payTo in payment_required. A safe way to learn what a paywalled endpoint looks like before creating your own. Use when you want to see a real x402 payment challenge from a paywalled route (price, network, payTo) without creating anything. Not for setting up your own paywall (use paywall_signup then paywall_create_route). Behavior: read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paywall_get_tenant ~53

[x402 Paywall] Your tenant record (needs PAYWALL_API_KEY). Use when you want your tenant record (name, slug, key hint). Not for route management. Behavior: read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paywall_import_routes ~114

[x402 Paywall] Bulk upsert routes keyed on (method, path) — paywall a whole API in one call (needs PAYWALL_API_KEY). Use when you want to paywall many routes in one call (upsert on method and path). Not for a single route (use paywall_create_route). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
routesarrayyesRoute objects, same fields as paywall_create_route.

No output schema declared.

No examples provided.

paywall_list_routes ~60

[x402 Paywall] List your paywalled routes (needs PAYWALL_API_KEY). Use when you want your paywalled routes and their prices. Not for earnings (use paywall_list_settlements). Behavior: read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paywall_list_settlements ~82

[x402 Paywall] Your real on-chain USDC settlements (earnings) (needs PAYWALL_API_KEY). Use when you want your real on-chain USDC settlements (earnings). Not for route configuration (use paywall_list_routes). Behavior: read-only.

NameTypeReqDescription
limitnumber–Default 50, max 200.

No output schema declared.

No examples provided.

paywall_signup ~148

[x402 Paywall] Create a tenant account. Returns a Bearer apiKey ONCE — store it and set PAYWALL_API_KEY. Rate-limited to 5/hour per IP. Use when you want a paywall tenant account and its API key (shown once). Not for managing routes of an existing tenant. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
namestringyesLetters, digits, space . _ - (max 100).
slugstringyesLowercase a-z0-9 and hyphens, 2-40 chars; becomes your mount path prefix /{slug}.

No output schema declared.

No examples provided.

paywall_update_route ~268

[x402 Paywall] Partial update of a route (e.g. change price or payout wallet); applies live within ~20s (needs PAYWALL_API_KEY). Use when you want to change a route's price, payout wallet or upstream without a redeploy. Not for creating or deleting routes. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
assetstring–Payment token contract; defaults to USDC on the network.
descriptionstring–Up to 200 chars: letters, digits, space . _ -
idstringyesRoute id from paywall_list_routes.
methodstring–Default GET.
networkstring–CAIP-2 id: Base mainnet eip155:8453, Base Sepolia eip155:84532.
pathstring–Route path, e.g. "/weather".
payTostring–Your payout wallet (0x…). Settlement pays here directly; nothing is custodied.
pricestring–Decimal USD amount, e.g. "0.01" or "$0.01".
upstreamUrlstring–Your https backend. Omit for the demo confirmation payload.

No output schema declared.

No examples provided.

polymarket ~225

[Trading Data API] Polymarket prediction markets with live probabilities: question, per-outcome probability, 24h and total volume, liquidity, best bid/ask, one-day price change and end date. Top markets by volume, liquidity or soonest end, or free-text search. **Example:** `/v1/polymarket?q=bitcoin&limit=5` Use when you want Polymarket markets with live per-outcome probabilities and volume. Not for Kalshi markets (use kalshi_probability). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

NameTypeReqDescription
limitnumber–Optional. 1-25 (default 10).
qstring–Optional. Free-text search, e.g. bitcoin, fed rate, election.
sortstring–Optional. volume (default), liquidity or ending. Ignored when q is set.

No output schema declared.

No examples provided.

price ~186

[Trading Data API] Current spot price for crypto (Coinbase) or US equities/ETFs (Alpaca SIP), via the shared routing layer. **Example:** `/v1/price?symbol=BTC` Use when you need the current spot price of one crypto asset or US stock/ETF. Not for history or candles (use ohlcv), or a trading view (use momentum_score or verdict). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

NameTypeReqDescription
classstringyesOptional. stock|crypto — required for symbols outside the curated list.
symbolstringyesRequired. e.g. BTC, ETH, SUI, NVDA, SPY.

No output schema declared.

No examples provided.

protocol_health_list_protocols ~175

[Protocol Health Oracle] All tracked protocols with their latest health score and verdict. Use when you need every tracked protocol with its latest score and verdict. Not for one protocol's details (use protocol_health_score). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

NameTypeReqDescription
categorystring–Optional. Filter by DefiLlama category.
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_refresh_all ~79

[Protocol Health Oracle] Force an immediate live re-score of all tracked protocols. Use when you need every tracked protocol re-scored right now instead of waiting for the schedule. Not for a single protocol (read it with protocol_health_score). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

protocol_health_score ~182

[Protocol Health Oracle] Latest health score for one protocol: components (GitHub activity, TVL trend, treasury), source details, and score history. Use when you are vetting one protocol before integrating it and want GitHub activity, TVL trend and treasury components. Not for a ranking (use protocol_health_scoreboard) or token contract risk (use token_risk). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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 ~186

[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. Use when you want the free public ranking of every tracked DeFi protocol: name, score and verdict only. Not for the component breakdown for one protocol (use protocol_health_score). Behavior: read-only and free; no key or payment needed.

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 ~110

[Protocol Health Oracle] Force an immediate sync of the tracked-protocol universe from DefiLlama (TVL > $1M). Runs automatically once/day; use this to trigger it on demand. Use when you want the tracked universe re-synced from DefiLlama (TVL above $1M), which also runs automatically on a schedule. Not for routine reads. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

protocol_health_track_protocol ~180

[Protocol Health Oracle] Track a new protocol. Scored immediately from live GitHub + DeFiLlama data. Use when a protocol you care about is not tracked yet and you want it scored from live GitHub and DefiLlama data. Not for reading an existing score. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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 ~167

[Trading Data API] US Treasury yield curve (1M–30Y) + recession-indicator spreads (10y-2y, 10y-3m), from FRED. **Example:** `/v1/rates` Use when you need the US Treasury yield curve and recession spreads (10y-2y, 10y-3m). Not for event dates (use macro_calendar). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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 ~203

[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. Use when you signed the onboarding message and want a free Registry API key (shown once). Not for inspecting a key (use registry_key_info). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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 ~55

[Wicked Registry] Top scored active tools. Public and free. Use when you want the top-scored active tools with no key or payment. Not for filtered search (use registry_search_tools). Behavior: read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

registry_key_info ~96

[Wicked Registry] Metadata and usage for a Registry API key (wr_...): label, created time, call counts. Pass api_key, or set REGISTRY_API_KEY. Use when you want a Registry API key's label, creation time and usage counts. Not for creating or revoking a key. Behavior: read-only.

NameTypeReqDescription
api_keystring–Registry API key to inspect. Overrides REGISTRY_API_KEY.

No output schema declared.

No examples provided.

registry_lookup ~170

[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. Use when you want a free lookup of a tool's id and headline score by name, URL fragment or exact endpoint before you call it. Not for full detail (use registry_tool_detail). Behavior: read-only.

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 ~179

[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. Use when you are starting self-serve onboarding and need the exact message to sign. Not for when you already have a signature (use registry_create_api_key or registry_register_tool). Behavior: read-only.

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 ~240

[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. Use when you own a tool and want it listed and monitored, with your wallet's signature over the registration message. Not for finding tools. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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 ~155

[Wicked Registry] File a complaint about a tool's reliability or behaviour. Public, rate-limited; reviewed manually, never auto-suspends. Use when a tool misbehaved and you want to file a complaint for manual review. Not for reading scores. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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_revoke_key ~108

[Wicked Registry] PERMANENTLY revoke a Registry API key (the one presented). Use if a key leaked. Pass api_key, or set REGISTRY_API_KEY. Use when a Registry API key leaked or is no longer needed and must be disabled permanently. Not for inspecting a key (use registry_key_info). Behavior: DESTRUCTIVE and not reversible; confirm intent before calling.

NameTypeReqDescription
api_keystring–Registry API key to revoke. Overrides REGISTRY_API_KEY.

No output schema declared.

No examples provided.

registry_search_tools ~248

[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. Use when you want to find x402/MCP tools filtered by category, protocol or minimum reliability score. Not for a quick free check of a known tool (use registry_lookup). Behavior: read-only.

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 ~71

[Wicked Registry] A tool's current composite reliability score. Public and free. Use when you want one tool's current composite score as a free badge. Not for the breakdown (use registry_tool_detail). Behavior: read-only.

NameTypeReqDescription
tool_idstringyesThe tool's Wicked Registry id.

No output schema declared.

No examples provided.

registry_tool_detail ~115

[Wicked Registry] One tool's full score breakdown, component history and recent real health checks. x402 or a free API key. Use when you want one tool's full score breakdown and recent real health checks. Not for finding tools (use registry_search_tools or registry_lookup). Behavior: read-only.

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_erc8004 ~90

[Wicked Reputation] Cross-reference a wallet against the open ERC-8004 Identity and Reputation registries (read-only). Free. Use when you want to cross-reference a wallet against the open ERC-8004 identity and reputation registries. Not for Wicked's own staking data (use reputation_status). Behavior: read-only.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_get_nonce ~120

[Wicked Reputation] Step 1 of every signed Reputation call (register, stake, unstake, withdraw): a one-time nonce plus the exact message to sign. Each signed call needs a fresh nonce. Use when you are about to register, stake, unstake or withdraw and need the one-time message to sign. Not for read-only lookups, which need no signature. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_history ~77

[Wicked Reputation] An agent's history of reputation/tier changes over time. Free. 404 means the wallet never registered. Use when you want how one agent's reputation and tier changed over time. Not for current standing (use reputation_status). Behavior: read-only.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_leaderboard ~80

[Wicked Reputation] Public leaderboard: every agent's current active stake, tier and slash count. Free. Use when you want the public ranking of agents by active stake, with tier and slash count. Not for filtered searches (use reputation_query). Behavior: read-only.

NameTypeReqDescription
limitnumber–Max rows (default set by the service).

No output schema declared.

No examples provided.

reputation_query ~208

[Wicked Reputation] Search/rank registered agents by tier, stake, reputation or slash history. Every filter is a typed query param. Use when you want to filter or rank agents by tier, stake, reputation or slash history. Not for one known wallet (use reputation_status). Behavior: read-only.

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_register ~157

[Wicked Reputation] Register your wallet as an agent (no stake required). Needs your signature over reputation_get_nonce's message; this tool never signs. Use when you want to register your wallet as an agent, with your own signature over the nonce message. Not for staking (use reputation_stake after funding the treasury). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
noncestringyesNonce from a FRESH reputation_get_nonce call.
signaturestringyes0x-prefixed ECDSA signature (EIP-191) over that nonce's message, from YOUR wallet.
walletstringyesYour 0x wallet address on Base.

No output schema declared.

No examples provided.

reputation_stake ~220

[Wicked Reputation] Record a USDC stake that YOU already sent on-chain to the treasury (see reputation_transparency for the address). Real funds: send the transfer from your own wallet first, then pass its tx_hash with a signed nonce. This tool never moves funds or signs. Use when you already sent USDC on-chain to the treasury and want that stake recorded, with its transaction hash and a signed nonce. Not for moving funds, which this server never does. Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

NameTypeReqDescription
amountnumberyesUSDC amount staked.
noncestringyesNonce from a FRESH reputation_get_nonce call.
signaturestringyes0x-prefixed ECDSA signature (EIP-191) over that nonce's message, from YOUR wallet.
tx_hashstringyesHash of your on-chain USDC transfer to the treasury.
walletstringyesYour 0x wallet address on Base.

No output schema declared.

No examples provided.

reputation_statement ~101

[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. Use when you need an agent's full position and ledger of stakes, unstakes, withdrawals and slashes. Not for a quick tier check (use reputation_status). Behavior: read-only.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_status ~113

[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'. Use when you want one agent's tier, stake, reputation score and slash count before dealing with it. Not for the event history (use reputation_statement) or a ranking (use reputation_leaderboard). Behavior: read-only.

NameTypeReqDescription
walletstringyesThe 0x wallet address.

No output schema declared.

No examples provided.

reputation_tiers ~79

[Wicked Reputation] Live tier thresholds and benefits (min stake, rate-limit multiplier, fee discount). Read at call time — thresholds are admin-configurable. Use when you want the live tier thresholds and benefits (minimum stake, rate-limit multiplier, fee discount). Not for a specific agent's tier (use reputation_status). Behavior: read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reputation_transparency ~75

[Wicked Reputation] Live transparency numbers: treasury address, custody model, unbonding cooldown, total stake, agents, slash events, founding-slot counts. Use when you want the treasury address, custody model, unbonding cooldown and totals, for example before staking. Not for per-agent data. Behavior: read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reputation_unstake ~181

[Wicked Reputation] Start the unbonding period for `amount` of your active stake. It stops counting toward tier/reputation immediately; withdraw after the cooldown (see reputation_transparency). Needs a signed nonce. Use when you want to start the unbonding period for part of your active stake, with a signed nonce. Not for collecting funds (use reputation_withdraw once the cooldown has passed). Behavior: DESTRUCTIVE and not reversible; confirm intent before calling.

NameTypeReqDescription
amountnumberyesUSDC amount to unbond.
noncestringyesNonce from a FRESH reputation_get_nonce call.
signaturestringyes0x-prefixed ECDSA signature (EIP-191) over that nonce's message, from YOUR wallet.
walletstringyesYour 0x wallet address on Base.

No output schema declared.

No examples provided.

reputation_withdraw ~159

[Wicked Reputation] Pay out every unbonding stake whose cooldown has elapsed, in one on-chain transfer to your wallet. Safe to retry if a payout fails. Needs a signed nonce. Use when your unbonding cooldown has elapsed and you want every matured stake paid out to your wallet. Not for starting the unbonding (use reputation_unstake). Behavior: DESTRUCTIVE and not reversible; confirm intent before calling.

NameTypeReqDescription
noncestringyesNonce from a FRESH reputation_get_nonce call.
signaturestringyes0x-prefixed ECDSA signature (EIP-191) over that nonce's message, from YOUR wallet.
walletstringyesYour 0x wallet address on Base.

No output schema declared.

No examples provided.

sanity_check ~233

[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. Use when you must verify one claim before acting on it, either against source text you supply or against live web evidence. Not for many claims at once (use sanity_check_batch). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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 ~190

[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`. Use when you have a multi-sentence output to verify against one shared context in a single call (up to 50 claims). Not for a single claim (use sanity_check). Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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.

sanity_get_check ~92

[Wicked Sanity] Fetch a previously run check by its check_id (returned by sanity_check / sanity_check_batch). x402 or SANITY_API_KEY like the other Sanity calls. Use when you want to re-read an earlier check by its check_id. Not for running a new check. Behavior: read-only.

NameTypeReqDescription
check_idstringyesThe check_id from an earlier sanity_check result.

No output schema declared.

No examples provided.

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 wickedapi-wicked-mcp 'https://mcp.wickedapi.com/mcp'
Common questions

What is the Wicked MCP server?

Wicked MCP is listed in the public MCP registry as io.github.WickedAPI/wicked-mcp. Whole Wicked suite for agents: market data, SEC filings, wallet checks, risk, identity, memory. This page covers its hosted endpoint (https://mcp.wickedapi.com/mcp).

Is the Wicked MCP server safe to use?

Wicked MCP scores 73 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 108 tools: kalshi_probability, kalshi_market, funding_oi, long_short_ratio, orderbook, and 103 more. Their descriptions and schemas cost roughly 19,143 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.