"Information about SQL (Structured Query Language)" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Indeed job listings by keyword and location, and full postings, as structured JSON.
Amazon keyword search, product details, seller profiles and seller catalogues, as structured JSON.
Yelp business search, place details and the full review feed, as structured JSON.
Yellow Pages local business search and full business listings, as structured JSON.
The public product catalogue and collections of any Shopify storefront, as structured JSON.
Booking.com stays by destination and dates, and full property details, as structured JSON.
Zillow for-sale, for-rent and sold listings, and full property details, as structured JSON.
Google Scholar search results, citation counts and citation export formats, as structured JSON.
Airbnb stays by location and dates, and full listing details, as structured JSON.
Redfin for-sale, for-rent and sold listings plus full property pages, as structured JSON.
Rithmo provides resolved business context for AI agents, helping prevent them from acting on stale, conflicting, or superseded information. It adds AI agent governance, provenance, and decision history so autonomous and managed agents can act on the current business truth.
Ask your AI about your EventSend events, delivery health and usage.
**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
Direct access to 60+ scraping and search tools. Extract structured data from Google (Search, Maps, Trends), Amazon, Airbnb, Social Media, and any web page directly into your AI agent.
OutSend is a B2B prospecting platform exposed as a remote MCP server. Ask your assistant for "1,000 plumbers in Lyon with verified emails" and it runs the whole job on OutSend: extract local businesses by search query and geographic area with a cost and volume estimate before launching, enrich any finished job with emails, social profiles, reviews, tech stack, and email deliverability checks, chain steps into pipelines (extract, enrich, filter, verify) and schedule recurring monitors that rerun
The official Model Context Protocol (MCP) server for RubiConnect — the enterprise platform for RCS (Rich Communication Services) and WhatsApp Business messaging. Connect external AI assistants (such as Claude Desktop, Claude.ai, Cursor, ChatGPT, and autonomous agent pipelines) directly to your RubiConnect messaging workspace to check phone reachability, send rich cards and carousels, trigger bulk campaigns, inspect live inbox conversations, and query messaging analytics.
Screen 2,400+ NSE equities with the Sift query language over 30 years of daily data.
Realtime financial context for AI agents: what changed, who is affected, and what to watch next. One suite covering news, events, guidance, filing changes, sentiment, stakeholders, and alerts. Information-efficient responses with evidence for every result. First-class point-in-time safety for backtests. Pairs well with web search and a market-data API. All data is our own.
Connect Claude, Cursor, and other MCP-compatible coding agents to DevTune AI search visibility data with the Streamable HTTP Model Context Protocol server. DevTune exposes a Model Context Protocol (MCP) server so that AI agents can query your AI search visibility data directly. This lets agents like Codex, Claude, Cursor, and other MCP-compatible tools access your metrics and data directly.
The official Model Context Protocol server for Ambee. It gives any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, VS Code, Ollama, and more direct access to live air quality, pollen, and weather data. To get started, including information on signing up and obtaining your Ambee key, check out the Ambee documentation on https://docs.ambeedata.com
