otherapi_key

Copyleaks

Copyleaks provides plagiarism, AI content, image, video, moderation, and writing analysis APIs.

Verdict

Copyleaks lets your team check text for AI authorship, plagiarism, grammar issues, and harmful content without leaving Switchy. @mention it to run synchronous scans on drafts, customer messages, or user-generated content — you get immediate feedback on originality, writing quality, or moderation flags. Writers use it to polish copy before publishing; support teams use it to triage flagged content; compliance teams use it to verify authenticity. Each scan type consumes credits from your Copyleaks account, and the sandbox mode returns mock data by default — set sandbox=false when you need real analysis.

Common use cases

  • Verify blog drafts aren't AI-generated
  • Catch plagiarism in submitted proposals
  • Polish grammar before client emails
  • Flag harmful language in user comments
  • Check cross-language content originality

Integration

Vendor
Copyleaks
Category
other
Auth
API_KEY
Tools
6
Composio slug
copyleaks

Tools

  • Check Writing

    Return grammar, mechanics, structure, word-choice, and readability feedback synchronously. By default this returns fixed sandbox mock output, not feedback on the submitted text; set sandbox=false for real feedback, which may consume credits

  • Detect AI Text

    Classify text as human- or AI-written synchronously. By default this returns fixed sandbox mock output, not analysis of the submitted text; set sandbox=false for real analysis, which may consume AI detection credits.

  • Get AI Text Credit Balance

    Return the connected account's separate AI Text Detector wallet balance.

  • Get Credit Balance

    Return the connected Copyleaks account's general plagiarism and authenticity scan credit balance.

  • Get Supported Metadata

    Return one public Copyleaks capability catalog: OCR languages, AI text file types, cross-language options, plagiarism file types, or writing correction definitions.

  • Moderate Text

    Detect harmful-content labels in text synchronously. By default this returns fixed sandbox mock output, not moderation of the submitted text; set sandbox=false for real moderation, which may consume credits and requires Text Moderation enab

Setup

Setup guide

  1. 11. In Switchy, open Settings and navigate to Integrations. 2. Search for Copyleaks and click Connect. 3. You'll be prompted to paste your Copyleaks API key — find this in your Copyleaks dashboard under API Settings or Account Credentials. 4. Paste the key and click Authorize; Switchy validates the connection by fetching your credit balance. 5. Once connected, open any Project and type '@Copyleaks check this draft for AI content' in a message. 6. The MCP runs the scan and returns results inline — if you see mock output, add 'sandbox=false' to your prompt for real analysis. 7. Check your credit balance anytime by asking '@Copyleaks what's my credit balance' to avoid surprise depletion mid-workflow.

What teammates see: by default, memories from Copyleaks are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Scan Draft for AI

@Copyleaks detect if this text is AI-written, sandbox=false: [paste your draft here]

Grammar Check Email

@Copyleaks check the writing quality of this email, sandbox=false: [paste email text]

Moderate User Comment

@Copyleaks moderate this comment for harmful content, sandbox=false: [paste comment]

Check Credit Balance

@Copyleaks what's my general credit balance and AI text credit balance?

List OCR Languages

@Copyleaks show me the supported OCR languages for plagiarism scans

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@copyleaks check this draft blog post for grammar and readability issues before I publish it to the company site.

Output

Copyleaks identified 3 grammar issues (subject-verb agreement in paragraph 2, comma splice in paragraph 4), 2 word-choice suggestions (replace 'utilize' with 'use', 'facilitate' with 'enable'), and flagged readability concerns in the opening sentence (Flesch score 32, consider shorter clauses). Overall structure is clear with logical paragraph flow. The feedback includes specific line references and severity ratings for each issue.

Notes

This example uses the Check Writing tool with sandbox=false, which consumes account credits. The MCP returns synchronous feedback, so large documents may time out. Requires API_KEY auth with writing-correction scope. Copyleaks does not rewrite text — it flags issues for manual revision.

Prompt

@copyleaks analyze this customer support response to see if it contains any AI-generated content that we should flag internally.

Output

Copyleaks AI Text Detector classified the 240-word response as 87% likely AI-generated, with high confidence on the middle two paragraphs (95% AI probability) and lower confidence on the opening greeting (42% human probability). The tool highlights sentence-level probability scores and notes formulaic phrasing patterns common in GPT-family models. This is a probabilistic classification, not definitive proof of authorship.

Notes

This example uses the Detect AI Text tool with sandbox=false, consuming AI detection credits from a separate wallet balance. The MCP returns synchronous results, so it works well for short texts but may struggle with multi-page documents. Check your AI Text credit balance first using the dedicated balance-check tool.

