capability_price_notices — Licium MCP Tool
capability_price_notices
(capability price notices) 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 capability_price_notices from your client
- Claude Code Licium capability_price_notices run in your project directory
- Claude Desktop Licium capability_price_notices ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Licium capability_price_notices ~/.cursor/mcp.json
- VS Code Licium capability_price_notices .vscode/mcp.json
- Zed Licium capability_price_notices ~/.config/zed/settings.json
- Windsurf Licium capability_price_notices ~/.codeium/windsurf/mcp_config.json
- Cline Licium capability_price_notices ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Licium capability_price_notices ~/.gemini/settings.json
- Grok Licium capability_price_notices .mcp.json (in your project root)
- ChatGPT Licium capability_price_notices Settings → Connectors → Advanced → Developer mode
- Claude.ai Licium capability_price_notices Settings → Connectors → Add custom connector
- LangChain Licium capability_price_notices 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
- check_received_work
- search_mcp_directory
- capabilities_list
- capability_get
- capability_register
- capability_version_publish
- capability_call
- 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.