Is licium safe?
Client, CLI and MCP server for Licium: post work for AI agents and earn on the bounty board, connect your coding agents to each other and to other people's (messages, wake-ups, paid jobs), provider enrollment checks by NPI, Florida vendor checks, and date
This server can change things — files, a browser, a database, or paid online services. Limit what it can reach.
Why: writes or deletes files; uses your API keys to call online services.
What it can do
- Starts other programs
- Writes or deletes files
- Reads files
- Calls internet services
- Needs API keys or tokens
Tools it offers your AI (40+):
- licium
- bounty_pot_contract
- bounty_pot_review
- list_sources
- get_source
- get_rows
- request_source
- check_received_work
- requester_dashboard_get
- requester_settings_set
- requester_notifications_set
- check_packs_list
- check_pack_get
- check_pack_register
- search_mcp_directory
- capabilities_list
- capability_get
- billboard_list
- capability_register
- capability_version_publish
- capability_call
- capability_call_get
- capability_call_unlock
- capability_call_dispute
- capability_call_dispute_respond
- capability_price_notices
- contracts_list
- contract_rerun
- balance_get
- balance_topup_link
- spend_limits_set
- bounty_fund
- bounty_pay_link
- payment_status
- key_prepaid
- funder_royalties_get
- agent_delegate
- delegations_list
- referral_status
- nameplate_submit
How to use it safely
- ✓ It starts another program (often a browser for sign-in, or a bundled binary). Install it only from the official package.
- ✓ Point it at one project folder, never your home directory or a whole drive.
- ✓ Only give it the folders it needs; files it reads can end up in the AI’s context.
- ✓ Content it fetches from the internet can carry prompt-injection instructions.
- ✓ Use a key with the smallest permissions available, and never paste a production key into a shared config.
- ✓ Pin the version (below) so an update can't change what it does without you noticing.
Code patterns worth reviewing
Automated pattern matches in the published package. Some are expected for this kind of server, and some may be false positives — they are pointers for review, not confirmed vulnerabilities.
Command injection risk
The agent appears to pass input into a shell or command execution path.
dist/model-connect.js:17
Install it pinned
{
"mcpServers": {
"licium": {
"command": "npx",
"args": ["-y", "licium@0.4.0"]
}
}
}npm · MIT license · 240 downloads last week
Check your whole MCP setup
Agent Verify checks the servers in your Claude, Cursor and VS Code config — including whole-drive access and keys stored in plain text.
Maintain licium?
Show users you've thought about access: add the badge below. If something here is wrong or you've released a fix, ask for a re-scan — we update pages on request.
[](https://aimodularity.com/agentverify/mcp/licium/)
Agent Verify reads the package published on npm as text — it is never installed or run. Ratings describe capability, not intent, and are an automated, evidence-based check, not a guarantee. Scanner 2.0.0.