Prompt

@copyleaks scan our draft privacy policy for harmful content labels before we send it to legal review, and summarize any flags by severity.

Output

Copyleaks content moderation found no high-severity flags in the 1,800-word policy draft. Two medium-severity labels appeared: 'legal jargon density' in Section 4 (may confuse non-expert readers) and 'ambiguous consent language' in Section 7 (could be clearer about opt-out mechanisms). No profanity, hate speech, or violence detected. The tool does not assess legal compliance — it flags readability and tone issues that might harm user trust.

Notes

This example pairs the Moderate Text tool (sandbox=false, consumes credits) with AI reasoning to prioritize findings. Copyleaks moderation focuses on harmful-content labels, not legal accuracy — always route flagged sections to qualified reviewers. The MCP returns label categories and confidence scores, not rewritten text.

Use-case deep-dives

Student essay review workflow

When Copyleaks fits a small tutoring or ed-tech team

A 3-person tutoring startup reviewing 20-30 student essays per week needs AI detection, grammar feedback, and plagiarism checks in one pass. Copyleaks wins here because all three tools run synchronously—no webhook polling, no multi-vendor juggling. The writing feedback tool returns grammar, structure, and readability scores in a single call, and the AI detection runs against the same text without re-uploading. The credit-balance tools let you gate features when wallets run low. Trade-off: if you're only doing grammar checks and already use Grammarly or LanguageTool, Copyleaks is overkill. But if you need the AI-detection layer for academic integrity, this MCP keeps the stack simple. Set sandbox=false in production or you'll get mock output forever.

Content moderation at scale

Why Copyleaks moderation works for low-volume community teams

A 5-person community platform moderating 100-200 user posts per day can use the Moderate Text tool to flag harmful content before human review. The tool returns labels synchronously, so you can block or queue posts in real time without building a webhook listener. The supported-metadata endpoint tells you which harm categories Copyleaks covers, so you know the taxonomy upfront. This works if your volume stays under a few hundred calls per day—Copyleaks charges per scan, and the credit-balance tool lets you monitor burn rate. If you're moderating thousands of posts daily or need multi-language nuance, a dedicated moderation API like Perspective or Hive will scale better and cost less per call. For small teams with mixed content-integrity needs, though, Copyleaks bundles moderation with plagiarism and AI detection under one key.

Freelance writer vetting process

When Copyleaks speeds up freelance writer vetting

A 2-person content agency hiring freelance writers can use the AI Text and Check Writing tools to vet sample submissions in one workflow. A candidate submits a 500-word article; you run AI detection to confirm it's human-written, then pull grammar and readability scores to gauge editing load. Both tools return results in seconds, so you can give feedback on a Zoom call or async in Slack. The credit-balance check keeps you from burning through your wallet on low-quality applicants. This breaks down if you're vetting 50+ writers per month—Copyleaks credits add up fast, and you'd save money with a cheaper grammar API plus spot-check AI detection. But for small agencies hiring 3-5 writers per quarter, the bundled tooling cuts the vetting loop from days to minutes.

Frequently asked

What does the Copyleaks MCP do in Switchy?

It lets your team check text for AI generation, plagiarism, grammar issues, and harmful content without leaving the workspace. You call tools like Detect AI Text or Check Writing from any Switchy prompt, and results appear inline. Useful for content review workflows where you want automated checks before publishing or sharing drafts.

Do I need a Copyleaks account to use this MCP?

Yes. You need a Copyleaks account with an active API key. The MCP uses API_KEY auth, so whoever connects it must paste their key into Switchy's settings. Each scan consumes credits from your Copyleaks balance—check your plan limits before connecting, especially if you run high-volume checks.

Can the Copyleaks MCP scan documents or only plain text?

The tools shown here accept text strings, not file uploads. If you need to scan PDFs or Word docs, you'll either extract the text first or use Copyleaks' web dashboard directly. The MCP is best for quick inline checks on drafts, messages, or snippets your team is already working with in Switchy.

How does this compare to running Copyleaks checks manually?

It's faster for repetitive workflows. Instead of copying text into the Copyleaks site, waiting, then pasting results back, you call a tool in Switchy and get the verdict immediately. The trade-off: you lose the web UI's detailed reports and visualizations. Use the MCP for yes/no decisions; use the dashboard for deep forensics.

Who on the team should connect the Copyleaks MCP?

Whoever owns your Copyleaks subscription and has the API key. That's usually a content lead, compliance manager, or ops person. Once connected, any Switchy user can invoke the tools, but all scans draw from the same credit pool—so set team norms around when to use sandbox mode versus live checks.

More other MCPs

See all other MCPs →

Data last verified 61 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.