Seo Audit

com.deepseoanalysisPublished by deepseoanalysis.comOfficial publisherv1.0.0Updated Oct 24, 2026

Run SEO + AI-visibility (GEO) audits from Claude, Cursor & other AI clients.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server that lets an AI assistant run SEO and AI-visibility (GEO) audits from clients such as Claude or Cursor.

What you can do
  • Run SEO audits on sites or pages from within an AI client.
  • Run AI-visibility (GEO) audits, checking how content appears to AI-driven search.
  • No tool list is published, so the exact actions and inputs are not documented in the provided material.
When to use it
Worth considering when you want an assistant to check search-engine optimization and AI-search visibility for a site without leaving the chat client.
Requirements
A remote MCP endpoint at deepseoanalysis.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested at sign-in. Audit results and any site data you submit go to a third-party service; no tool list is published, so confirm what it can read or change before connecting.

Installation

In SourceWeft

  1. Open Seo Audit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.deepseoanalysis%2Fseo-audit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "seo-audit": {
      "type": "http",
      "url": "https://deepseoanalysis.com/api/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.