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

REMOTE · MCP.AYERS.REPAIR · 2 COMPONENTS

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

64 Trust /100

Last scanned (9 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
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 Management20
  • Stability observed for 6 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 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.

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 61

    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 · Probed https://mcp.ayers.repair/lancelot

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ayers.repair CN=Amazon RSA 2048 M01,O=Amazon,C=US 28 Oct 2026 13 May 2027 RSA 2048 SHA256-RSA 5ade1f73e4fc77a7a0036b53324dbf1
SANs: mcp.ayers.repair
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ayers.repair. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
repair. present 39172 8 Verified
ayers.repair. 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
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ayers.repair/lancelot Verified 200
http (plaintext) http://mcp.ayers.repair/lancelot HTTPS enforced
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 is a hosted endpoint at https://mcp.ayers.repair/lancelot, 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 · mcp.ayers.repair

# add to Claude Code
claude mcp add --transport http ayers-software-repair-lancelot 'https://mcp.ayers.repair/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 hosted endpoint (https://mcp.ayers.repair/lancelot).

Is the Lancelot MCP server safe to use?

Lancelot scores 64 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 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.

Does the Lancelot MCP server require authentication?

No. We connected to Lancelot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.