"Audi" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
SEO and AI-search audit for websites, built for Uzbekistan (Uzbek and Russian sites). Checks on-page SEO, technical health (HTTPS, TLS 1.3, HSTS, HTTP/2-3, robots.txt, sitemap, broken links), AI-search readiness (GEO/AEO), speed and Core Web Vitals, content and social tags, and returns concrete fixes plus AI recommendations for title, description and H1 based on real search demand in Uzbekistan. Start an audit with start_audit, then fetch the result with get_audit.
**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
Scan Solidity & Anchor code
Paid OpenAPI audit and API change detection for agents. $0.10 USDC per analysis via x402 on Base.
Audit and repair any public GitHub repo. Free survey; paid source, unified diffs and a pull request.
AI code security audits via x402 USDC: $0.01 scans, $0.50 audits, $5 auto-fixes. SAST/SCA.
Audit Dockerfiles for root users, baked-in secrets, curl-pipe-shell and unpinned base images.
Check npm packages for typosquats, hallucinated names, install scripts and risky new releases.
Audit MCP servers for tool poisoning and shadowing. Scan a remote server by URL or paste its tools.
Detects catastrophic-backtracking (ReDoS) regex risk via AST parsing, with JS-safe rewrites.
Validates cron expressions and finds DST bugs that make jobs silently skip or double-fire.
Audits MCP tool definitions for patterns that make models call tools wrong or mis-fill args.
kube-linter audit for Kubernetes manifests — 63 checks: security, availability, RBAC, network.
Security audit for docker-compose.yml — 25 checks: secrets, privileges, network, volumes, images.
