Seo Web Analysis Mcp Server

io.github.TheNextGenNexusPublished by GitHub account TheNextGenNexusv1.0.1Updated Oct 24, 2026

Run Lighthouse audits, check SSL certificates, detect tech stacks, query WHOIS and DNS records

VerifiedSTDIODesktop onlyWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant run SEO and web diagnostics: Lighthouse audits, PageSpeed Insights, SSL checks, tech-stack detection, WHOIS and DNS.

What you can do
Run performance audits on a URL with Google Lighthouse and fetch Google PageSpeed Insights results for it. Check a domain's SSL certificate details. Identify the technology stack behind a website. Look up WHOIS registration records and DNS records for a domain. Requests are forwarded from the local process to the nexgendata Apify endpoint and results are returned.
When to use it
Useful when you want an assistant to inspect a site's performance, security certificate, underlying technologies or domain registration during SEO, competitor or troubleshooting work, without opening separate audit tools.
Requirements
Runs locally over stdio, typically launched with npx or installed globally with npm, so Node.js is needed. It is a bridge to the nexgendata Apify endpoint, so network access is required. APIFY_TOKEN is listed as required in the manifest but optional in the README; without it the public endpoint is used and rate-limited.
Before you install
APIFY_TOKEN is a secret API credential for Apify; keep it out of shared configs and version control. Tool calls are forwarded to a third-party Apify endpoint, so the URLs and domains you query leave your machine. The README notes the public endpoint is rate-limited, which may cause failures or throttling.

Installation

In SourceWeft

  1. Open Seo Web Analysis Mcp Server 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.

Other MCP clients

Follow the launch instructions in the repository.

README

SEO & Web Analysis MCP Server

Run Lighthouse audits, check SSL certificates, detect tech stacks, query WHOIS and DNS records — powered by nexgendata on Apify.

Quick Start

Using npx (recommended)

bash
npx @nexgendata/seo-web-analysis-mcp-server

Install globally

bash
npm install -g @nexgendata/seo-web-analysis-mcp-server

Configure with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{      "mcpServers": {            "seo-web-analysis-mcp-server": {                  "command": "npx",                  "args": [                        "-y",                        "@nexgendata/seo-web-analysis-mcp-server"                  ],                  "env": {                        "APIFY_TOKEN": "your-apify-token-optional"                  }            }      }}

Configure with Cline

Add the same configuration to your Cline MCP settings.

Available Tools

ToolDescription
run_lighthouse_auditRun a Google Lighthouse performance audit on a URL
get_pagespeed_insightsGet Google PageSpeed Insights for a URL
check_ssl_certificateCheck SSL certificate details for a domain
identify_tech_stackIdentify the technology stack of a website
query_whoisQuery WHOIS records for a domain
query_dns_recordsQuery DNS records for a domain

Environment Variables

VariableRequiredDescription
APIFY_TOKENNoYour Apify API token for authenticated access. Without it, the server uses the public endpoint (rate-limited).

How It Works

This MCP server acts as a local stdio bridge to the nexgendata Apify MCP endpoint. When you call a tool, it forwards the request to Apify and returns the results.

Links

License

MIT

Source: servers/seo-web-analysis-mcp-server/README.md at commit 38fefb7

Tools

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

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.