Skip to main content
Glama

Related Servers

Alternatives to fbc-guard

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI assistant check any URL to see how much of a page's main content is present in the raw HTML versus only after JavaScript runs, showing which text blocks, meta fields, canonical tags, JSON-LD and links AI crawlers like GPTBot and ClaudeBot cannot read. It also reports what robots.txt allows for 22 AI bot tokens and how the site responds to each bot's user-agent.
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables users to scan a website, project folder or HTML file for generic AI-generated copy, template design and unfinished details, scoring each finding with file-and-line evidence and a per-page breakdown. It turns the results into phased, step-by-step repair plans that Claude, Cursor and other AI tools can apply, then re-measures the score after each change.
      8
      1,363 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to scan pages and whole sites for SEO and AI-search visibility, generate ready-to-paste fixes and validated structured data, and verify HTML before deploy and live results after — all through stable issue codes so an agent can fix problems one by one and prove they are gone.
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Lets an MCP client check whether an ecommerce store can be read by AI assistants, auditing robots.txt to see which AI search versus training crawlers are blocked and sampling product pages to confirm structured data and facts survive in raw HTML without JavaScript. It can also generate a training-only opt-out robots.txt that leaves answer-engine crawlers allowed, all inside the conversation the user is already in.
      2
      MIT

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly separated by input mode: check_fbc_code analyzes supplied source text, while check_fbc_url fetches a live page and its same-origin scripts. Sharing the same rule set does not create ambiguity because the descriptions make the execution boundary explicit.

    Naming Consistency5/5

    Both names follow the same predictable pattern: check_fbc_ followed by the input type (code or url). The snake_case convention is consistent across the entire server.

    Tool Count4/5

    Two tools is below the typical 3–15 range, but the server has a narrow, single-purpose domain and each tool covers a genuinely distinct workflow. The surface is minimal without being redundant, though it is still on the thin side.

    Completeness5/5

    The server covers both obvious entry points for this domain: pasted source code and deployed URL scanning, including same-origin external scripts. It returns detailed per-rule results, evidence, warnings, and statuses for pass/fail/unknown/not_applicable, with no obvious core checker operation missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues