Slop Patterns MCP server
com.sloppatterns/slop-patternssloppatterns.comstreamable-httpv1.2.1Scanned
Checks UI code for AI-default design patterns and gives the fix. By Precious Studio.
7 tools: 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Slop Patterns MCP server can do
The Slop Patterns MCP server is published by sloppatterns.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: check_design, changelog and report_pattern), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (report_pattern).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 3Claude Code: ask
changelogThe library version, what each release added or changed, and how patterns are versioned.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The library version, what each release added or changed, and how patterns are versioned. Use it to cite a specific version of Slop Patterns.
Annotations the server declares
- title: Library changelog
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_designCheck 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.1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_design" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check UI code for AI design patterns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
report_patternReport 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Report a new pattern
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
get_patternGet one full pattern entry by id or code (e.g.No findings
Why it is in this group
- The name "get_pattern" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one pattern
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_patternsList the whole Slop Patterns taxonomy: code, id, name and one-liner for every documented AI design anti-pattern.No findings
Why it is in this group
- The name "list_patterns" says "list": a word for reading.
Description, as the server wrote it List the whole Slop Patterns taxonomy: code, id, name and one-liner for every documented AI design anti-pattern.
Annotations the server declares
- title: List all patterns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_patternsPlain-language search across the library.No findings
Why it is in this group
- The name "search_patterns" says "search": a word for reading.
Description, as the server wrote it Plain-language search across the library. "gradient headline" returns A10 Gradient Text Headline.
Annotations the server declares
- title: Search patterns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whyReturn only the causal explanation for one pattern — which model, tool or template default produces it.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return only the causal explanation for one pattern — which model, tool or template default produces it.
Annotations the server declares
- title: Why a pattern happens
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://sloppatterns.com/mcp: tools/list returned 7 tools to an anonymous client, including check_design (write), changelog (write), report_pattern (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_design
The server marks "check_design" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http slop-patterns https://sloppatterns.com/mcpclaude mcp add --transport http slop-patterns https://sloppatterns.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__slop-patterns__list_patterns",
"mcp__slop-patterns__get_pattern",
"mcp__slop-patterns__search_patterns",
"mcp__slop-patterns__why"
],
"ask": [
"mcp__slop-patterns__check_design",
"mcp__slop-patterns__changelog",
"mcp__slop-patterns__report_pattern"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as slop-patterns. Review it before you use it.
Capability tags behind 1 rule
- mcp__slop-patterns__report_pattern untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.sloppatterns/slop-patterns/verify?hash=c51fb80d3ca75314a70101d2ad73fb948e6a752bee17575d97e35907db63cf1a" | jq -e '.changed == false'Pinned hash c51fb80d3ca7, from Nov 11, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.sloppatterns/slop-patterns/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.sloppatterns/slop-patterns)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:04 UTC.
Slop Patterns MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Slop Patterns MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Slop Patterns MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Slop Patterns MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Slop Patterns MCP server have?
- 7 tools: 3 write, 4 read. check_design, changelog, report_pattern, list_patterns, get_pattern, search_patterns and why.
Does the Slop Patterns MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Slop Patterns MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Slop Patterns MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.