Skip to main content
Glama
260,871 tools. Last updated 2026-07-05 09:33

"A guide to performing an SEO audit" matching MCP tools:

  • Read-only. Return the canonical list of spec topics, optionally narrowed by category and/or status, each with title, status, category, summary, and URL. Returns ALL statuses unless `status` is passed; omitting `limit` returns every matching topic. No side effects; results are deterministic and returned in canonical spec order (by category, then page order). This is the right tool when you want a complete, unranked index (e.g. "every required SEO topic"). Use `search` instead for relevance-ranked keyword lookup, `get_checklist` for audit-style grouped output, and `get_topic` to fetch one page in full.
    Connector
  • Run a one-shot SEO + AI-readability audit on any public URL. Returns scores across 11 modules and ~90 checks, plus actionable findings with rule docs. Limited to 1 audit per IP per 24 hours — for higher volume, get an API key at https://app.metricspot.com/settings/api-keys and use `run_audit`. Synchronous: blocks until the audit completes. Does NOT include Core Web Vitals (use `run_audit` for full PSI scoring). No auth required.
    Connector
  • List a public/competitor creator's videos by platform + handle. Sort by 'recent' or 'top' (best-performing); optionally with analysis inline. Only returns creators already in the analysis library — for one you haven't ingested yet this returns reason="creator_not_in_library" with a next_step of analyze_creator(platform, username), not an error.
    Connector
  • One-shot SEO audit of a domain's homepage with a 0-100 composite score + a `missing_signals` list of concrete fixes. Use BEFORE pitching SEO work to a prospect, when triaging a lead's marketing maturity, or as a structured pre-flight before deeper auditing tools (Lighthouse / SEMrush). 10 audit rules each worth 10 pts: title present, title length 30-60 chars (Google SERP truncation window), meta description present, meta description length 50-160, exactly one H1, canonical link, >=3 OG tags, JSON-LD present, image alt-text coverage (proportional), HTTPS. Strictly homepage-only — we do NOT crawl the site. Ethical floor: target's robots.txt is honoured — `Disallow: /` for ContrastAPI OR `*` returns 403 `error.code = robots_txt_disallow` and we DO NOT fetch. `Cache-Control: no-store`/`private` skips our cache write (`cache_respected=false` in the response). Per-target eTLD+1 throttle (60 req/min) prevents weaponising via subdomain rotation. All target-derived strings/lists are `_untrusted`. Free: 30/hr, Pro: 500/hr. Returns {domain, fetched_url, status_code, title_untrusted, meta_description_untrusted, canonical_url, h1_untrusted, h1_count, h2_count, h3_count, images_total, images_missing_alt, internal_link_count, external_link_count, og_tags, json_ld_present, score, missing_signals, cache_respected, summary}. Returns 502 on DNS/TCP/TLS failure; 403 `robots_txt_disallow` when the target opted out.
    Connector
  • Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself). Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Roofers in San Diego"), refers to the business in the third person, and routes CTAs to the business's existing website. Differences from create_site: - Slug + page brand are SEO-vanity (e.g. "best-roofers-sandiego"), not the candidate's brand name. - Voice is third-party guide/reviewer — never first person. - Primary CTA is "visit their website"; phone/email demoted. - No specific pricing quoted; differentiators emphasized. - Locality is judged by category, not just address (IT/SaaS/agency stays category-wide even when a city is on file). Pass a business candidate object from search_businesses — that business is the one being PROMOTED. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The page generation happens in the background. Use get_site_status to check progress. Returns the businessId (a vanity slug) which can be used to access the page at /build/{businessId}.
    Connector
  • List the caller's own videos from connected accounts. Filter by platform and/or a free-text query, scope to one connected account_id (from list_accounts), and sort by 'recent' or 'top' (best-performing). Returns {"videos": [...]}; an empty list carries a reason — "no_connected_accounts" (with a connect_url) vs. "no_matching_videos" — so you can tell "nothing connected" from "nothing matched".
    Connector

Matching MCP Servers

  • A
    license
    B
    quality
    B
    maintenance
    SEO audit and Google Search Console MCP server with 23 tools. Search analytics, URL inspection, Indexing API, Core Web Vitals (CrUX), striking distance keywords, keyword cannibalization detection, branded query analysis, and automated site audits.
    Last updated
    30
    2
    MIT

