MCP server · REST API

Plug Slopcheck into your AI

Your coding agent can pull the effect recipes instead of guessing at liquid glass, and run a full review of the site it just built — then work through the brief on its own.

0 · Get a key

1 · Add the MCP server

Claude Code

claude mcp add --transport http slopcheck https://slopcheck.dev/mcp \
  --header "Authorization: Bearer slop_YOUR_KEY"

Cursor, Windsurf & other clients (mcp.json)

{
  "mcpServers": {
    "slopcheck": {
      "url": "https://slopcheck.dev/mcp",
      "headers": { "Authorization": "Bearer slop_YOUR_KEY" }
    }
  }
}

The recipe tools work without a key — drop the header if you only want those.

2 · Tools

list_recipesFreeAll effect recipes with when-to-use and when-not-to.
get_recipeFreeTested HTML/CSS/JS + React code for one recipe, as markdown.
review_site1 creditStart a full review of a URL. Takes 1–3 minutes.
get_reviewKeyScore, tells, findings and the full redesign brief once ready.

Try asking: “Review my landing page with Slopcheck and apply the brief.”

3 · Or call the REST API

Recipes (public)

curl https://slopcheck.dev/api/v1/recipes
curl https://slopcheck.dev/api/v1/recipes/liquid-glass

Reviews (API key)

curl -X POST https://slopcheck.dev/api/v1/reviews \
  -H "Authorization: Bearer slop_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'
# → 202 { "id": "…", "status": "queued", "reportUrl": "…" }

curl https://slopcheck.dev/api/v1/reviews/REVIEW_ID \
  -H "Authorization: Bearer slop_YOUR_KEY"
# → { "status": "ready", "score": 72, "tells": […], "kit": {…}, "briefMarkdown": "…" }

A failed review gives its credit back. Limit: 20 reviews per hour per key. Each review also has a private web report at reportUrl.