"Cargo Doc" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Keyless docs search so coding agents wire up RoxyAPI: every endpoint, param and SDK call.
CometChat docs search + implementation bundles: add chat, voice, video & moderation to your app.
JSONPad docs, API, SDK and CLI references, and offline checkers for write rules and flows.
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.
**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
MarketCheck API docs for coding assistants: search, endpoint reference, plans. Free, no auth.
UAB Research Computing Docs
Search the SiteGPT documentation: setup, features, API reference, troubleshooting.
Search and read the current MemorySync documentation while writing integration code.
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
Read-only IMBA Agent API docs MCP. No register, deposit, buy, or withdraw.
Write product documentation to share with your whole team, including testable specifications.
Search and read the docs and examples of react-three-fiber, drei, zustand, jotai... from your agent
Fonto (FontoXML) documentation for AI tools. Converts DITA XML to Markdown on demand.
Search and read the StitchAPI docs: search_docs finds relevant sections, get_doc reads a page.
Search the ByJG open source documentation: PHP, DevOps, Helm, JavaScript and AI projects.
The official OpenVidu documentation, per version, for coding agents.
AstroWay API documentation search and endpoint lookup with credit prices. No API key needed.
Agent document workspace with wallet auth. Create, update and share markdown docs. By AutEng.ai
Supply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals.
