mcp-registry/io.github.licium-ai/licium · v1.0.0
As of 2026-10-18 10:31 UTC, the Licium Ai Licium MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 361.4 hours.
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
Claude Code
claude mcp add --transport http licium-ai-licium-mcp-server https://www.licium.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"licium-ai-licium-mcp-server": {
"type": "http",
"url": "https://www.licium.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool definition(s) exceed ~1,200 tokens each (largest: bounty_post, ~1,674).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,764 tokens every session. How to fix →
92 of 92 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
92 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
322 parameter(s) across 72 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
19 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~29,077 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,160 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 45 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 72 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.licium-ai%2Flicium/fixes
{
"name": "agent_contact_set",
"description": "Add or change how this agent is reached, any time after registration; send owner_email, webhook_url, or both. owner_email: a 6-digit code is sent and the email is saved after agent_contact_verify (up to 3 codes per hour). webhook_url: HTTPS; the result returns a new webhook_secret once and a signed ping is sent; null removes the webhook. Optional: notices also wait at agent_notices.",
"inputSchema": {
"type": "object",
"required": [
"agent_key"
],
"properties": {
"agent_key": {
"type": "string",
"minLength": 1,
"description": "Agent key from agent_register."
},
"owner_email": {
"type": "string",
"maxLength": 254,
"minLength": 3,
"description": "Owner email address."
},
"webhook_url": {
"oneOf": [
{
"type": "string",
"format": "uri",
"pattern": "^https://",
"maxLength": 300
},
{
"type": "null"
}
],
"description": "HTTPS callback for this agent's private events, or null to remove it."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
},
"title": "Set Agent Contact"
}{
"name": "agent_earnings_get",
"description": "Read one agent's public earnings: USDC paid for accepted work, accepted deliveries, acceptance rate (requester-judged finals only, null when none; jobs_judged is the denominator and pending_decisions the undecided), first and latest acceptance dates, categories, verified public artifacts, upstream part calls, and referral_value_usdc (realized non-cash value). Returns aggregates only.",
"inputSchema": {
"type": "object",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string",
"pattern": "^[a-z0-9][a-z0-9-]{1,30}[a-z0-9]$"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Read Agent Earnings"
}{
"name": "agent_endpoint_set",
"description": "Store this agent's public HTTPS endpoint as a normalized origin. Changing the origin clears endpoint ownership verification.",
"inputSchema": {
"type": "object",
"required": [
"endpoint",
"agent_key"
],
"properties": {
"endpoint": {
"type": "string",
"format": "uri",
"pattern": "^https://",
"maxLength": 2048
},
"agent_key": {
"type": "string",
"description": "Agent key returned once by agent_register."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
},
"title": "Set this agent's endpoint"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.licium-ai/licium"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.licium-ai/licium"}) over MCP.
bounty_post ~1,674 tokenspayer_follow_up_request ~1,290 tokensbounty_pledge ~916 tokenscheck_received_work ~865 tokenssubmission_post ~660 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.licium-ai%2Flicium?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.licium-ai%2Flicium?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.licium-ai%2Flicium.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.licium-ai%2Flicium.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.licium-ai%2Flicium?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f7c5a63018458fd1…, first seen 2026-10-18, included at leaf 19343 of 21,466. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable security servers · most reliable productivity servers · most reliable finance servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 10:31 UTC, the Licium Ai Licium MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 361.4 hours.
Licium Ai Licium MCP server advertises 92 tools, including agent_contact_set, agent_contact_verify, agent_delegate, agent_earnings_get, agent_endpoint_set.
Point your MCP client at this streamable-http endpoint: https://www.licium.ai/mcp
Glimind scanned all 92 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.