mcp-server-serp-title-width
Related Servers
Alternatives to mcp-server-serp-title-width
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceProvides technical SEO tools for AI agents, including structured data generation, meta tag creation, robots.txt validation, and SERP previews, all offline with no API key or account.1820 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceProvides agents with tools to score a page's AI readiness, check which AI crawlers robots.txt blocks, and assess passage citability—all performed locally.27 npm2MIT

cygnix-seoofficial
AlicenseBqualityBmaintenanceEnables users to cluster keyword lists, classify search intent, detect Google Search Console keyword cannibalization, score title tags and meta descriptions for CTR, and generate content briefs, all deterministically and locally from their own pasted data with no API key required. It also flags fixes such as canonical targets and merge actions for competing pages.526 npmMIT- AlicenseAqualityBmaintenanceFree SEO + GEO (AI-search-citation) analysis for AI assistants: full SEO audits, AI-crawler-access checks (GPTBot/ClaudeBot/PerplexityBot), Core Web Vitals, structured data, security headers, mobile, and images. No signup, no API key, nothing sent to any server - runs entirely on the user's machine.1367 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude, ChatGPT, Cursor, and Claude Code to run 25+ specialized SEO checks on any URL, generate XML sitemaps and robots.txt files, extract brand design elements, and audit technical SEO, content quality, mobile responsiveness, and security.MIT
- AlicenseAqualityCmaintenanceEnables local validation of supplied HTML for SEO metadata and JSON-LD structured data, checking titles, meta descriptions, H1s, image alt attributes, and JSON syntax errors.280 npmMIT
TDQS
Scored across 2 tools
The two tools are cleanly separated by input source: measure_titles takes title strings directly, while check_title_files takes file/directory paths and extracts titles itself. There is no realistic scenario where an agent would struggle to pick between them.
Both names follow a verb_noun snake_case pattern (measure_titles, check_title_files). The verbs differ slightly (measure vs check) for what is essentially the same underlying check, but the nouns make the distinction clear.
Two tools is thin in absolute terms but appropriate for this narrow, single-purpose server (pixel-width title auditing). Each tool covers a distinct input mode and neither feels redundant.
The surface covers the two main ways an agent would obtain titles: raw strings and local HTML files, with directory recursion and entity decoding handled. Minor gaps exist (no URL fetching or batch input from a file of plain titles), but agents can work around these by passing strings directly.