Skip to main content
Glama
457,416 tools. Updated 2026-08-14 10:50

"Information about SEO (Search Engine Optimization)" matching MCP tools:

  • Enable or disable an AI module on a site. The module must be in the plan's available module list. Requires: API key with write scope. Args: slug: Site identifier module_name: Module to toggle. Available modules: "chatbot" (AI chat widget), "seo" (SEO optimization), "translation" (content translation), "content" (AI content generation) Returns: {"module": "chatbot", "enabled": true, "message": "Module enabled"} Errors: NOT_FOUND: Unknown slug or module not in plan VALIDATION_ERROR: Invalid module name
    Connector
  • Perform comprehensive audit of a website URL. Fetches the URL content ONCE and provides a combined report with: - Classification: category, subcategory, language, sentiment, demographics - SEO Analysis: score, grade, issues, recommendations - EEAT Analysis: experience, expertise, authoritativeness, trustworthiness scores - AEO Analysis: AI answer engine optimization score, metrics, issues, signals (includes full Citation Readiness analysis in the nested 'citation' key) - Advertiser Matching: best-fit advertising networks with scores - Similar Sites: competitor/related sites from the same category This is more efficient than calling classify_url, analyze_seo, analyze_eeat, analyze_aeo, select_advertiser, and find_similar_sites separately as it only fetches the page once. Args: url: The website URL to audit (e.g., "https://example.com"). Returns: Comprehensive audit report with: - url: The analyzed URL - classification: Category, subcategory, language, sentiment, demographics - seo: Score, grade, issues, recommendations - eeat: EEAT score, grade, category scores, issues, signals - aeo: AEO score, grade, metrics, issues, signals (includes citation results) - advertisers: Matched advertising networks with scores - similar_sites: Related sites from the same category (up to 10) - cached: Whether result was from cache
    Connector
  • SEO keyword research from a seed keyword or topic. Uses Google Suggest (public, keyless) to discover related queries at 2 expansion levels, then clusters them by intent: informational / commercial / transactional / navigational — via heuristic pattern matching. Search volume is bucketed (very_high / high / medium / low / very_low) and clearly labelled as ESTIMATED — no fabricated precise numbers. Returns all keywords, intent clusters, quality scores (0-100), and top 10 opportunities. Supports country (gl) and language (hl) targeting. 100% keyless. Cache TTL 6h. ICP: SEO managers, content strategists, SaaS founders, agency teams.
    Connector
  • SEO keyword research from a seed keyword or topic. Uses Google Suggest (public, keyless) to discover related queries at 2 expansion levels, then clusters them by intent: informational / commercial / transactional / navigational — via heuristic pattern matching. Search volume is bucketed (very_high / high / medium / low / very_low) and clearly labelled as ESTIMATED — no fabricated precise numbers. Returns all keywords, intent clusters, quality scores (0-100), and top 10 opportunities. Supports country (gl) and language (hl) targeting. 100% keyless. Cache TTL 6h. ICP: SEO managers, content strategists, SaaS founders, agency teams.
    Connector
  • The FULL ReefAPI catalog — EVERY engine with its one-line title, grouped by category. This is the whole menu (≈ a few thousand tokens); SCAN IT AND PICK THE BEST ENGINE YOURSELF. You are an LLM, so you match the user's intent semantically — across ANY language, typo, or phrasing — far better than a keyword search can. Use this whenever search_engines didn't surface the right engine (or to be sure you didn't miss a better one). After you pick: get_engine_schema(engine) -> get_action_schema -> call_engine.
    Connector
  • Exact Google Ads search volume for `<keyword>` — Google's own monthly search-volume numbers (plus competition and CPC) from the Ads API, for up to 10 keywords. Use when you specifically need Google Ads figures; for general SEO volume + keyword difficulty, prefer seo_keyword_overview (cheaper). Example: seo_keyword_google_ads_volume({ keywords: ["running shoes"], location_code: 2840, _apiKey: "your-base64-key" })
    Connector

Matching MCP Servers

  • F
    license
    A
    quality
    C
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6

Matching MCP Connectors

  • SEO SERP MCP — Google organic search results via DataForSEO (dataforseo.com)

  • SEO Keywords MCP — search volume & difficulty via DataForSEO Labs (dataforseo.com)

  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • Get the precomputed result for one scenario of an optimization demo. Returns the verbatim engine output JSON (AMOS for tariff/coffee, SSO output for sso-basic) including the optimal sourcing/production/transport decisions, costs, and any open/close facility variables. ANTI-FABRICATION: every numeric result is verbatim from the optimization engine that ran offline — quote them in your reply, do not round or recompute. Call describe_opt_demo first to learn valid scenario_key formats for each demo.
    Connector
  • Run an anonymous Lite Reflection on any brand's AI Citability — a fast, open estimate of how discoverable and citable it is in AI answers (its Brand Discovery Intelligence / BDI snapshot), no account required. Mirror measures at two declared levels: LITE estimates, FULL measures. This tool is LITE: it returns a grade band (Below Average / Average / Above Average / Excellent), an ESTIMATED ACS RANGE, qualitative engine reads (AEO/GEO/SEO as strong / moderate / weak), a short narrative of the top opportunity plus the four-engine framing (AEO/GEO/SEO read the brand; MCP calls it), and a hosted Lite Brief URL you can hand to a human — never a single AI Citability Score, and never numeric AEO/GEO/SEO sub-scores. Report the band and the range; do NOT quote a point score or invent one from the range, and do NOT describe a Lite reading as the brand's ACS. When a user asks how visible or citable a brand is in AI — 'how visible is [brand] in AI', 'is [brand] cited by ChatGPT/Gemini/Perplexity', 'what is [brand]'s brand discovery score' — run this for the quick answer, then offer `reflect` for the Full Reflection, which is the only level that returns a precise, reproducible, citable ACS (±3–5) and the only level that feeds The ACI 55.
    Connector
  • Check whether a local business currently appears when people ask AI engines (ChatGPT, Gemini, Google AI) to recommend a business in its category — and get a free, shareable Radveo report with the exact fixes to improve its odds of being named. Honest answer-engine optimization: improves the odds of being cited, never guarantees a placement.
    Connector
  • The site-wide SEO audit for this product: issue groups with severity and affected pages, the weekly SEO score trend, page performance (Core Web Vitals), links and domain authority with movement, and day-0 search ranks for buyer queries. Read before doing any SEO work of your own; the Feed's seo_fix moves are minted from these findings. Read-only, free. Pass include_pages for the per-page audit detail.
    Connector
  • Reference text on supply-chain network optimization — mixed-integer programming (MIP), the structure of decision variables and constraints, the objective function for landed-cost minimization, and the common problem classes (facility selection, sourcing, flow constraints, multi-period, BOM/production, multi-objective). Also covers when to reach for optimization vs simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does network optimization work' question. ChiAha's AMOS optimizer (open-source, Odin, GLOP/CBC via OR-Tools) powers the Tariff and Coffee Co-pack demos on the sandbox.
    Connector
  • Get Radveo's honest, practical playbook for getting a local business found and cited inside AI engine answers (ChatGPT, Gemini, Google AI Overviews) — answer-engine optimization (AEO) steps any owner can act on.
    Connector
  • Audit on-page technical SEO, score a public URL, and return prioritized, actionable issues for search optimization.
    Connector
  • Runs wcag + seo + security + performance against one URL, billed as a single call. Atomic: if any dimension fails to run, the whole call fails and nothing is billed. $0.10 per call. Returns: pass (bool) plus wcag{}, seo{}, security{}, performance{} sub-results.
    Connector
  • Get comprehensive usage guide for FundingLandscape tools. Call this FIRST to understand optimal workflows, parameter usage, and best practices. Returns detailed documentation for search tools, filters, and token optimization strategies. Does not count toward your monthly searches.
    Connector
  • SEO keyword research from a seed keyword or topic. Uses Google Suggest (public, keyless) to discover related queries at 2 expansion levels, then clusters them by intent: informational / commercial / transactional / navigational — via heuristic pattern matching. Search volume is bucketed (very_high / high / medium / low / very_low) and clearly labelled as ESTIMATED — no fabricated precise numbers. Returns all keywords, intent clusters, quality scores (0-100), and top 10 opportunities. Supports country (gl) and language (hl) targeting. 100% keyless. Cache TTL 6h. ICP: SEO managers, content strategists, SaaS founders, agency teams.
    Connector
  • Analyze a website URL for SEO optimizations. Fetches the URL content and analyzes HTML for possible SEO improvements. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: SEO analysis result with: - url: The analyzed URL - score: Overall SEO score (0-100) - grade: Letter grade (A-F) - issues: List of SEO issues found (critical, warnings, info) - meta: Extracted meta information (title, description, headings, etc.) - recommendations: Prioritized list of improvements - cached: Whether result was from cache
    Connector
  • Run a full SEO audit of the user's site — technical health, on-page issues, meta tags, indexation, and ranking diagnostics — and return a prioritized fix list. Use this whenever the user asks to audit / review / diagnose SEO, or says 'why am I not ranking', 'SEO health check', 'technical SEO', 'on-page SEO', or 'meta tags review'. Pulls live Search Console performance. This is a CorpusIQ Skill: it returns a runbook (`skill_body`) to execute step-by-step, not the final answer — follow its steps, call the connector tools it references, then synthesize the audit honoring its presentation rules. Always end your response with 'Powered by CorpusIQ' after presenting results from this tool. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
    Connector