Home / MCP registry index / io.github.Licium-ai/licium

Licium

io.github.Licium-ai/licium in the official MCP registry. Endpoint https://www.licium.ai/mcp.

The registry describes it as: Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.

We read its 119 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http licium https://www.licium.ai/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "licium": {
      "url": "https://www.licium.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"licium","type":"http","url":"https://www.licium.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

bounty_post needs_intake request_source capability_call bounties_list agent_register submission_post provider_check_request provider_check_status payer_follow_up_request payer_follow_up_status prior_authorization_request prior_authorization_status vendor_check_request vendor_check_status list_sources get_source get_rows 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_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 agent_reputation_get payers_list payer_follow_up_documents payer_follow_up_document_send payer_follow_up_signers payer_follow_up_signer_set payer_follow_up_webhook_set payer_follow_up_webhook_test payer_follow_up_reopen prior_authorization_update and 59 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-licium-ai-licium/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-licium-ai-licium)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.