io.github.CalBearKen/ls-search
REMOTE · LIANGSEARCH.AIONIQ.AI · SCANNED AUG 21
Disposable private vector search + semantic RAG for AI agents. x402 pay-per-call, no account.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 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.
How do I install the io.github.CalBearKen/ls-search MCP server?
io.github.CalBearKen/ls-search is a hosted endpoint at https://liangsearch.aioniq.ai/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 · liangsearch.aioniq.ai
claude mcp add --transport http calbearken-ls-search 'https://liangsearch.aioniq.ai/mcp'
{
"mcpServers": {
"calbearken-ls-search": {
"url": "https://liangsearch.aioniq.ai/mcp"
}
}
} {
"servers": {
"calbearken-ls-search": {
"type": "http",
"url": "https://liangsearch.aioniq.ai/mcp"
}
}
} [mcp_servers.calbearken-ls-search] url = "https://liangsearch.aioniq.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"calbearken-ls-search": {
"type": "remote",
"url": "https://liangsearch.aioniq.ai/mcp",
"enabled": true
}
}
} openclaw mcp add calbearken-ls-search --url 'https://liangsearch.aioniq.ai/mcp' --transport streamable-http
mcp_servers:
calbearken-ls-search:
url: "https://liangsearch.aioniq.ai/mcp" {
"McpServers": {
"calbearken-ls-search": {
"Transport": "http",
"Url": "https://liangsearch.aioniq.ai/mcp"
}
}
} assistant mcp add calbearken-ls-search -t streamable-http -u 'https://liangsearch.aioniq.ai/mcp'
{
"mcpServers": {
"calbearken-ls-search": {
"type": "http",
"url": "https://liangsearch.aioniq.ai/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.
- 21 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 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
- 10 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Aug 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 7 Aug 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified 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 21 Aug 2026 · Probed https://liangsearch.aioniq.ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of liangsearch.aioniq.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| aioniq.ai. | present | 2371 | 13 | Verified |
| liangsearch.aioniq.ai. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liangsearch.aioniq.ai/mcp | Unreachable | ||
| http (plaintext) | http://liangsearch.aioniq.ai/mcp | HTTPS enforced |
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 →
trace_create_workspace ~148
Create an isolated, disposable (ephemeral) vector-search workspace - your own sandboxed index/namespace for semantic retrieval and RAG. Prepays container time via x402 micropayment (USDC on Base, EIP-3009); no account, no signup. Call without x_payment to get the price + payment terms; with a signed x_payment it returns a one-time capability_token for the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| spend_limit_usd | number | – | Optional cap on total spend incl. extensions |
| ttl_minutes | integer | – | Container minutes to prepay (default 15) |
| x_payment | string | – | Base64 signed x402 payment payload (EIP-3009) |
No output schema declared.
No examples provided.
trace_dispose_workspace ~67
Dispose and permanently delete the workspace and its in-memory vector index/data (zero data retention); returns a cryptographically signed disposal receipt confirming the wipe.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | yes | Workspace id from trace_create_workspace |
| workspace_token | string | yes | Capability token from trace_create_workspace |
No output schema declared.
No examples provided.
trace_get_passage ~67
Retrieve a single stored passage/document/item (content and metadata) from your workspace vector index by item id.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
| workspace_id | string | yes | Workspace id from trace_create_workspace |
| workspace_token | string | yes | Capability token from trace_create_workspace |
No output schema declared.
No examples provided.
trace_get_usage ~66
Get workspace usage and billing status for your disposable vector-search workspace: prepaid time/TTL remaining, total spend, ingest/search counts, and state.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | yes | Workspace id from trace_create_workspace |
| workspace_token | string | yes | Capability token from trace_create_workspace |
No output schema declared.
No examples provided.
trace_ingest_batch ~99
Ingest and index documents, passages or text chunks into your workspace to build the searchable vector/embedding index for semantic search and RAG retrieval. Each document: {name, text OR content_b64, mime?}; supports text and binary (base64) content.
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | – |
| workspace_id | string | yes | Workspace id from trace_create_workspace |
| workspace_token | string | yes | Capability token from trace_create_workspace |
No output schema declared.
No examples provided.
trace_search ~154
Semantic vector search / similarity retrieval (nearest-neighbor, embedding-based) over your private disposable index - the core RAG retrieval call. Supports natural-language text queries, cross-modal text->image, and reverse-image search (image_b64). Returns ranked passages/hits with locators. Provide query OR image_b64.
| Name | Type | Req | Description |
|---|---|---|---|
| families | array | – | visual | text_semantic | raw |
| image_b64 | string | – | Base64 image for reverse-image search |
| k | integer | – | Number of results (default 8) |
| query | string | – | Natural-language query |
| workspace_id | string | yes | Workspace id from trace_create_workspace |
| workspace_token | string | yes | Capability token from trace_create_workspace |
No output schema declared.
No examples provided.
What is the io.github.CalBearKen/ls-search MCP server?
io.github.CalBearKen/ls-search is an MCP server listed in the public MCP registry as io.github.CalBearKen/ls-search. Disposable private vector search + semantic RAG for AI agents. x402 pay-per-call, no account. This page covers its hosted endpoint (https://liangsearch.aioniq.ai/mcp).
Is the io.github.CalBearKen/ls-search MCP server safe to use?
io.github.CalBearKen/ls-search scores 0 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 io.github.CalBearKen/ls-search MCP server expose?
io.github.CalBearKen/ls-search exposes 6 tools: trace_create_workspace, trace_search, trace_ingest_batch, trace_get_passage, trace_get_usage, trace_dispose_workspace. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.
Does the io.github.CalBearKen/ls-search MCP server require authentication?
Its publisher declares no required credentials for io.github.CalBearKen/ls-search. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.CalBearKen/ls-search MCP server still maintained?
io.github.CalBearKen/ls-search has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 7 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.