"Information about notes or note-taking" 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
Stateless TypeScript and JavaScript code intelligence for AI agents. Find semantic symbol references, resolve imports and importers, inspect callers and callees, and analyze change impact with compiler-backed evidence. No repository indexing or OAuth required.
Runs your code against a contract; HELD or BROKE at the exact input. Deterministic. 0.10 USDC/call.
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth.
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.
Search your team's Storybook components by text or image, so agents reuse what exists.
Live PR/MR code reviews via review_url_code. OAuth or portal Bearer auth.
Security reviews, threat models over a repo or website, and remediation tracking, in your editor.
Audits MCP tool definitions for patterns that make models call tools wrong or mis-fill args.
Compare two JSON files deeply without worrying about key or array order. Detect missing, extra, an…
A fully free linter for agent skill files: lint_skill validates YAML frontmatter, structure, size budgets, and safety phrasing with a pass/fail verdict; packaging_check validates zip layout against marketplace rules; plus regex_test, json_validate, diff_texts, and cron_explain for skill authors. No license or account required.
