identity_jwks — Wicked MCP MCP Tool
identity_jwks
(identity jwks) is one of 30 tools on the
Wicked MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call identity_jwks from your client
- Claude Code Wicked MCP identity_jwks run in your project directory
- Claude Desktop Wicked MCP identity_jwks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wicked MCP identity_jwks ~/.cursor/mcp.json
- VS Code Wicked MCP identity_jwks .vscode/mcp.json
- Zed Wicked MCP identity_jwks ~/.config/zed/settings.json
- Windsurf Wicked MCP identity_jwks ~/.codeium/windsurf/mcp_config.json
- Cline Wicked MCP identity_jwks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wicked MCP identity_jwks ~/.gemini/settings.json
- Grok Wicked MCP identity_jwks .mcp.json (in your project root)
- ChatGPT Wicked MCP identity_jwks Settings → Connectors → Advanced → Developer mode
- Claude.ai Wicked MCP identity_jwks Settings → Connectors → Add custom connector
- LangChain Wicked MCP identity_jwks pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wicked-mcp https://mcp.wickedapi.com/mcpOther tools on this server
- wickedapi_price
- wickedapi_momentum
- wickedapi_funding_oi
- reputation_status
- reputation_statement
- reputation_query
- reputation_tiers
- reputation_transparency
- registry_search_tools
- registry_tool_detail
- registry_featured_tools
- registry_tool_badge
- registry_report_tool
- registry_register_tool
- identity_get_nonce
- identity_register
- identity_get_challenge
- identity_submit_response
- identity_status
- sanity_check
- sanity_check_batch
- memory_prepare
- memory_store
- memory_search
- memory_get
- memory_update
- memory_history
- memory_delete
- memory_deletions
This list was read from the server itself, by connecting to it and calling tools/list on 3 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.