founder-toolkit-mcp
Related Servers
Alternatives to founder-toolkit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to audit URLs, static build output, raw HTML, and whole sites for SEO issues, returning actionable findings with rule IDs, severities, fixes, selectors, and evidence, plus optional JavaScript rendering and Lighthouse performance checks.4,643 npm2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.373 npm2MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to run read-only technical SEO and AI-search-readiness audits on any URL via GET/HEAD requests. Checks on-page elements like titles, meta descriptions, headings, canonical and Open Graph tags, JSON-LD validity, alt text and link health, plus robots.txt, sitemaps and llms.txt for crawler access.3MIT
- AlicenseAqualityCmaintenanceEnables Claude to run safe, read-only diagnostics against servers and websites — certificate chains and expiry, HTTP status/redirects/security headers, DNS records, email authentication (SPF, DKIM, DMARC, MTA-STS, TLS-RPT) and sitemaps. Every check returns severity-tagged findings with concrete fixes, plus a 0-100 score and A-F grade, without any ability to modify the target.8MIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.182MIT
- AlicenseNot gradedqualityBmaintenanceExposes six tools over stdio that let an agent audit a project or live URL for technical SEO, GEO/AEO, structured data, and CRO issues, analyze marketing copy, and generate llms.txt, schema, programmatic SEO, and launch kit assets, including applying fixes. Runs dependency-free on Python 3.10+.1MIT
TDQS
Scored across 7 tools
Each of the three domains (SEO, MRR lookup, email auth) is clearly separated, and the descriptions explicitly define the relationship between seo_free_audit (broad overview) and seo_check (focused drill-down), as well as mrr_search (find by name) → mrr_startup (fetch by slug/id). The main residual ambiguity is within seo_check, where 12 underlying checkers are folded into one tool with an opaque `tool` parameter, which an agent must parse rather than select between tools.
All names are snake_case with consistent domain-prefix namespacing (seo_*, mrr_*, email_*) followed by a clear noun/verb, e.g. seo_free_audit, mrr_leaderboard, mrr_startup. The convention makes grouping and prediction of tool families obvious.
Seven tools across three domains is well-scoped for a founder toolkit, and the decision to collapse 12 SEO sub-checkers into a single parameterized seo_check tool actively avoids tool explosion. Every tool earns its place with no filler.
The surface covers the read-only lifecycle well: SEO broad audit + focused checks, MRR search/leaderboard/stats/detail, and DNS-based email auth, with sensible handoffs between them. Minor gaps exist (no batch/multi-domain or cross-domain correlation, no historical comparison), but these are workarounds rather than blockers.