Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lancelot

NPM · @AYERSELECTRONICS/LANCELOT · 2 COMPONENTS

An MCP server for search and retrieval over a local LanceDB database

+20 this week 83 Trust /100

Last scanned (9 hours ago)

Scores higher than 76% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 72 of 229 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ayers-software-repair/lancelot). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 293 tokens (~73/item across 4 items; 4 tools + 0 resources), lean.Pass
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +26
    • CVE-2023-54404 no longer affects this package ▲ security
    • CVE-2026-0621 no longer affects this package ▲ security
    • CVE-2026-111768 no longer affects this package ▲ security
    • CVE-2026-111771 no longer affects this package ▲ security
    • CVE-2026-111769 no longer affects this package ▲ security
    • GHSA-f897-62hf-6gxq no longer affects this package ▲ security
    • CVE-2026-25536 no longer affects this package ▲ security
    • CVE-2025-66414 no longer affects this package ▲ security
    • CVE-2026-104850 no longer affects this package ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → 0.86 ▲ functional
  • 30 Oct 26 −8
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • CVE-2025-66414 no longer affects this package ▲ security
    • CVE-2023-54404 no longer affects this package ▲ security
    • CVE-2026-25536 no longer affects this package ▲ security
    • CVE-2026-104850 no longer affects this package ▲ security
    • CVE-2026-111768 no longer affects this package ▲ security
    • CVE-2026-111771 no longer affects this package ▲ security
    • CVE-2026-0621 no longer affects this package ▲ security
    • CVE-2026-111769 no longer affects this package ▲ security
    • GHSA-f897-62hf-6gxq no longer affects this package ▲ security
    • Provenance: fail → pass ▲ security
    • Known CVEs: fail → pass ▲ security
    • The attested source repository moved: ayers-software-repair/lancelot security
    • Dependency health: 0.85 → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • MCP protocol: fail → pass ▲ functional
    • Package version: 0.3.1 → 0.3.3 functional
    • Package version: 0.3.1 → 0.3.2 functional
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 48

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@ayerselectronics/lancelot@0.3.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ayers-software-repair/lancelot
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ayers-software-repair/lancelot/.github/workflows/registry.yml@refs/tags/v0.3.3
Rekor log index 3597708560
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6466fe103187abd5319f04685e5f825c15fe0c92d06bccd112434a01098b7c256043abd143edc4bda50acc1bf195a356dd0640ef6906aa03c041a6331

Background: How many MCP packages publish verified provenance →

Dependencies 229 packages
Packages resolved 229
Deprecated 1
Stale 70
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~293 tokens

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 →

Tool Tokens
lancedb_query ~115

RAG query with context retrieval from LanceDB

NameTypeReqDescription
contextBudgetnumber–Maximum characters of context to return (default: the configured budget, 8000)
limitnumber–Maximum number of chunks to retrieve (default: the configured limit, 20; at most 200)
questionstringyesThe user's question
tablestring–Table to query (default: the configured table)
warmStartboolean–Retrieve a general project overview instead of answering the question

No output schema declared.

No examples provided.

lancedb_search ~130

Search LanceDB for relevant documents using vector or text search

NameTypeReqDescription
limitnumber–Maximum number of results (default: the configured limit, 20; at most 200)
querystringyesSearch query string
searchTypestring–vector uses OpenAI embeddings, text matches words in the text column, auto uses vector when a key is set and text otherwise
tablestring–Table to search (default: the configured table)
textColumnstring–Column holding the text
vectorColumnstring–Column holding the vectors

No output schema declared.

No examples provided.

lancedb_status ~31

Get LanceDB status and statistics

NameTypeReqDescription
verboseboolean–Include the column names of each table

No output schema declared.

No examples provided.

lancedb_version ~17

Show Lancelot version information

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Lancelot MCP server?

Lancelot runs locally as an npm package, launched with npx -y @ayerselectronics/lancelot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ayerselectronics/lancelot

# add to Claude Code
claude mcp add ayers-software-repair-lancelot -- npx -y @ayerselectronics/lancelot
Common questions

What is the Lancelot MCP server?

Lancelot is an MCP server listed in the public MCP registry as io.github.ayers-software-repair/lancelot. An MCP server for search and retrieval over a local LanceDB database. This page covers its npm package (@ayerselectronics/lancelot).

Is the Lancelot MCP server safe to use?

Lancelot scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Lancelot MCP server expose?

Lancelot exposes 4 tools: lancedb_search, lancedb_query, lancedb_status, lancedb_version. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.

Is the Lancelot MCP server still maintained?

Lancelot is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Lancelot MCP server under?

Lancelot declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.