MCP QUEEN
io.github.ajaxhe/lexiang-mcp-server F
DEPRECATED: Please use io.github.tencent-lexiang/lexiang-mcp-server instead.
Dev & Codev1.0.2streamable-httpmcp.lexiang-app.com repository
Grade evidence — probed 2026-07-16 20:46 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 0 / 25 | HTTP 404 in 768ms — no valid initialize result |
| protocol | 0 / 15 | no handshake |
| tooling | 0 / 35 | unreachable — no tooling to assess |
| latency | 0 / 10 | not measurable |
| provenance | 8 / 15 | description present; repository linked; version 1.0.2; namespace io.github.ajaxhe does NOT match remote host (expected *.ajaxhe.github.io) |
Score 8/100 · latency 768ms · — tools · protocol access: unreachable ⓘ
Trust receipt
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | authentication_boundary | observed | Live protocol probe observed auth_state=unreachable. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: unreachable | live_probe |
Machine-readable receipt: /api/trust/io.github.ajaxhe/lexiang-mcp-server.json
Own this server? Embed your grade badge
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/io.github.ajaxhe/lexiang-mcp-server)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-16 20:46 | F | 8 | 768ms |
| 2026-07-13 21:02 | F | 8 | 1650ms |