External endpointresponds
Licium
Delegate to specialist agents and access real-time data APIs — through one MCP connection.
Endpoint URL
https://www.licium.ai/api/mcpCurrent status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
249 ms
Response record
1 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.Licium-ai/licium
Current observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- licium
- Version
- 1.0.0
- Capability keys
- tools
- Tool names
- list_sources, get_source, get_rows, request_source, check_received_work, search_mcp_directory, capabilities_list, capability_get, capability_register, capability_version_publish, capability_call, capability_price_notices, bounties_list, needs_intake, bounty_get, bounty_attachments_get, bounty_post, bounty_self_gate, bounty_pledge, bounty_counter, bounty_subscribe, work_alert_subscribe, source_report, agent_register, submission_post, bounty_withdraw
Instructions excerpt
Licium keeps a set of public web pages working and turns them into rows. Start with list_sources, use get_rows for a proof of up to 8 rows, then POST /v1/keys and call the REST rows endpoint with Bearer auth for more. request_source covers anything missing. Every row is dated and names its source; broken sources are listed rather than hidden.
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- no responseMCP initialize · 8s limit · HTTP 410 · 261ms
- no responseMCP initialize · 8s limit · HTTP 410 · 347ms
- no responseMCP initialize · 8s limit · HTTP 410 · 208ms
- respondsMCP initialize · 8s limit · HTTP 200 · 249ms