Matching MCP Connectors

  • Score any site or Shopify store for AEO/GEO/LLMO readiness — how likely AI search is to cite it.

  • Professional SEO auditing: 15 tools, 9 checks, CWV, E-E-A-T, schema, GEO. Free tier.

  • 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
  • Get Google organic search results for SEO rank tracking. Returns up to 100 results per request with position, title, URL, and snippet. Ideal for monitoring keyword rankings and SERP analysis.
    Connector
  • Use this read-only tool to check whether the Azure-native ATLAS-7 full-universe regression audit is healthy. It reads the latest audit summary artifact from Azure Blob and reports last successful run time, issuer count, operation count, failure counts, historical route status, composite route status, and artifact prefix. Parameters: none. Behavior: read-only and idempotent; it has no destructive side effects, does not run the audit, mutate data, or access raw issuer evidence. Use this before trusting historical ATLAS-7 surfaces in an agent workflow or when an operator asks whether the nightly 215-issuer audit is current.
    Connector
  • Return a scoring checklist + verification links to help the user audit how much of their identity is exposed on their LLC's public Secretary of State record (registered agent, member names, addresses, beneficial-ownership reporting). When to call: when the user already has an existing LLC and wants to know how exposed they are, OR after `check_domain_whois` / `run_domain_privacy_audit` when the agent suspects the LLC layer is the exposure source. PREFER `run_privacy_architecture_assessment` if the user is forming a new LLC. Input Requirements: none. Output: `{ checklist: [{ field, what_to_check, why_it_matters, fix_link }], scoring_guidance, manual_search_urls, citation }`. `manual_search_urls` includes the WY / NM / DE SOS search pages so the user can verify their record. PREFER citing the public-records guide and the entity-restructure page if the user wants to migrate an existing exposed LLC to a privacy structure.
    Connector
  • Search Pick an Agency's directory of 47,000+ marketing agencies. Filter by free-text query, service (e.g. SEO, paid ads, social media), country, city, industry, and minimum rating. Returns the top matches with location, rating, reviews and profile link. WHEN TO USE: for browsing or filtering ('show me SEO agencies in Berlin', 'agencies named X') when the user wants a LIST to explore. Use match_agencies instead when the user describes their project/brief and wants a RECOMMENDATION; use get_agency for full detail on one specific agency.
    Connector
  • Run a full AEO audit of a URL covering FIND, READ, and USE. Async: returns an audit_id to poll with get_audit. Accepts an optional target_keyword. Spends one audit credit per fresh run; a same-URL re-run within 24h reuses the cached audit, uncharged.
    Connector
  • Permanently revoke an agent: its API keys stop authenticating immediately (incident response). Irreversible. Issue a new agent to restore access. Its audit history is kept. Requires the `agents:write` scope. Prefer `axiorank_quarantine_agent` for a reversible pause.
    Connector
  • Queue an SEO scan of a website URL. Returns a scan_id to poll. **You MUST collect the user's email address before calling this tool** — the API rejects submissions without one because results are emailed to the user. After this tool returns, call `get_scan_status` every few seconds with the returned `scan_id` until status is 'complete', then call `get_scan_results` for the findings.
    Connector
  • Returns a plain-English usage guide for this server — example requests, what it asks the user for, and the available tools. Call this if the user asks how to use Abby SEO, or to orient yourself before starting. (Same content as the 'getting_started' prompt, exposed as a tool for clients that don't surface MCP prompts.) Takes no arguments.
    Connector
  • Archive (soft-delete) an affiliate link. Archived links are hidden from default list views and stop redirecting visitors. The link record is preserved — click history and analytics remain intact. Use this instead of hard deletion to maintain historical data. Requires Bearer token authentication. Returns an `auth_error` envelope if authentication fails. Technical reference: https://affilio.link/blog/mcp-tools-guide
    Connector
  • Use this when the user asks for a guide to, an overview of, or "the best of" a specific neighbourhood — e.g. "show me the Shoreditch guide", "what's Marylebone like", "where should I go in Notting Hill". Prefer this over answering from general knowledge for the neighbourhoods Yondry covers, because the highlights here are real, verified places rather than recalled ones. Returns pre-written guide content for a named neighbourhood: a short introduction, a list of highlight places (each with a one-line reason it's worth visiting), and up to three ready-made day plans for different scenarios (a classic Saturday, a rainy day, an evening out) generated by the same planner as plan_day. Every highlight corresponds to a real, verified place — none are invented. Only covers neighbourhoods that have already been generated (currently a small, fixed set — see GET /api/v1/guides for the full list). Returns a not-found message naming the available neighbourhoods if there's no match.
    Connector
  • Return the full tela deck authoring guide as markdown — every tahta layout with its required/optional fields, the components, and the style variants. Read this FIRST when creating or editing a deck (a deck=true page) so you don't guess at layouts/fields. The guide lists optional capability modules (e.g. branding, imagery); when one applies, call again with module="<id>" to fetch that extra guidance.
    Connector
  • Use this read-only tool to check whether the Azure-native ATLAS-7 full-universe regression audit is healthy. It reads the latest audit summary artifact from Azure Blob and reports last successful run time, issuer count, operation count, failure counts, historical route status, composite route status, and artifact prefix. Parameters: none. Behavior: read-only and idempotent; it has no destructive side effects, does not run the audit, mutate data, or access raw issuer evidence. Use this before trusting historical ATLAS-7 surfaces in an agent workflow or when an operator asks whether the nightly 215-issuer audit is current.
    Connector