"Pi Network" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
**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
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.
Scan GitHub-hosted AI skills for vulnerabilities: prompt injection, malware, OWASP LLM Top 10.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected.
Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages.
Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install.
Python identifier charset, value discarded
Python string escape count, input discarded
JSON/YAML, regex, diff, JWT, SQL dialects — the keyless millisecond ops an agent needs mid-task.
Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
PE MZ/PE signature, bytes discarded
Governance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles.
Cloudflare Workers MCP server: code-explainer
Cloudflare Workers MCP server: code-pattern-risk-scanner
Convert docs to agent-readable specs with criteria and constraints. $0.10/convert.
Multi-LLM council: 25+ frontier models in parallel, consensus scoring, verdict-first code review.
295k+ bug-fix patterns with MCP Hub proxy, PII filtering, and code search
