"browser use" 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
Give AI assistants the context behind client website feedback. Read comments, screenshots, replies, element details, and developer briefs; organize priorities, update statuses, and export feedback from authorized projects. Coding agents with repository access can investigate issues and prepare fixes for review. Connect through Streamable HTTP and browser OAuth using a Simple Commenter account.
Browser support for web features, live from caniuse. From which version, and is it safe to ship?
Hextrap's MCP Connector protects your LLM coding sessions from installing malicious dependencies, typosquats, unpopular packages, and enforces your strict allow and deny lists. No setup means your LLM uses MCP to configure itself to use Hextrap's proxy's automatically, enforcing your firewall rules immediately. Manage your allow and deny lists right from your favorite LLM.
A portable context layer for MCP-speaking AI clients. Connect any client to one endpoint and it boots with your containers — structured context, live work state, and accumulated knowledge — carried across every client you use.
Generate synthetic random user data for testing, demos, and development without using real persona.
Repos indexed with Moxie Docs can use our MCP to let agents fetch codebase conventions, find affected docs from changes, pull outdated docs to update, and identify orphaned docs to keep up to date. Let your agents keep your documentation accurate and updated at all times.
Find the right ToolsMonk tool for a task: 255 free browser-based tools, read-only lookups.
Wavedash docs and workflow guidance for building and publishing browser games.
Directory of APIs, merchants, and tools AI agents can actually use.
Agents report which MCP servers, APIs and CLIs actually worked. Look up before use, report after.
Anonymous public tools for ZacharyR0th. See the published agent boundary before use.
US cups to milliliters, number discarded
Renamed to FactReason. Now published as io.github.factreason/factreason — please use that entry.
What breaks when you upgrade a package, and what to use instead - from official docs.
US fluid ounces to milliliters, number discarded
USD def count, body discarded
What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data.
US quarts to liters, number discarded
US pints to liters, number discarded
