MCP.Market

DraftCheck AI-writing linter MCP server

online · 100% uptime
by kburrus64-max·io.github.kburrus64-max/slopscore·v0.1.1

DraftCheck: flags AI-writing patterns in prose with fix hints. Deterministic linter, not a detector.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed DraftCheck AI-writing linter yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

DraftCheck AI-writing linter tools (3)

write = sends, deletes, buys or posts
  • slop_checkFree

    FREE (up to 5000 chars). Score a draft for AI-writing tells ("AI slop") and list each tell with its location and a fix hint. Use before publishing any text you generated.

  • slop_check_longFree

    PAID $0.002 USDC via x402 (Base). Same as slop_check for texts up to 200000 chars.

  • slop_patternsFree

    FREE. List every AI-writing pattern DraftCheck detects, with a fix hint for each.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 598ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How DraftCheck AI-writing linter compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
230 ms
faster than 59% of 30,031 servers

What its tools let an agent do: 3 read

Install DraftCheck AI-writing linter in Claude Code, Cursor or VS Code

claude mcp add --transport http slopscore https://slopscore-nine.vercel.app/mcp
Add to Cursor

What the publisher says

From the DraftCheck AI-writing linter repository's README, as published. We do not edit it. Read it on GitHub

DraftCheck

Formerly SlopScore. Same product, new name after a naming clash.

Find the patterns that make writing read as AI-generated, and fix them before you publish.

DraftCheck scans text for 20+ habits of machine-written prose: "it's not X, it's Y" contrasts, dramatic one-line closers, "let's dive in" openers, inflated significance ("a pivotal moment"), AI vocabulary ("delve", "seamless", "leverage"), em-dash overuse, bold-label bullet lists, and chatbot leftovers like "I hope this helps!". It returns a 0-100 score and points at every match with a short fix.

It's a linter, not a detector. It doesn't guess who wrote a text. It shows you the specific sentences readers will notice.

  • Web app (free, runs in your browser): https://slopscore-nine.vercel.app
  • Pattern guides with examples: https://slopscore-nine.vercel.app/patterns/

CLI

npx github:kburrus64-max/draftcheck README.md docs/

(Not on npm yet as draftcheck. The unscoped slopscore name on npm belongs to a different project. Install from GitHub: npm i -D github:kburrus64-max/draftcheck. The slopscore CLI bin remains as an alias.)

FAIL  71  Pure slop        docs/launch-post.md
           1: Chatbot residue: "Great question"
           3: Not X, but Y: "this isn't just a tool, it's"
           3: Inflated significance: "marks a pivotal moment"
ok     4  Reads human      docs/install.md

Options:

Code blocks, inline code, front matter, URLs and HTML tags are ignored, so READMEs with examples don't get flagged for their code. Read from stdin with -.

GitHub Action

name: DraftCheck
on:
  pull_request:
    paths: ["**/*.md", "docs/**", "content/**"]
jobs:
  slop:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: kburrus64-max/draftcheck@v1
        with:
          paths: "docs content README.md"
          max: "40"

Each match shows up as an annotation on the changed line. The check fails when a file goes over max.

Agent skill

DraftCheck ships as an Agent Skill for Claude Code, Cursor, Codex and other agents that read SKILL.md files. The skill tells the agent to score its draft, rewrite only the flagged spans, and re-check:

npx skills add kburrus64-max/draftcheck

As a Claude Code plugin (skill plus the hosted MCP server), from inside Claude Code:

/plugin marketplace add kburrus64-max/draftcheck
/plugin install draftcheck@draftcheck

Cursor can load the same repo as a plugin through .cursor-plugin/plugin.json.

Prompt-only writing skills such as humanizer and no-ai-slop tell an agent what to avoid; DraftCheck gives it a deterministic check to run afterwards.

Library

import { analyze, PATTERNS } from "draftcheck";

const r = analyze("Great question! Let's dive in.", { ignoreQuoted: false });
r.score;    // 0-100
r.label;    // "Reads human" | "A little sloppy" | "Sloppy" | "Pure slop"
r.matches;  // [{ id, label, category, start, end, text, hint }]

No dependencies. Works in Node 18+ and the browser.

How scoring works

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

DraftCheck AI-writing linter: common questions

Is DraftCheck AI-writing linter MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the DraftCheck AI-writing linter safety report
How do I install DraftCheck AI-writing linter?
It runs remotely at slopscore-nine.vercel.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does DraftCheck AI-writing linter need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is DraftCheck AI-writing linter maintained?
The last commit was 30 days ago (2026-10-05). The latest release is v0.1.1.
Is DraftCheck AI-writing linter up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does DraftCheck AI-writing linter compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from kburrus64-max →