Connect-MCP

dev.lekta/lekta

dev.lekta/lekta · v2026.8.0

Audits how AI answer engines read a page and grades it A+ to F across four measured layers.

MCPremoteAPI keyDocuments & PDFMessagingFiles & storage

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 5 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 5 tools · 5 read, 0 write · Messaging, Documents & PDF, Developer tools

Test call lekta_my_sites: needs a key: tool error: Authentication required. Lekta tools need a free API key: create one at https://lekta.dev/en/panel/api and send it with (1,525 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://lekta.dev/mcp

Tools

5 tools listed at last check
  • 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 it, read it and lift answers from it. Fetches the page the way those engines do — a plain HTTP GET as LektaBot, the
  • 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, robotsDisallowsLektaBot, score (0-100, null when the target cou
  • 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 full fix text. Reads storage only and never fetches, so the p
  • 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 to prove a deploy actually moved the number: lekta_audit →
  • 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 — this tool takes no arguments; call it with an empty argumen

Badge

Connect-MCP badge for dev.lekta/lekta

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/dev.lekta/lekta.svg)](https://clawy.uk/mcp/s/dev.lekta/lekta)