# Slop Patterns (remote · sloppatterns.com)

Checks UI code for AI-default design patterns and gives the fix. By Precious Studio.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `sloppatterns.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns.md), [page](https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns)

## Channel facts

- Endpoint: `https://sloppatterns.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 561 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Slop Patterns MCP server?

Slop Patterns is a hosted endpoint at https://sloppatterns.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-sloppatterns-slop-patterns 'https://sloppatterns.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sloppatterns-slop-patterns": {
      "url": "https://sloppatterns.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sloppatterns-slop-patterns": {
      "type": "http",
      "url": "https://sloppatterns.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sloppatterns-slop-patterns]
url = "https://sloppatterns.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sloppatterns-slop-patterns": {
      "type": "remote",
      "url": "https://sloppatterns.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sloppatterns-slop-patterns --url 'https://sloppatterns.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sloppatterns-slop-patterns:
    url: "https://sloppatterns.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sloppatterns-slop-patterns": {
      "Transport": "http",
      "Url": "https://sloppatterns.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sloppatterns-slop-patterns -t streamable-http -u 'https://sloppatterns.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-sloppatterns-slop-patterns": {
      "type": "http",
      "url": "https://sloppatterns.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `check_design` (~140 tokens)

Check UI code for AI design patterns

Check a snippet of CSS, HTML or JSX against the Slop Patterns library and return every AI design anti-pattern it matches, with the fix for each. Covers the 101 documented patterns that have a mechanical tell. Useful for reviewing generated UI code.

Input parameters:

- `code` (string, required): The CSS, HTML or JSX to check. Paste it whole; partial snippets work but full files are more accurate.
- `shareStats` (boolean): Optional, defaults to false. If true, contribute an anonymous count of WHICH rule codes fired to the public monthly figures at https://sloppatterns.com/#stats. Never sends your code, your URL, or any…

### `list_patterns` (~42 tokens)

List all patterns

List the whole Slop Patterns taxonomy: code, id, name and one-liner for every documented AI design anti-pattern.

Input parameters:

- `track` (string): Optional filter.

### `get_pattern` (~60 tokens)

Get one pattern

Get one full pattern entry by id or code (e.g. "a1" or "the-unchosen-gradient"): what it looks like, why the tools produce it, who it hurts, the fix, sources.

Input parameters:

- `id` (string, required)

### `changelog` (~38 tokens)

Library changelog

The library version, what each release added or changed, and how patterns are versioned. Use it to cite a specific version of Slop Patterns.

### `search_patterns` (~34 tokens)

Search patterns

Plain-language search across the library. "gradient headline" returns A10 Gradient Text Headline.

Input parameters:

- `query` (string, required)

### `report_pattern` (~168 tokens)

Report a new pattern

Report an AI design anti-pattern that is NOT yet in the library, for a design failure seen repeatedly that a search of the library does not find. Reports are reviewed by a human before anything is published, and published entries credit the reporter.

Input parameters:

- `credit` (string): Name or handle to credit if this is published. Optional.
- `description` (string, required): What it looks like and why it is a failure. Two or three sentences.
- `example` (string): A short code or copy snippet showing it. Optional. Do not include anything proprietary.
- `name` (string, required): A short memorable name for the pattern, e.g. "Skeleton That Never Resolves".
- `whereSeen` (string): Product name or URL where you saw it. Optional but makes the report far more useful.

### `why` (~33 tokens)

Why a pattern happens

Return only the causal explanation for one pattern — which model, tool or template default produces it.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72

## Common questions

### What is the Slop Patterns MCP server?

Slop Patterns is an MCP server listed in the public MCP registry as com.sloppatterns/slop-patterns. Checks UI code for AI-default design patterns and gives the fix. By Precious Studio. This page covers its hosted endpoint (https://sloppatterns.com/mcp).

### Is the Slop Patterns MCP server safe to use?

Slop Patterns scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Slop Patterns MCP server expose?

Slop Patterns exposes 7 tools: check_design, list_patterns, get_pattern, changelog, search_patterns, and 2 more. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

### Does the Slop Patterns MCP server require authentication?

No. We connected to Slop Patterns without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Slop Patterns MCP server still maintained?

Slop Patterns is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Slop Patterns MCP server?

VerifyMCP ran 13 checks on Slop Patterns, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://sloppatterns.com/mcp
- Repository: https://github.com/pavithralamahewa/slop-patterns
- Website: https://sloppatterns.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns.json
- HTML version of this page: https://verifymcp.io/servers/com-sloppatterns-slop-patterns/sloppatterns