MCP server
by joodascode
Track coding accuracy with SlopWatch, an automated reconciliation software for verifying code changes and managing accou
Monitors AI coding claims by tracking what AI says it implemented versus what actually gets changed in your code files. Provides accountability scoring to catch AI lies about code modifications.
SlopWatch is a community-built MCP server published by joodascode that provides AI assistants with tools and capabilities via the Model Context Protocol. Track coding accuracy with SlopWatch, an automated reconciliation software for verifying code changes and managing accou It is categorized under developer tools. This server exposes 3 tools that AI clients can invoke during conversations and coding sessions.
You can install SlopWatch in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
SlopWatch is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
SlopWatch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, SlopWatch benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired SlopWatch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired SlopWatch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired SlopWatch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
SlopWatch is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
SlopWatch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
SlopWatch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
SlopWatch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
SlopWatch is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
showing 1-10 of 65
Stop AI from lying about what it implemented! Track what AI claims vs what it actually does.
✨ Ultra-Minimal Responses - 90% less verbose output
🔄 Combined Tool - Single call instead of 2 separate tools
⚡ Seamless Workflow - Perfect for AI pair programming
🎯 Cursor MCP Compatible - Works seamlessly with Cursor IDE
Ever had AI say "I've added error handling to your function" but it actually didn't? Or claim it "implemented user authentication" when it just added a comment?
SlopWatch catches AI lies in real-time.
Smithery handles hosting, authentication, and updates automatically
For Cursor IDE:
{
"mcpServers": {
"slopwatch": {
"command": "npx",
"args": ["slopwatch-mcp-server"]
}
}
}
Manual Cursor Setup:
Cmd+Shift+J on Mac, Ctrl+Shift+J on Windows)npx slopwatch-mcp-serverFor Claude Desktop:
Add to your claude_desktop_config.json:
{
"mcpServers": {
"slopwatch": {
"command": "npx",
"args": ["slopwatch-mcp-server"]
}
}
}
Global NPM Install:
npm install -g slopwatch-mcp-server
Perfect for when AI implements something and you want to verify it:
// AI implements code, then verifies in ONE call:
slopwatch_claim_and_verify({
claim: "Add input validation to calculateSum function",
originalFileContents: {
"utils/math.js": "function calculateSum(a, b) { return a + b; }"
},
updatedFileContents: {
"utils/math.js": "function calculateSum(a, b) {
if (typeof a !== 'number' || typeof b !== 'number') {
throw new Error('Invalid input');
}
return a + b;
}"
}
});
// Response: "✅ PASSED (87%)"
For when you want to claim before implementing:
// Step 1: Register claim
slopwatch_claim({
claim: "Add error handling to user login",
fileContents: {
"auth.js": "function login(user) { return authenticate(user); }"
}
});
// Response: "Claim ID: abc123"
// Step 2: Verify after implementation
slopwatch_verify({
claimId: "abc123",
updatedFileContents: {
"auth.js": "function login(user) {
try {
return authenticate(user);
} catch (error) {
throw new Error('Login failed');
}
}"
}
});
// Response: "✅ PASSED (92%)"
| Tool | Description | Response |
|---|---|---|
slopwatch_claim_and_verify | ⭐ Recommended - Claim and verify in one call | ✅ PASSED (87%) |
slopwatch_status | Get your accountability stats | Accuracy: 95% (19/20) |
slopwatch_setup_rules | Generate .cursorrules for automatic enforcement | Minimal rules content |
SlopWatch is designed specifically for Cursor IDE and AI pair programming:
1. AI: "I'll add error handling to your function"
2. SlopWatch: Automatically tracks the claim
3. AI: Implements the code
4. SlopWatch: Verifies implementation matches claim
5. Result: ✅ PASSED (92%) or ❌ FAILED (23%)
// AI says: "I'll add rate limiting to your API endpoint"
slopwatch_claim_and_verify({
claim: "Add rate limiting middleware to /api/users endpoint",
originalFileContents: {
"routes/users.js": "app.get('/api/users', (req, res) => { ... })"
},
updatedFileContents: {
"routes/users.js": "const rateLimit = require('express-rate-limit');
const limiter = rateLimit({ windowMs: 15*60*1000, max: 100 });
app.get('/api/users', limiter, (req, res) => { ... })"
}
});
// Result: ✅ PASSED (94%)
// AI claims: "Added responsive design with CSS Grid"
slopwatch_claim_and_verify({
claim: "Make UserCard component responsive using CSS Grid",
originalFileContents: {
"components/UserCard.jsx": "const UserCard = () => <div className="user-card">...</div>"
},
updatedFileContents: {
"components/UserCard.jsx": "const UserCard = () => <div className="user-card grid-responsive">...</div>",
"styles/UserCard.css": ".grid-responsive { display: grid; grid-template-columns: repeat(auto-fit, minmax(300px, 1fr)); gap: 1rem; }"
}
});
// Result: ✅ PASSED (89%)
Track your AI's honesty over time:
slopwatch_status();
// Returns: "Accuracy: 95% (19/20)"
Generate automatic accountability rules:
slopwatch_setup_rules();
This creates a .cursorrules file that automatically enforces SlopWatch verification for all AI implementations.
SlopWatch analyzes:
npm cache clean --force and reinstallEnable detailed logging by setting DEBUG=true in your environment.
We welcome contributions! Please see our Contributing Guide for details.
MIT License - see LICENSE for details.
Made with ❤️ for the Cursor community
Stop AI from lying about what it implemented. Start using SlopWatch today!
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.