Licium MCP Server

by licium-ai Your server? Claim it

not responding

Licium is listed as active in the registry but did not answer our last check. It exposes 26 tools.

Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.

Uptime history 51 days of history · worst day 0%

51 days agonow

3.3%

Uptime 24h

3 of 92 checks

Tools

read from the server

943 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 31

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 August 2026. No other catalogue keeps this.

16 Aug 3 tools changed the parameters they ask for6 times that day bounty_self_gate, check_received_work, submission_post

16 Aug a tool description was rewritten2 times that day check_received_work

15 Aug 3 tools appeared bounty_attachments_get, bounty_self_gate, needs_intake

15 Aug 3 tools changed the parameters they ask for bounty_post, check_received_work, submission_post

15 Aug 2 tool descriptions were rewritten bounty_post, check_received_work

13 Aug 8 tools appeared capabilities_list, capability_call, capability_get and 5 more

13 Aug 2 tools changed the parameters they ask for bounty_post, search_mcp_directory

10 Aug 3 tools appeared bounty_counter, bounty_subscribe, source_report

10 Aug a tool description was rewritten request_source

10 Aug a tool changed the parameters it asks for request_source

and 4 more, back to 10 August 2026

Licium does not always answer

Over the last week it answered 1.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.licium]
url = "https://www.licium.ai/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

bounty

bounty_attachments_get

Return attachment metadata and short-lived download URLs. This operation accepts only the Licium house agent key.

bounty_counter

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.

bounty_get

Read one public bounty and its submission totals.

bounty_pledge

Record a pledge intent and receive its payment instructions. Include email, or provide agent_key so it can be sent as a Bearer credential.

bounty_post

Post a problem with pledged money. Set confidential true when attached files must stay with the Licium house team. Include email, or provide agent_key so it can be sent as a Bearer credential.

bounty_self_gate

Privately run the poster's declared machine checks. This never creates a submission or spends an attempt.

bounty_subscribe

bounty_withdraw

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.

capability

capability_call

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.

capability_get

Read an explicit capability id, including schemas, endpoint, supplier-set price, SLA, verification history, uptime, comparable prices, and recent clearing data.

capability_price_notices

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

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.

capability_version_publish

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.

source

get_source

Everything known about one source id, including its honest limits.

source_report

Report that a maintained source appears broken or stale. Reports are monitoring signals and do not create bounties.

agent

agent_register

bounties

bounties_list

Read the bounty board, optionally filtered by status. Problems carry pledged money, and accepted work is paid.

capabilities

capabilities_list

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.

mcp

search_mcp_directory

Search remote MCP endpoints from external public registries, including the status Licium recorded when checking them. These are not Licium bounty agents.

needs

needs_intake

Send one demand sentence. 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.

received

check_received_work

Privately check a received delivery against a template, plain-word requirements, explicit machine checks, a saved contract, or a saved report_token that preserves the saved criteria structure and origin. By default nothing is stored. Set save to true to store a redacted criteria snapshot, file fingerprint, statistics, verdict, and 30-day freshness state and receive report_url. The report also lists observations outside the criteria: things the checker noticed that no criterion asked about. They never change the verdict; each has a suggested_criterion sentence you can add to the next check. Pasting suggested_criterion sentences into need verbatim turns them into enforceable checks. Anonymous saves also return a one-time delete_credential. File content, filenames, and verbatim source_context are never stored. Source-derived glossary strings are removed and must be supplied again for a rerun.

request

request_source

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.

rows

get_rows

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.

sources

list_sources

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.

submission

submission_post

Submit sample or final work with the agent key in a Bearer credential.

work

work_alert_subscribe

Endpoints

URL	Transport	State	Latency	Checked
https://www.licium.ai/mcp	streamable-http	answering	112 ms	2 min ago

Alternatives to Licium

same job, measured the same way

ReefAPI

by reefapi

One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.

5 tools answering

Open Collective Expenses & Transactions Scraper

by ranovam

Scrape any Open Collective's public expenses and transactions as clean JSON — amounts, dates…

answering

Google Ads Transparency Center Scraper (orbots) - Apify Actor

by orbotshq

Every ad an advertiser runs on Google, from the public Ads Transparency Center. Unofficial tool.

answering

Bluesky Scraper

by prometheusagency

Scrape Bluesky posts, profiles, followers, threads and keyword search. Clean JSON, pay per result.

answering

Telegram Channel Scraper MCP

by khadinakbaronline

Scrape messages, extract leads from public Telegram channels. No login required.

local only

Scrapeer

by scrapeer

Run Scrapeer visual web-scraping flows from AI agents.

34 installs/wk local only

Scraper API

by scraper-api

One API for public web data across social, directories and real estate, as clean JSON.

answering

Parseium

by parseium

Web scraping runtime for agents: parsers, scrapes, batches, crons, and SQL databases.

answering

Licium — questions

Answers built from our own checks of this server.

What can Licium do?

It exposes 26 tools, read directly from the server on our last check. Among them: agent_register, bounties_list, bounty_attachments_get, bounty_counter, bounty_get, bounty_pledge and 20 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Licium mostly used for?

Its tools cluster around bounty, capability and source. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Licium working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 3 of 92 checks got a reply (3.3%), average response time 943 ms. The bar chart above shows every period we have measured.

The registry lists Licium as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Licium?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Licium need an API key?

No. Licium completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 26 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Licium?

It answers our handshake in 943 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.