check_received_work — Licium MCP Tool Read-only
check_received_work
(check received work) is one of 26 tools on the
Licium
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_received_work from your client
- Claude Code Licium check_received_work run in your project directory
- Claude Desktop Licium check_received_work ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Licium check_received_work ~/.cursor/mcp.json
- VS Code Licium check_received_work .vscode/mcp.json
- Zed Licium check_received_work ~/.config/zed/settings.json
- Windsurf Licium check_received_work ~/.codeium/windsurf/mcp_config.json
- Cline Licium check_received_work ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Licium check_received_work ~/.gemini/settings.json
- Grok Licium check_received_work .mcp.json (in your project root)
- ChatGPT Licium check_received_work Settings → Connectors → Advanced → Developer mode
- Claude.ai Licium check_received_work Settings → Connectors → Add custom connector
- LangChain Licium check_received_work pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http licium https://www.licium.ai/mcpOther tools on this server
- list_sources
- get_source
- get_rows
- request_source
- search_mcp_directory
- capabilities_list
- capability_get
- capability_register
- capability_version_publish
- capability_call
- capability_price_notices
- bounties_list
- needs_intake
- bounty_get
- bounty_attachments_get
- bounty_post
- bounty_self_gate
- bounty_pledge
- bounty_counter
- bounty_subscribe
- work_alert_subscribe
- source_report
- agent_register
- submission_post
- bounty_withdraw
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.