Techtenstein Seo

io.github.sathvic-kolluPublished by GitHub account sathvic-kolluv1.0.2Updated Oct 25, 2026

On-page SEO audit for any URL. Titles, meta, headings, links, score, and fix recommendations.

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Local MCP server that runs on-page SEO audits for one URL or up to 20 URLs and returns scores, page metadata and fix recommendations.

What you can do
Audit a single page's on-page SEO and return a score, title, meta description, heading counts, word count, image alt coverage, link counts and recommendations. Audit up to 20 URLs in one batch and compare their SEO scores. Summarize the returned JSON into prioritized fixes or a comparison table.
When to use it
Useful when you want an assistant to check a page or a set of competitor pages for on-page SEO issues and turn the results into concrete fixes, without leaving the chat session.
Requirements
Runs locally via uvx from the PyPI package techtenstein-seo-mcp, configured in the Claude Desktop, Cline or Cursor config. Requires a TECHTENSTEIN_API_KEY environment variable from the provider's API site; a free tier of 100 audits per day is offered, with paid tiers above that. Network access to the audit API.
Before you install
The API key is passed as the TECHTENSTEIN_API_KEY environment variable and stored in the client config file. Audited URLs are sent to the third-party Techtenstein API. Paid tiers cost money; the free tier is limited to 100 audits per day.

Installation

In SourceWeft

  1. Open Techtenstein Seo 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

Techtenstein SEO MCP

MCP server that gives your Claude, Cline, or Cursor session access to on-page SEO audits for any URL. Powered by the Techtenstein SEO Audit API.

Tools exposed

  • seo_audit(url) — Full on-page SEO audit for a single URL
  • seo_batch_audit(urls) — Batch audit up to 20 URLs

Install (Claude Desktop)

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "techtenstein-seo": {      "command": "uvx",      "args": ["techtenstein-seo-mcp"],      "env": {        "TECHTENSTEIN_API_KEY": "your_key_from_techtenstein.com"      }    }  }}

Restart Claude Desktop. seo_audit and seo_batch_audit will appear as available tools.

Install (Cline / VS Code)

Cline auto-detects MCP servers from your Claude Desktop config. Same setup as above works.

Install (Cursor)

Add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "techtenstein-seo": {      "command": "uvx",      "args": ["techtenstein-seo-mcp"],      "env": {"TECHTENSTEIN_API_KEY": "your_key"}    }  }}

Get an API key

Free tier (100 audits/day, no card): https://apis.techtenstein.com

Paid tiers start at $5/month for 5,000 audits.

Example usage

Once installed, ask Claude:

"Run an SEO audit on https://techtenstein.com and tell me the top 3 things to fix."

Claude will call seo_audit, receive the JSON response, and synthesize recommendations.

Or batch:

"Audit these 5 competitor pages and compare their SEO scores: [urls]"

Claude will call seo_batch_audit, receive all 5 results, and produce a comparison table.

Response schema

json
{  "url": "https://example.com",  "seo_score": 84,  "title": {"content": "...", "length": 58, "optimal": true},  "meta_description": {"content": "...", "length": 145},  "headings": {"h1": 1, "h2": 5, "h3": 12},  "word_count": 2367,  "images": {"total": 15, "with_alt": 12, "alt_coverage": 80},  "links": {"internal": 24, "external": 8},  "recommendations": ["...", "..."]}

Support

License

MIT

Source: README.md at commit a44f763

Tools

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

Version history

1
  1. v1.0.2LatestSep 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.