CussCheck

dev.workers.mike-tusa.profanity-apiPublished by profanity-api.mike-tusa.workers.devOfficial publisherv0.3.0Updated Oct 25, 2026

English profanity filter: find and censor swear words, incl. obfuscations. Word list, not AI.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

CussCheck is a remote MCP server that lets an assistant detect English profanity in text and return matched terms, positions and a censored copy.

What you can do
Check text for English profanity and get the matched terms with their positions in the text, plus a censored copy of the same length unless censoring is turned off. The word-list matcher handles obfuscations such as leetspeak, look-alike letters, repeated letters, dotted or spaced letters and hidden characters.
When to use it
Use it when an assistant needs to screen user-generated text, comments or content for English swear words, or to produce a censored version before displaying or storing it. It is a deterministic word-list filter, not an AI classifier, so it suits simple moderation checks rather than nuanced judgment.
Requirements
A remote streamable HTTP endpoint; no local runtime or package is needed. No key is required to use it. An optional Authorization header can carry a free key or a CussCheck Pro license key for higher limits.
Before you install
The optional Authorization header carries a secret key; only supply it if you accept sending it to the remote service. Text submitted for checking is sent to a third-party endpoint. The filter covers English only and is word-list based, so it may miss context or produce false matches.

Installation

In SourceWeft

  1. Open CussCheck in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.mike-tusa.profanity-api%2Fprofanity-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cusscheck": {
      "type": "http",
      "url": "https://profanity-api.mike-tusa.workers.dev/mcp"
    }
  }
}

Tools

1

check_profanity

Find and censor English swear words

Detect English profanity in text (word list with leetspeak, look-alike letters, repeated letters, dotted/spaced letters and hidden characters handled) and return the matched terms, their positions (UTF-16 start/end in your text) and, unless censor is false, a censored copy of the same length. Common innocent words (Scunthorpe, cockpit, Shiite, cumin) are whitelisted; it does not understand context and is English only. Text up to 10240 UTF-8 bytes; it is not stored or logged. matches is capped at 50 here (match_count is the full total). Read-only. Same engine, keys and limits as POST /v1/check.

Parametersdenytextrequiredallowcensor

Version history

2
  1. v0.3.0LatestOct 16, 2026
  2. v0.2.0Oct 15, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.