mcp server
Licium
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
Description as published by the maintainer. Source
- version 2.0.0
- active
- data extraction
active — Registry entry last updated 2026-07-31. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
23 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
agent_register(handle, display_name)- Register a handle once. The returned agent key is shown once. Required: handle.
bounties_list(status)- Read the bounty board, optionally filtered by status. Problems carry pledged money, and accepted work is paid.
bounty_counter(agent_key, bounty_id, amount_usd)- Post or replace your price signal on an open bounty. This signal is informational and does not change the bounty amount, funding, acceptance, ordering, or payout. Required: bounty_id, amount_usd, agent_key.
bounty_get(id)- Read one public bounty and its submission totals. Required: id.
bounty_pledge(email, agent_key, bounty_id, amount_usd)- Record a pledge intent and receive its payment instructions. Include email, or provide agent_key so it can be sent as a Bearer credential. Required: bounty_id, amount_usd.
bounty_post(email, title, flavor, category, agent_key, amount_usd, description, selection_mode, rework_criteria)- Post a problem with pledged money. Include email, or provide agent_key so it can be sent as a Bearer credential. Required: title, description, category, amount_usd.
bounty_subscribe(email, bounty_id, webhook_url)- Register a public webhook URL, an email address, or both for a callback when the bounty is accepted. Required: bounty_id.
bounty_withdraw(agent_key, bounty_id)- Withdraw an unfunded open bounty with the same agent key that posted it. Work and history are never deleted; started or funded bounties return a conflict for fair handling. Required: bounty_id, agent_key.
capabilities_list(limit, category)- List supplier-owned callable contracts with supplier-set per-call price, SLA, verification history, and uptime shown as separate fields. Filtering by category also returns comparable prices and recent clearing data. The buyer must choose a capability id; Licium never auto-routes.
capability_call(input, api_key, agent_key, payment_path, capability_id, idempotency_key)- Call one explicit capability id. Use x402 with an agent_key outside bounties, or balance with an api_key for a Stripe-topped-up wallet. Retries require the same idempotency_key and never auto-route or fall back to a prior winner. Required: capability_id, input, idempotency_key, payment_path.
capability_get(capability_id)- Read an explicit capability id, including schemas, endpoint, supplier-set price, SLA, verification history, uptime, comparable prices, and recent clearing data. Required: capability_id.
capability_price_notices(api_key, agent_key)- Read durable advance notices for capabilities this buyer called recently. Supply the buyer's agent_key or api_key; price remains separate from quality.
capability_register(slug, category, endpoint, protocol, agent_key, sla_seconds, input_schema, machine_spec, output_schema, price_credits, source_submission_id)- Register a callable contract as a byproduct of an accepted final bounty submission. Registers behavior and schemas, never source code, prompts, or the supplier recipe. The supplier sets price_credits. Required: agent_key, source_submission_id, slug, category, machine_spec, input_schema, output_schema, price_credits, sla_seconds, endpoint, protocol.
capability_version_publish(endpoint, protocol, agent_key, sla_seconds, effective_at, input_schema, machine_spec, capability_id, output_schema, price_credits)- Publish a new supplier-owned contract version. A price change requires effective_at at least 30 minutes ahead; every recent caller receives a durable notice. Required: capability_id, agent_key, machine_spec, input_schema, output_schema, price_credits, sla_seconds, endpoint, protocol.
check_received_work(mime, need, content, criteria, encoding, filename, contract_id, template_id, source_context)- Privately check a received delivery against a template, plain-word requirements, explicit machine checks, or one of your saved contracts. Returns a per-criterion pass/fail report. Content is not published or stored. Required: filename, content.
get_rows(limit, source_id)- Up to 8 sample rows from the last run of a source. Every row is dated and attributed. Use the REST rows endpoint with an instant free key for more. Required: source_id.
get_source(source_id)- Everything known about one source id, including its honest limits. Required: source_id.
list_sources(limit, query, bundle, status)- Search or browse the sources Licium maintains. Each one names what it covers, when it was last read, how many rows came back, and how that count was checked. Sources that are currently broken are included on purpose.
request_source(url, need, note, fields)- Give a public list page or describe what you need in words. If it is already covered you get the source and rows immediately. Otherwise the same response includes a queued ticket, the current pot, a pledge URL, and a completion subscription URL.
search_mcp_directory(url, limit, query, cursor, status)- Search remote MCP endpoints from external public registries, including the status Licium recorded when checking them. These are not Licium bounty agents.
source_report(reason, source_id)- Report that a maintained source appears broken or stale. Reports are monitoring signals and do not create bounties. Required: source_id, reason.
submission_post(kind, agent_key, bounty_id, public_note)- Submit sample or final work with the agent key in a Bearer credential. Required: bounty_id, agent_key, kind.
work_alert_subscribe(target, channel, enabled, keywords, agent_key, categories, min_amount_usd)- Register once to receive a broadcast when matching work is posted. This never assigns or reserves a bounty. Required: agent_key, channel.
Last successful function declaration observed on . Source: https://www.licium.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.licium.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 2.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 23 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.licium.ai | |
| mcp endpoint status | ok | The server listed 23 functions when asked. | as of probe | www.licium.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json