Connect Lekta and your agent gets 5 tools, among them lekta_audit, lekta_diff, lekta_fix_plan. It answers at https://lekta.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Audits how AI answer engines read a page and grades it A+ to F across four measured layers.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
lekta_audit | Audits ONE live page for AEO (Answer Engine Optimization), also called GEO (Generative Engine Optimization): whether ChatGPT, Claude, Perplexity, Google AI Overviews and Bing can reach, read, quote and cite it. Fetches the page the way thos Inputs: url |
lekta_diff | Compares the two most recent scorable audits stored for ONE URL and reports the movement: score and grade before → after, which checks improved, which regressed, with both run timestamps. This is the progress meter of the fix loop. USE THIS Inputs: url |
lekta_fix_plan | Turns the most recent STORED audit of a URL into an ordered remediation plan: every failing or warned check as a numbered step, biggest point recovery first, each with its severity, the points that fixing it is expected to regain, and the f Inputs: url |
lekta_my_sites | Lists the sites saved on the authenticated Lekta account: URL, latest authoritative grade and score, when it was last audited, and the recheck interval where a schedule is on. This is account inventory, not a measurement. PARAMETERS: none — |
lekta_report | Runs the same page audit as lekta_audit and returns the whole report as one JSON document instead of Markdown — for programs, not people. Top-level fields: engineVersion, url (as requested), finalUrl, fetchedAt, durationMs, targetState, rob Inputs: url |
Every block below points at https://lekta.dev/mcp. Pick your client and copy.
claude mcp add --transport http lekta https://lekta.dev/mcp
{
"mcpServers": {
"lekta": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://lekta.dev/mcp"]
}
}
}{
"mcpServers": {
"lekta": {
"url": "https://lekta.dev/mcp"
}
}
}{
"servers": {
"lekta": {
"type": "http",
"url": "https://lekta.dev/mcp"
}
}
}{
"context_servers": {
"lekta": {
"url": "https://lekta.dev/mcp"
}
}
}{
"mcpServers": {
"lekta": {
"serverUrl": "https://lekta.dev/mcp"
}
}
}{
"mcpServers": {
"lekta": {
"url": "https://lekta.dev/mcp"
}
}
}name: Lekta
version: 0.0.1
schema: v1
mcpServers:
- name: Lekta
type: streamable-http
url: https://lekta.dev/mcp{
"mcpServers": {
"lekta": {
"httpUrl": "https://lekta.dev/mcp"
}
}
}{
"mcpServers": {
"lekta": {
"type": "http",
"url": "https://lekta.dev/mcp"
}
}
}{
"mcpServers": {
"lekta": {
"url": "https://lekta.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Flekta.dev%2Fmcp&type=streamable_http&id=lekta&name=Lekta
It answered our last check on 19 October 2026 in 419 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by lekta.dev and served from lekta.dev, the vendor's own domain: https://lekta.dev/mcp.
5, as returned by the server's own tools/list on 11 September 2026: lekta_audit, lekta_diff, lekta_fix_plan, lekta_my_sites, lekta_report.
It answered our last check on 19 October 2026 in 419 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://lekta.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.lekta. Endpoint host: lekta.dev. ARD identifier: urn:air:dev.lekta:mcp:lekta.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.