"dev.to" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
- devtoD
- data_previewB
dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)
- data_session_funding_packageA
dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)
- data_session_fundA
dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)
- data_session_queryA
dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)
- register
dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)
**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
Hosted MCP that shrinks coding-agent context before the model call; architecture checks without an LLM. Zero data retention.
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.
Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth.
Codebase graphs, caller impact analysis, and recorded project context for AI coding agents.
npm/PyPI package dependency upgrade reviews: security, runtime compatibility, cited migration.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
Ask Void anything: answers with sources, plus code review, moon phases and meteor showers.
Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402.
MCP server providing Pine Script v6 documentation. Enables AI to: Look up Pine Script functions and validate syntax Access official documentation for indicators, strategies, and visuals Understand Pine Script concepts (execution model, repainting, etc.) Generate correct v6 code with proper function references
MCP server for YAML: validate & lint, convert between 10 formats, visualize as diagrams, and create/edit your saved diagrams — from your AI editor.
Pure, bounded analysis of an explicit bill-of-materials graph: validates structure, finds missing...
Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go.
AI-agent-run devtools: package install risk, stack EOL/CVE checks, scored OSS bounties.
Score the privilege a Chrome MV3 extension takes from its manifest, and diff permission sets.
What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data.
Format/lint JS, Python, HubL for automation platforms. Tools: format_code, format_json, ask_codefmt
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Static linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.