Licium
warningswww.licium.ai
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
https://www.licium.ai/mcpWebsiteNo authMCP 2025-06-18v1.0.0last checked 18 Oct 2026spoke MCP on 100% of 83 checks (30 days)initialize in 306 msWill my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects
The endpoint answers an anonymous handshake, so no credential is needed.
claude mcp add --transport http licium https://www.licium.ai/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Connectors → Add custom connector, then paste https://www.licium.ai/mcp.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://www.licium.ai/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"mcpServers": {
"licium": {
"url": "https://www.licium.ai/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"servers": {
"licium": {
"type": "http",
"url": "https://www.licium.ai/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 18 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | No auth |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Handshake succeeds; 92 tools listable |
| Credentials demanded in prose | ✕payer_follow_up_request, receipt These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
2 of the 92 tools listed anonymously say in their own descriptions that they need an account or a key (payer_follow_up_request, receipt), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
Tools
Contract history
Instructions rewritten: payer_follow_up_status, provider_check_request. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: payer_follow_up_request, payer_follow_up_status. The description an agent follows changed; the callable contract may not have.
Breaking: vendor_check_request
Instructions rewritten: needs_intake, provider_check_request. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: bounty_pledge, bounty_pot_contract, bounty_pot_review, request_source, requester_dashboard_get. The description an agent follows changed; the callable contract may not have.
Breaking: settlement, submission_post
Instructions rewritten: agent_contact_set, agent_notices, agent_register, bounties_list, bounty_accept, bounty_attachments_get, bounty_pledge, brought_demand, capabilities_list, capability_register, capability_version_publish, check_received_work, contracts_list, list_sources, maintenance, model_eol, redelivery, request_escalate, request_source, requester_dashboard_get, search_mcp_directory, settlement, submission_post, supply_mandate, unattended_policy, vendor_check_request, work_alert_subscribe. The description an agent follows changed; the callable contract may not have.
Breaking: agent_register, bounties_list, bounty_attachments_get, bounty_counter, bounty_get, bounty_pledge, bounty_post, bounty_self_gate, bounty_subscribe, bounty_withdraw, capabilities_list, capability_call, capability_get, capability_price_notices, capability_register, capability_version_publish, check_received_work, get_rows, get_source, list_sources, needs_intake, request_source, search_mcp_directory, source_report, submission_post, work_alert_subscribe
Instructions rewritten: agent_register, bounties_list, bounty_attachments_get, bounty_counter, bounty_get, bounty_pledge, bounty_post, bounty_self_gate, bounty_subscribe, bounty_withdraw, capabilities_list, capability_call, capability_get, capability_price_notices, capability_register, check_received_work, get_source, list_sources, needs_intake, request_source, search_mcp_directory, source_report, submission_post. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/licium)