SEO GEO Intelligence

io.github.atul0016Published by GitHub account atul0016v0.1.1Updated Oct 24, 2026

SEO and AI-answer visibility intelligence for search, content gaps, and GEO actions.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

A local MCP server that gives an assistant SEO and AI-answer visibility intelligence for search, content gaps, and GEO actions.

What you can do
Provides SEO and AI-answer visibility intelligence to an assistant, covering search visibility, content gaps, and GEO (generative engine optimization) actions, per its description. No tool list is published, so the exact operations are not documented here. It runs as a local process on the user's machine over stdio.
When to use it
Consider it if you want an assistant to help analyze search and AI-answer visibility, find content gaps, or plan GEO actions, and you already hold a license for it.
Requirements
Runs locally over stdio, via uvx from the PyPI package or the Docker image. Requires a license key in EARNALL_MCP_LICENSE_KEY, obtained from the vendor's purchase page. Optional variables EARNALL_MCP_ACTIVATION_ID and EARNALL_MCP_LICENSE_API are also read. Desktop only.
Before you install
Requires a paid license key (EARNALL_MCP_LICENSE_KEY) and validates it, likely against a remote endpoint; the optional EARNALL_MCP_LICENSE_API variable can point validation elsewhere. The activation ID is described as a stable per-user/device identifier. No tool list is published, so review what it does before use.

Installation

In SourceWeft

  1. Open SEO GEO Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.