"Web Page Content" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
15 deterministic AI agent and developer tools for code context pruning, token budgeting, hybrid search reranking, self-healing patches, AST analysis, circular dependency detection, root-cause isolation, schema compilation, math/financial solving, critical-path scheduling, A/B testing, memory diffs, API compatibility checks, boundary test generation, and Monte Carlo risk simulation.
**Can AI actually read your page?** ChatGPT, Perplexity, Claude and Google's AI Overviews fetch pages very differently from your browser — no JavaScript, tight timeouts, and a robots.txt rulebook of their own. Lekta fetches a URL exactly the way they do and grades what survives, **A+ to F**. This is the technical half of **AEO** (answer engine optimization) and **GEO** (generative engine optimization): before a model can cite you, it has to be able to fetch you, parse you, and find one sentence worth quoting. **The loop this server was built for:** `Audit https://mysite.com/pricing with Lekta, apply the fixes it lists, audit it again, and show me the difference.` Your agent gets a graded verdict, a ranked fix plan with the exact markup to paste, and a diff that proves the change landed. Repeat until A+. **Four layers, 100 points:** **Access** 25 — do the ~17 AI crawler tokens get past robots.txt? **Indexability** 25 — how much content survives without JavaScript? **Answerability** 30 — is there a single quotable sentence an engine can lift? **Recency** 20 — can a model tell when this page was last true? **What this is not:** a rank tracker. Lekta will not tell you how often ChatGPT mentions your brand. It tells you whether your page can be read and quoted when it does — the part you can actually fix. **No black box.** Every finding cites its basis — an RFC, a vendor doc, or a dated measurement we ran. The engine is versioned with a public changelog: a score never moves without a published shift table. **Tools:** `lekta_audit` (fresh fetch) · `lekta_report` (cached read) · `lekta_fix_plan` (ranked, paste-ready) · `lekta_diff` (before/after) · `lekta_my_sites` Listing tools is open. Tool calls need a free key from lekta.dev/en/panel/api — send `Authorization: Bearer lekta_…` or `x-api-key`. Cached reads, fix plans and diffs cost nothing; only fresh fetches count against the daily limit. **Topics:** AEO · GEO · AI SEO · LLM SEO · answer engine optimization · generative engine optimization · AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) · JavaScript-free indexability · structured data · content freshness
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.
Review frontend code and live pages against 386 quality-gated web development rules.
Web scraping, code review, content gen, sentiment. Zero Core Tools.
Edge MCP Server for live WCAG 2.1 AA accessibility compliance and AST security audits.
Paid AI utility APIs for semantic web comparison, migration safety, code verification, document extraction, security analysis, monitoring, accessibility auditing, and citation research. Accessible through MCP with x402 payments on Base mainnet.
Paid AI utilities for web comparison, code checks, document extraction, security, and research.
Extract declared website CSS color literals and counts without a browser or page text
Read-only smart-contract security intelligence for autonomous agents.
Project memory for coding agents: requirements, decisions, code graph and delivery telemetry.
A paid remote MCP for code graph MCP for AI coding, built to return verdicts, receipts, usage logs,
