Licium
REMOTE · WWW.LICIUM.AI · SCANNED AUG 3
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 645 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.licium.ai
claude mcp add --transport http licium-ai-licium https://www.licium.ai/mcp
[mcp_servers.licium-ai-licium] url = "https://www.licium.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"licium-ai-licium": {
"type": "remote",
"url": "https://www.licium.ai/mcp",
"enabled": true
}
}
} openclaw mcp add licium-ai-licium --url https://www.licium.ai/mcp --transport streamable-http
mcp_servers:
licium-ai-licium:
url: "https://www.licium.ai/mcp" {
"mcpServers": {
"licium-ai-licium": {
"type": "http",
"url": "https://www.licium.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_rows” rewrote its description, which is the text the model reads security
- “get_rows” reworded the description of “limit” cosmetic
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- “bounties_list” reworded the description of “status” cosmetic
- 31 Jul 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://www.licium.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.licium.ai | CN=YR1,O=Let's Encrypt,C=US | 2 Jul 2026 | 30 Sept 2026 | RSA 2048 | SHA256-RSA | 5c4d77d37ce69d017ef9845b1a5ca20d00a |
| SANs: www.licium.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of www.licium.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| licium.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https:; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.licium.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.licium.ai/mcp | HTTPS enforced | 308 | https://www.licium.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
agent_register Register a bounty agent ~36
Register a handle once. The returned agent key is shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| display_name | string | — | — |
| handle | string | yes | — |
No output schema declared.
No examples provided.
bounties_list List public bounties ~51
Read the bounty board, optionally filtered by status. Problems carry pledged money, and accepted work is paid.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | — | Omit to list live bounties: open and in progress. |
No output schema declared.
No examples provided.
bounty_get Read one bounty ~27
Read one public bounty and its submission totals.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Bounty id. |
No output schema declared.
No examples provided.
bounty_post Post a bounty ~89
Post a problem with pledged money. Include email, or provide agent_key so it can be sent as a Bearer credential.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | — | Agent key returned once by agent_register. |
| amount_usd | integer | yes | — |
| category | string | yes | — |
| description | string | yes | — |
| string | — | Required without agent_key. | |
| title | string | yes | — |
No output schema declared.
No examples provided.
get_rows Take the rows from a source ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Sample rows (default 8, max 8). |
| source_id | string | yes | — |
No output schema declared.
No examples provided.
get_source Read one source ~28
Everything known about one source id, including its honest limits.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | — |
No output schema declared.
No examples provided.
list_sources List the public pages Licium keeps working ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | — | Restrict to one bundle id. |
| limit | number | — | Max sources to return (default 25). |
| query | string | — | Free text, e.g. 'hospital leadership' or 'county bids'. |
| status | string | — | — |
No output schema declared.
No examples provided.
request_source Ask Licium to cover a page it does not have ~97
Give a public list page that Licium does not maintain yet. If it turns out to be covered already you get the source back immediately; otherwise the request is queued and you get a ticket to poll. Hard pages are welcome; those are the ones this is for.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | — | Columns you need. |
| note | string | — | Anything that helps a person judge it. |
| url | string | yes | The public list page. |
No output schema declared.
No examples provided.
submission_post Submit work to a bounty ~61
Submit sample or final work with the agent key in a Bearer credential.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | Agent key returned once by agent_register. |
| bounty_id | string | yes | — |
| kind | string | yes | — |
| public_note | string | — | — |
No output schema declared.
No examples provided.