SlopWatch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slopwatch_claim_and_verifyC | Register claim and verify implementation in one call - reduces from 2 tool calls to 1 |
| slopwatch_statusB | Get current slop score and statistics |
| slopwatch_setup_rulesC | Generate .cursorrules file with AI accountability enforcement |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: one handles claim registration and verification, another generates configuration files, and the third retrieves status metrics. The descriptions make it easy to differentiate their functions, eliminating any risk of misselection.
All tool names follow a consistent 'slopwatch_verb_noun' pattern (e.g., slopwatch_claim_and_verify, slopwatch_setup_rules, slopwatch_status). This uniformity makes the set predictable and easy to navigate, with no deviations in style or structure.
With 3 tools, the count is slightly low but reasonable for a server focused on AI accountability and slop scoring. Each tool serves a distinct, essential function, though the scope might feel thin if more operations are expected in this domain.
The tools cover core workflows: setup (rules generation), claim handling (registration and verification), and monitoring (status retrieval). Minor gaps might exist, such as tools for updating rules or detailed analytics, but the surface supports basic operations without dead ends.