Wicked MCP

What Wicked MCP does

Wicked MCP MCP server connects an MCP client to 12 Wicked services through one package. Its coverage includes market and on-chain data, protocol health, token safety, broker synchronization, regulatory filings, wallet checks, agent identity, reputation, tool reliability, hallucination checks, persistent memory, and x402 paywalls.

The package exposes 90 tools. It also provides six readable resources, including the service directory, platform guidance, and live endpoint catalogs. Seven prompts combine related calls into workflows such as token checks, dependency vetting, morning market briefings, claim verification, agent verification, reliable-tool discovery, and signed memory guidance.

How it works

The first four service groups are generated from live OpenAPI documents, so their available tools follow the deployed API definitions. Other tools are implemented separately for wallet-signature flows and endpoints outside the standard /v1 paths.

A local process communicates over stdio. Alternatively, an MCP client can use https://mcp.wickedapi.com/mcp over streamable HTTP without installing the package. The hosted endpoint is stateless and rate-limited by IP. Requests without credentials can still receive a real x402 payment challenge rather than being silently rejected or paid automatically.

The server does not sign transactions or retain private keys. Identity, registry registration, and memory operations that require signatures use messages or nonces supplied for signing by the caller’s wallet.

Setup and configuration

For a local MCP configuration, run the package with npx -y @wickedlabs/wicked-mcp. A client may pass WICKEDAPI_API_KEY for free, rate-limited access where supported, or WICKEDAPI_PAYER_PRIVATE_KEY for automatic x402 payment from a funded Base-mainnet wallet. Neither variable is required to start the server.

Without configuration, Token Risk remains free, as do five Trading Data API endpoints: sentiment, macro calendar, market overview, gas, and Kalshi probability. Service-specific API keys can also be configured for Registry, Identity, Sanity, Memory, and Paywall operations. Base URL variables are available when an installation must target alternate service hosts.

The remote endpoint can be used directly by a streamable-HTTP client. Self-hosting is supported through the repository’s Dockerfile or the built HTTP start command; HTTP deployments can configure rate limits, allowed hosts, and a trusted client-IP header.

Tools and capabilities

Wicked MCP MCP server groups tools by service:

• Trading tools cover prices, OHLCV, market signals, macro events, and selected chain reads.
• Protocol Health, Token Risk, Wallet, and Filings tools support DeFi, token, wallet, and public-company research.
• Broker Sync provides brokerage-related synchronization operations.
• Identity and Reputation tools support agent assertions, sandbox testing, and reputation data.
• Registry tools search and report on tool reliability, while Sanity checks help verify generated claims.
• Memory tools prepare, store, search, and manage signed agent memory flows.
• Paywall tools support tenant signup and related x402 operations.

The rug_check, vet_dependency, and other prompts provide predefined multi-tool sequences for clients that surface MCP prompts.

Limitations and notes

Paid calls may require an API key, x402 payment, or a service-specific credential. Automatic payment requires a funded Base-mainnet wallet and uses USDC; the server does not automatically pay when only the public remote endpoint is used. Some operations require the caller to produce wallet signatures, and sandbox identity results are not treated as verified.

The remote deployment is rate-limited per IP. API availability and tool lists can change because several tools reflect live OpenAPI catalogs. The Wicked MCP MCP server should therefore be evaluated against the service and authentication requirements of each workflow rather than treated as a single uniform API.