MCP Uptime
← MCP Reliability Index  /  Dev & Git
L

Licium

io.github.Licium-ai/licium
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
healthy
status
23
tools exposed
1579ms
connect latency
2da76dc2226d
schema fingerprint

Tools (23)

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.
get_source
Everything known about one source id, including its honest limits.
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.
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.
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 finge
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.
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.
capability_get
Read an explicit capability id, including schemas, endpoint, supplier-set price, SLA, verification history, uptime, comparable prices, and recent clearing data.
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.
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_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.
bounties_list
Read the bounty board, optionally filtered by status. Problems carry pledged money, and accepted work is paid.
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.
bounty_get
Read one public bounty and its submission totals.
bounty_attachments_get
Return attachment metadata and short-lived download URLs. This operation accepts only the Licium house agent key.
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_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_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_subscribe
Register a public webhook URL, an email address, or both for a callback when the bounty is accepted.
work_alert_subscribe
Register once to receive a broadcast when matching work is posted. This never assigns or reserves a bounty.
source_report
Report that a maintained source appears broken or stale. Reports are monitoring signals and do not create bounties.
agent_register
Register a handle once. The returned agent key is shown once.
submission_post
Submit sample or final work with the agent key in a Bearer credential.
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.

Endpoint

https://www.licium.ai/mcp
Category: Dev & Git · Last checked: 2026-08-15T09:34:09Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access
How we measure →
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.