Lotus Wisdom
REMOTE · LOTUS-WISDOM-MCP.LINXULE.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Contemplative reasoning with Lotus Sutra wisdom framework and ext-apps visualization.
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 450 tokens (~150/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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 · lotus-wisdom-mcp.linxule.workers.dev
claude mcp add --transport http linxule-lotus-wisdom https://lotus-wisdom-mcp.linxule.workers.dev/mcp
[mcp_servers.linxule-lotus-wisdom] url = "https://lotus-wisdom-mcp.linxule.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"linxule-lotus-wisdom": {
"type": "remote",
"url": "https://lotus-wisdom-mcp.linxule.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add linxule-lotus-wisdom --url https://lotus-wisdom-mcp.linxule.workers.dev/mcp --transport streamable-http
mcp_servers:
linxule-lotus-wisdom:
url: "https://lotus-wisdom-mcp.linxule.workers.dev/mcp" {
"mcpServers": {
"linxule-lotus-wisdom": {
"type": "http",
"url": "https://lotus-wisdom-mcp.linxule.workers.dev/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 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
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://lotus-wisdom-mcp.linxule.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=linxule.workers.dev | CN=WE1,O=Google Trust Services,C=US | 18 Jul 2026 | 16 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 2561e2df933e283113a5fb529fa82ad8 |
| SANs: linxule.workers.dev, *.linxule.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of lotus-wisdom-mcp.linxule.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lotus-wisdom-mcp.linxule.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://lotus-wisdom-mcp.linxule.workers.dev/mcp | Inconclusive | 405 |
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.
lotuswisdom Lotus Wisdom ~279
Contemplative reasoning tool. Use for complex problems needing multi-perspective understanding, contradictions requiring integration, or questions holding their own wisdom. **Workflow:** Always start with tag='begin' (returns framework). Then continue with contemplation tags. Do NOT output wisdom until status='WISDOM_READY'. **Tags:** begin (FIRST - receives framework), then: open/engage/express (process), examine/reflect/verify/refine/complete (meta-cognitive), recognize/transform/integrate/transcend/embody (non-dual), upaya/expedient/direct/gradual/sudden (skillful-means), meditate (pause).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Your contemplation for this step |
| isMeditation | boolean | — | Whether this step is a meditative pause |
| meditationDuration | integer | — | Duration for the meditation pause in seconds (1-10) |
| nextStepNeeded | boolean | — | Whether another step is needed |
| previousJourney | string | — | Pass the journey string from the previous response to maintain journey tracking (e.g. "begin → open → examine"). |
| stepNumber | integer | — | Current step number |
| tag | string | yes | Current processing technique (wisdom-domain tag) |
| totalSteps | integer | — | Estimated total steps needed (adjustable as you go) |
| Name | Type | Req | Description |
|---|---|---|---|
| contemplation | string | — | — |
| currentStep | string | — | — |
| domainJourney | string | — | — |
| duration | number | — | — |
| finalJourney | string | — | — |
| finalStep | string | — | — |
| instruction | string | — | — |
| journey | string | — | — |
| journeyLength | number | — | — |
| nextStepNeeded | boolean | — | — |
| processComplete | boolean | — | — |
| processLength | number | — | — |
| prompt | string | — | — |
| status | string | yes | — |
| stepNumber | number | — | — |
| steps | array | — | — |
| totalSteps | number | — | — |
| welcome | string | — | — |
| wisdomDomain | string | — | — |
No examples provided.
lotuswisdom_summary Lotus Wisdom Journey Summary ~42
Get a summary of the current contemplative journey
| Name | Type | Req | Description |
|---|---|---|---|
| previousJourney | string | — | Pass the journey string from a previous response to reconstruct the current journey summary. |
| Name | Type | Req | Description |
|---|---|---|---|
| domainJourney | string | yes | — |
| journeyLength | number | yes | — |
| status | string | yes | — |
| steps | array | yes | — |
No examples provided.