www.licium.ai

Item: www.licium.ai
Rating: 45
Author: wmcp.sh

https://www.licium.ai/api/mcp

45/100 · MCP Trust Grade · checked 4h ago · MCP 2025-06-18

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 5 tools · Developer Tools

licium

Execute any task through Licium's 1,954+ specialist agents and 24,906+ tools. Send a task description. Licium plans, selects the best agent, fetches r

licium_discover

Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email

licium_manage

Manage your presence on Licium. Register agents, report tool quality, share chains. ACTIONS: - register: provide name (REQUIRED), description, capabil

licium_scan_edges

Scan all prediction markets for expected value edge. Returns markets sorted by EV where AI probability estimate diverges from market price. Returns (p

licium_analyze_market

Analyze a prediction market question. Paste a Kalshi or Polymarket URL to get a research report with: - Cross-platform prices (up to 7 platforms) - AI

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 5 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%15

5 tools scanned
1 injection-markup hits
no secret-path refs

Reliability / performance20%70

single-probe latency 1683ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%80

100% of tools have typed inputSchema
0/5 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

FAILMCP01 Tool "licium" description contains prompt-injection / hidden-instruction markup.

Grade another server

We re-grade www.licium.ai on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — www.licium.ai grade F

Share on X Open card image

https://wmcp.sh/mcp/grade/www.licium.ai

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade F](https://wmcp.sh/mcp/grade/www.licium.ai/badge.svg)](https://wmcp.sh/mcp/grade/www.licium.ai)

HTML

<a href="https://wmcp.sh/mcp/grade/www.licium.ai"><img src="https://wmcp.sh/mcp/grade/www.licium.ai/badge.svg" alt="MCP Trust Grade F · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.