Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.
0 this week 54 Trust /100

Last scanned (5 hours ago)

Scores higher than 88% of MCPB servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 696 tokens (~174/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 0
    • Package version: 0.55.0 → 0.55.1 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1
    • Stability: 0.90 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.54.1 → 0.55.0 functional
  • 24 Oct 26 +1
    • Package version: 0.48.0 → 0.54.1 functional
  • 21 Oct 26 +1
    • Package version: 0.54.0 → 0.54.1 functional
  • 20 Oct 26 0
    • Package version: 0.51.0 → 0.54.0 functional
    • Package version: 0.51.0 → 0.53.0 functional
    • Package version: 0.51.0 → 0.52.0 functional
  • 19 Oct 26 +1
    • Stability: 0.67 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.48.0 → 0.51.0 functional
    • Package version: 0.48.0 → 0.50.0 functional
    • Package version: 0.48.0 → 0.49.0 functional
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed mcpb/https://github.com/dcadolph/slop-chop/releases/download/v0.55.1/slop-chop-mcp_0.55.1_linux_amd64.mcpb@0.55.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 4 exposed · ~696 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check ~194

Report the writing tells in text without changing a word. Use it to find where a draft carries the patterns the profile lists, and which ones. Each finding carries the rule that matched, the exact text, its line and column, and the swap the chop tool would make. It also returns a lint score from 0 to 100 measuring how densely those patterns appear. The score is not a reading on who wrote the text and must not be reported as one, and it compares only within one scoring version, which the reply names. Deterministic, free, and local: nothing is uploaded.

NameTypeReqDescription
dialectstring–Spelling variant to enforce: american, british, or off.
presetsnull|array–Built-in preset packs to apply for this call, replacing the server defaults. Call the presets tool for the list.
textstringyesThe text to scan for AI writing tells. Required.
NameTypeReqDescription
findingsnull|arrayyes–
scoreintegeryes–
scoringVersionintegeryes–

No examples provided.

chop ~285

Rewrite text so it reads like a person wrote it instead of an AI. Use it to de-slop or humanize AI-generated text, remove AI tells from a draft, strip em-dashes, or hold writing to a house style. It cuts em-dash splices, semicolon habits, hedging and filler transitions, stock openers such as "In summary", the listicle reflex, and buzzwords such as "delve", "leverage", and "robust". The rules pass is deterministic, free, and runs on this machine with nothing uploaded, so the same input always gives the same output. Markdown code blocks and inline backtick spans are left alone. Returns the cleaned text, the tells it found, the tells it left for you to reword by hand, and the slop score before and after.

NameTypeReqDescription
dialectstring–Spelling variant to enforce: american, british, or off.
model_rewriteboolean–Run the optional model rewrite after the rules pass. Off by default. It needs a provider API key and makes a paid call, so ask for it only when the deterministic clean is not enough.
presetsnull|array–Built-in preset packs to apply for this call, replacing the server defaults. Call the presets tool for the list.
textstringyesThe text to clean. Required.
NameTypeReqDescription
findingsnull|arrayyes–
modelRewritebooleanyes–
remainingnull|arrayyes–
scoreintegeryes–
scoreAfterintegeryes–
scoringVersionintegeryes–
textstringyes–

No examples provided.

drift ~168

Measure a draft against the user's own writing and report where it stops sounding like them. Use it before handing over a draft you wrote for them, or to check whether text matches their voice. It compares sentence rhythm, punctuation habits, and register against the fingerprint the user measured from their own writing, and names each trait that landed outside their range, such as longer sentences or a heavier vocabulary. Drift is not slop: a trait outside the range can be good writing that is not theirs, so nothing is rewritten. It needs a fingerprint, which the user makes by running slop-chop voice fingerprint on their own writing. Deterministic, free, and local.

NameTypeReqDescription
textstringyesThe draft to measure against the user's own writing. Required. Needs a paragraph or more to read anything.
NameTypeReqDescription
driftnull|arrayyes–
readsLikeYoubooleanyes–
traitsintegeryes–

No examples provided.

presets ~49

List the built-in preset packs the chop and check tools accept. A preset overlays extra rules on the standard profile, such as cleaver for the aggressive swaps or plain for turning corporate phrasing into plain English.

Input schema present but exposes no named parameters.

NameTypeReqDescription
presetsnull|arrayyes–

No examples provided.

Install

How do I install the slop-chop MCP server?

slop-chop ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, fd071dc7a4957c48aa0f698becf8380141f1479e96255eec5476925f3d0628f9; the commands to do that are on this page. If it does not match, do not open it.

mcpb · slop-chop-mcp_0.55.1_linux_amd64.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

fd071dc7a4957c48aa0f698becf8380141f1479e96255eec5476925f3d0628f9

macOS / Linux

echo "fd071dc7a4957c48aa0f698becf8380141f1479e96255eec5476925f3d0628f9  slop-chop-mcp_0.55.1_linux_amd64.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\slop-chop-mcp_0.55.1_linux_amd64.mcpb).Hash -eq "fd071dc7a4957c48aa0f698becf8380141f1479e96255eec5476925f3d0628f9"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the slop-chop MCP server?

slop-chop is an MCP server listed in the public MCP registry as io.github.dcadolph/slop-chop. Find and remove the writing patterns a profile lists. Deterministic rules, model rewrite opt-in. This page covers its MCPB bundle (https://github.com/dcadolph/slop-chop/releases/download/v0.55.1/slop-chop-mcp_0.55.1_linux_amd64.mcpb).

Is the slop-chop MCP server safe to use?

slop-chop scores 54 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the slop-chop MCP server expose?

slop-chop exposes 4 tools: check, chop, drift, presets. Their descriptions and schemas cost roughly 696 tokens of context every time the server is loaded.

What licence is the slop-chop MCP server under?

slop-chop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.