aislopmeter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AISLOPMETER_CHROME | No | If neither Chrome nor Edge is found, set `AISLOPMETER_CHROME` to a browser path, or scan the project folder instead. | |
| AISLOPMETER_REPORT_DIR | No | Reports are written to `~/.aislopmeter/reports/`. Set `AISLOPMETER_REPORT_DIR` to change that. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slop_scanA | Scan a website URL, a local project folder (Next.js, Vite/React, Astro, Vue, Svelte, plain HTML, Markdown content…) or a single .html file for AI slop: generic copy, cliché phrasing, template "vibe-coded" design, placeholder leftovers and missing trust signals. Returns a 0-100 slop score, five category scores and findings ranked by impact, each with evidence, a fix and (for folders) file:line locations to edit. Re-scanning the same target automatically shows a before/after comparison. Prefer scanning the project folder when the user is working on the site's code; scan the URL for live sites. |
| slop_scan_htmlA | Scan raw HTML (for example a page the user pasted, or HTML you generated) for AI slop. Same report as slop_scan. Use slop_scan for URLs and folders. |
| slop_rescue_planA | Turn a scan into a prioritised, site-specific transformation plan: which facts to ask the owner for, quick clean-ups, copy rewrites, a design direction and trust fixes, each tied to findings, file:line locations and an estimated score gain. Follow the plan, then call slop_scan again to measure the change. |
| slop_compareA | Show the before/after difference between two scans: score change, resolved findings, remaining and new ones. |
| slop_reportA | Write the visual HTML report for a scan (a Report screen with the score and findings, and a calm What-to-do screen with a checklist, time estimates and the owner questions) and optionally open it in the user's browser. Use it at the end of a rescue so the user finds the result waiting when they return. Pass open: true only if the user agreed to have it opened. |
| slop_pageA | The full report for a single page of a site scan: its own score, categories and findings, each with steps and a done-when check. Use it to work through a site page by page. |
| slop_fixA | Concrete, step-by-step instructions for one finding of a scan: what to change, the exact file:line places, a before/after example and a "done when" check. Without finding_id it picks the most important open finding and lists the others. Use it to work through a scan one problem at a time. |
| slop_guideA | Read the reference guides behind AI Slop Meter: "criteria" (every check, its threshold and sources), "playbook" (the full rescue method), "copy" (rewriting rules with examples), "design" (how to leave the template look behind), "interview" (questions that get real facts from the owner). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| rescue | Scan a site or project, plan the transformation with the owner, apply it and re-measure until the target score. |
| fix | Scan, fix the single most important finding, re-scan and show what changed. Small, safe steps. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| aislopmeter-criteria | docs: docs/CRITERIA.md |
| aislopmeter-playbook | docs: playbook/RESCUE.md |
| aislopmeter-copy | docs: playbook/COPY.md |
| aislopmeter-design | docs: playbook/DESIGN.md |
| aislopmeter-interview | docs: playbook/INTERVIEW.md |
TDQS
Scored across 8 tools
Most tools target distinct actions: scanning (slop_scan/slop_scan_html), planning (slop_rescue_plan), comparing (slop_compare), guiding (slop_guide) and fixing (slop_fix). The only mild overlap is between slop_report (whole-scan visual report), slop_page (per-page report) and slop_fix (per-finding steps), but the descriptions clearly differentiate scope.
Every tool uses a consistent snake_case 'slop_' prefix with a clear action noun (slop_scan, slop_guide, slop_compare, slop_report, slop_page, slop_fix). The single variant slop_scan_html is a readable, predictable extension of the base verb.
Eight tools is well-scoped for a scan-and-rescue workflow, with each tool covering a distinct stage (scan, guide, plan, compare, report, page, fix). No redundant or filler tools.
The surface covers the full lifecycle: scanning (URL/folder/HTML), reference guides, prioritised planning, comparison, reporting and per-finding fixes, so no obvious dead ends. Minor gap: no explicit scan history or listing tool, though re-scan before/after and slop_compare largely compensate.