slop-detect.com valid

Slop Detector

Score any landing page against the AI-design fingerprint. Deterministic 0–100

For agents: Tool that scores landing pages 0-100 against an AI-design fingerprint, with REST, CLI and MCP interfaces, a pattern catalogue API, and docs.

landing page scoringai design detectionslop detectordesign lintingpattern catalogue

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T03:02:50.524Z. Cached copy · Source on slop-detect.com

# Slop Detector

> Score any landing page against the AI-design fingerprint. Deterministic 0–100
> slop scoring for landing pages, plus an AEO axis that measures whether AI
> engines can read and cite a page. Open source; runs on real Chromium; ships as
> a web app, a CLI, and an MCP server.

Slop Detector inspects a page's live computed styles (and, optionally, its copy)
and returns a weighted, reproducible score. Lower is better: 0 means no
default-template tells were found. It is not a quality verdict. A high score means a
page matches many default-template patterns, not that it is bad.

## Core docs

- [Homepage (markdown twin)](https://slop-detect.com/index.md): What Slop
  Detector measures and how the scan works.
- [Methodology](https://slop-detect.com/docs): How each axis is scored, the
  DESIGN.md system axis, and the REST/CLI/MCP surface in one reference. Markdown
  twin: https://slop-detect.com/docs.md.
- [Brand & identity](https://slop-detect.com/brand): The design system, and the
  dogfood proof that this site passes its own detector.
- [Pattern catalogue (JSON)](https://slop-detect.com/api/patterns): Every design
  and copy pattern, with weights and the current definitions version (`2026.11`). Leaderboard rows stay on the measured 2026.10 corpus.
  Markdown twin: https://slop-detect.com/api/patterns.md.
- [Blog](https://slop-detect.com/blog): research essays on how the score works,
  why fixed detectors decay, 2026.09 four-axis calibration, and AEO for
  engineering teams. Each post has a markdown twin at `/blog/<slug>.md`.

## How it works

- [Web app](https://slop-detect.com): Paste a URL, get a 0–100 score in ~5s via
  Cloudflare Browser Rendering (real headless Chromium).
- [Source on GitHub](https://github.com/ravidsrk/slop-detect): Monorepo with the
  core engine, CLI, web app, and MCP server.
- [AGENTS.md](https://github.com/ravidsrk/slop-detect/blob/main/AGENTS.md):
  instructions for AI coding agents working in or with the repo.

## Tools for agents

- CLI: `npx slop-detect <url>`; add `--aeo` for the AEO axis, `--design-md auto`
  for the system axis, `--fail-on heavy` to gate CI, `--remote` to scan via the
  API with no local browser.
- MCP server `slop-detect-mcp`: tools `scan_page`, `check_aeo`,
  `check_design_system`, `fix_prompt`, `lint_design_md`, `diff_design_md`.

## Axes

- Design slop: fonts/tracking, gradients/glow, layout conventions.
- Copy slop: hedge-y, em-dash-heavy LLM phrasing (optional second axis).
- AEO: AI-crawler access, robots.txt, indexability, markdown twin, llms.txt,
  content-negotiation. Higher is better (inverse of the slop score).
- System: DESIGN.md compliance. Does the page honor its OWN declared design
  system? Relative, per-site; higher is better; reports named drift (undeclared
  fonts, off-palette colors, off-scale radii). Opt in via `designMd` on
  `POST /api/scan`.

## Keep it clean (monitoring)

- [Monitor a domain](https://slop-detect.com/#monitor): `POST /api/watch`
  `{ domain,
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=slop-detect.com · GET /v1/domain/slop-detect.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for slop-detect.com:
1. POST https://agentwebmap.com/v1/sites/slop-detect.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://slop-detect.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/slop-detect.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/slop-detect.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.