"Overview of HTTP (HyperText Transfer Protocol)" 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
The PostNitro MCP server lets AI assistants and agents — Claude (Desktop, Code, and Cowork), Cursor, ChatGPT, and any other Model Context Protocol client — create carousels, image posts, and videos, manage brand kits, audio tracks, and connected social accounts, and schedule posts directly. Instead of writing REST API calls, you connect the server once and your AI assistant gets ready-made tools covering carousel, image, and video generation, brands, audio, social accounts, and scheduling.
Give an agent a place to put large output. Instead of returning 40k characters of a build log into the conversation, it posts the file to docbin and hands back one short URL. Docs render with syntax highlighting and markdown, every update is a new immutable version, and old links keep working. Six tools for create, read, update, delete, list and search. Works anonymously with no signup, or sign in for permanent docs under your own handle.
20 blogging, brand-voice, copywriting, video and social skill products. 6 of 8 free.
Publish complete HTML artifacts and return a public share URL.
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
Publish articles and notes under your own byline, to a readership of other AI agents.
Official MCP server for UploadKit, the file-uploads platform for developers. Gives Claude Code, Cursor, Windsurf, and Zed first-class knowledge of UploadKit's 40+ open-source React components, Next.js route handler scaffolding, <UploadKitProvider> wiring, BYOS (S3/R2/GCS/B2) configuration, and full-text search across 88+ docs pages. Runs locally via npx — no API key, no telemetry, no config.
Official Viddler MCP: list videos, manage access control, pull proof-of-viewing analytics.
The first commercial implementation of HTTP 402 Payment Required for creator content monetization. AI agents pay $0.0025 per content pull from paywalled creator libraries. Patent-pending micropayment infrastructure — creators get paid automatically.
MCP server for the RPG-Schema.org definition and helping the usage of RPG-Schemas in TTRPG manuals
- ME-QROAuthcom.me-qr.mcp
ME-QR MCP Server brings the full power of the ME-QR platform to your AI agents via the Model Context Protocol (MCP). It allows LLMs to autonomously create, design, and manage QR codes for any type of data without leaving the chat interface.
A Model Context Protocol server for Wix AI tools
Authored design service: one-of-one landing pages, pitch decks, and research-grounded briefs.
AI website builder (Wix/Framer alt). SlateHut MCP over HTTP: tools, schemas. Bearer auth.
Search 286 episodes of product management wisdom from top leaders at Figma, Airbnb, Linear.
