Skip to main content
Glama
kienpt91
by kienpt91

Related Servers

Alternatives to founder-toolkit-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      36 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      17 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      8
      12 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      18
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform instant SEO audits, check robots.txt, sitemaps, and AI crawler access for any URL without API keys.
      MIT

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues