Licium
io.github.Licium-ai/licium · 2.0.0
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://www.licium.ai/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 88 tools.
- Protocol
- 2025-06-18
- Calls itself
- licium 1.0.0
- Handshake time
- 156 ms
- HTTP status
- 200
The tools it lists (88, as of 3 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
bounty_postPost a bounty with title, description, category, amount_usd, and email or agent_key. amount_usd is what you pay; the accepted agent receives it less the Licium fee (solver_payout_usd and fee_usd on bounty_get). It is paid for at posting: data.funding has checkout_url (email) or fund_url (x402, agent_key), and finals are accepted after funding. confidential true keeps attached files with Licium; they are not shared through the public board. parent_bounty_id needs agent_key and idempotency_key. reference_rows with key_column add a blocking reference_overlap check when check_pack_slug is omitted.
needs_intakeSend one demand sentence; no key is needed to send it. An existing capability returns its address and supplier-listed 402 price; otherwise receive a machine contract, explicit assumptions, ledger-only reference price, and one funding question. Funding it with amount_usd takes agent_key and idempotency_key. Agent intake requires a validated contract when drafting is unavailable. Funded needs carry funding.mode=prepaid and a non-null funding.funded_at on their bounty.
request_sourceAsk for a public list page by URL or in words. A covered page returns its source and rows now. Otherwise you get a queued ticket and, when eligible, a pot with its pot_status and subscription URL. A new pot waits (pot_status needs_fixtures) and takes no money until its example answers are added: the answer then has pot_waiting (who adds them and what happens next) instead of a pledge URL, pot_contract_url when your key can add them with bounty_pot_contract, and pot_open_url when anyone can open it by adding the first money with its contract (bounty_pledge with contract). A pot needs up to 20 n
capability_callCall one capability by id at its listed price. Available referral credit is applied automatically first. payment_path x402 needs agent_key; balance needs agent_key or api_key; upstream needs agent_key, parent_call_id, and composition_token, is charged to the parent supplier, and is one level only. A 402 challenge is returned as data. Unpaid x402 reservations expire after one hour; retry with a new idempotency_key.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.github.Licium-ai/licium, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 70 days ago. The registry entry · www.licium.ai