Lotus — AI Citation Intelligence
REMOTE · LOTUS.CLICON.APP
Measure how AI assistants cite your brand. Returns measured data and ready-to-apply fixes.
Available components
Last scanned (21 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Marketing and SEO
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Schema quality: 837 → 1203 ▼ functional
- The server no longer declares the “experimental” capability functional
- New tool “activate_artifact” functional
- New tool “approve_artifact” functional
- New tool “get_report_data” functional
- New tool “list_artifacts” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 18 Oct 2026 · Probed https://lotus.clicon.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lotus.clicon.app | CN=WR3,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | RSA 2048 | SHA256-RSA | f31086a39b38650d127a1acc40789581 |
| SANs: lotus.clicon.app | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lotus.clicon.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| clicon.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lotus.clicon.app/mcp/ | HTTP error | 404 | |
| http (plaintext) | http://lotus.clicon.app/mcp/ | Inconclusive | 404 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
activate_artifact ~75
Activate an artifact by its ID. The artifact must belong to the authenticated client's domain. Activation makes the artifact live — only one version of a given type can be active at a time. Use when an agent needs to deploy an approved artifact to production.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | – |
No output schema declared.
No examples provided.
analyze_geo ~73
Analyze a domain's visibility across AI-generated answers. Without an API key: returns a limited preview (1/day per IP, 3/week). With a valid API key: returns the full analysis including measured metrics, revenue-at-risk estimates and scenario simulations.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
approve_artifact ~79
Approve an artifact by its ID. The artifact must belong to the authenticated client's domain. Approved artifacts are ready for activation but are not yet live on the site. Use when an agent has reviewed a generated artifact and wants to mark it as ready for deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | – |
No output schema declared.
No examples provided.
generate_share_link ~68
Generate a public report link for the authenticated client and persist it. Returns {report_url, slug}. Use when an agent needs to create a shareable report covering the client's full visibility status: crawler activity, revenue at risk, competitive intelligence and competitors.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_artifact ~82
Return the most recent artifact (llms_txt or json_ld) for the authenticated client: content, version, generated_at and status. Use when an agent needs to read the generated llms.txt or JSON-LD. artifact_type must be "llms_txt" or "json_ld".
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_type | string | yes | – |
No output schema declared.
No examples provided.
get_bleed_model ~64
Return the traffic erosion model for the authenticated client: cascading metrics with their *_source provenance labels, plus the resulting revenue-at-risk calculation. Use when an agent needs to assess the economic impact of losing traffic to AI-generated answers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_bot_activity ~71
Return AI crawler activity for the authenticated client's domain: total hits, breakdown per bot, most recent hits and last-seen per bot. Use when an agent needs to assess how frequently AI crawlers visit a site over the last N days.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
get_citation_verdict ~83
Return the most recent citation score for the authenticated client, along with the measurements from that same week (safe fields only). Raw data — no healthy/critical classification applied. Use when an agent needs to audit how generative engines cite a client: citation rate, average position, sentiment, competitors mentioned and entity fidelity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_competitor_actions ~44
Return pending and completed competitor actions for a domain. Requires a valid API key (pro, growth or agency).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_quick_win_code ~59
Generate ready-to-install code for a quick win, identified by its hash. Only available for structured_data quick wins. Requires a valid API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| hash | string | yes | – |
No output schema declared.
No examples provided.
get_quick_wins ~44
Return pending and applied quick wins for a domain. Requires a valid API key (pro, growth or agency).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_report_data ~79
Return the full report payload for a share link slug owned by the authenticated client. Returns the report even if the share link has expired. Use when an agent needs to read a report it previously generated with generate_share_link, without opening the public URL in a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_artifacts ~133
Return artifacts (llms_txt, json_ld, defense_nodes) for the authenticated client, without their content payload. Optionally filter by exact status (e.g. "pending_review", "approved"). Use status="" to return all statuses. limit caps the number returned (default 20, max 100); the "total" field always reflects the real unfiltered count for the domain. Use when an agent needs to discover which artifact IDs are available before approving or activating a specific one.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
mark_applied ~90
Verify-before-mark: checks that the expected schema is actually present in the live DOM of the site before marking the quick win as applied. Only marks it if the expected @type is found among the schemas detected on the domain (best-effort, fails safe). Requires a valid API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| hash | string | yes | – |
No output schema declared.
No examples provided.
regenerate_artifacts ~76
Regenerate the GEO artifacts (llms_txt, json_ld and supporting schema nodes) for the authenticated client. Respects a 6h cooldown and the daily generation budget. Use when an agent needs to force regeneration after changes to the site or to the competitor/advantage configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_installation ~83
Check live whether llms.txt and JSON-LD are correctly installed on the authenticated client's domain. Returns an overall status (fully_deployed / partially_deployed / not_deployed) plus the detailed result for each artifact. Use when an agent needs to confirm that GEO artifacts are serving correctly on the client's site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Lotus — AI Citation Intelligence MCP server?
Lotus — AI Citation Intelligence is a hosted endpoint at https://lotus.clicon.app/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lotus.clicon.app
claude mcp add --transport http app-clicon-lotus 'https://lotus.clicon.app/mcp/'
What is the Lotus — AI Citation Intelligence MCP server?
Lotus — AI Citation Intelligence is an MCP server listed in the public MCP registry as app.clicon/lotus. Measure how AI assistants cite your brand. Returns measured data and ready-to-apply fixes. This page covers its hosted endpoint (https://lotus.clicon.app/mcp/).
Is the Lotus — AI Citation Intelligence MCP server safe to use?
Lotus — AI Citation Intelligence scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lotus — AI Citation Intelligence MCP server expose?
Lotus — AI Citation Intelligence exposes 16 tools: analyze_geo, get_quick_wins, get_quick_win_code, mark_applied, get_competitor_actions, and 11 more. Their descriptions and schemas cost roughly 1,203 tokens of context every time the server is loaded.
Does the Lotus — AI Citation Intelligence MCP server require authentication?
Its publisher declares that Lotus — AI Citation Intelligence requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Lotus — AI Citation Intelligence MCP server still maintained?
Lotus — AI Citation Intelligence is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.