Profanity Filter Skill

Overview

A profanity and text moderation API. Submit any string with an optional single-character mask, which defaults to an asterisk. The endpoint inspects the content against a list of profane words, swaps matches with the chosen mask character, and reports whether offensive terms appeared. Paid plans also return the total count of filtered words.

Live Test Profanity Filter Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as ProfanityFilterSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "ProfanityFilterSkill",
  "arguments": {
    "text": "This is a sample text that may contain inappropriate words"
  }
}

You do not name the tool yourself; the model picks it. Asking about This is a sample text that may contain inappropriate words in the terms this skill covers is enough for it to reach for ProfanityFilterSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`text`Required	string	The text to filter profanity words from
`mask`Optional	string	The mask to replace the profanity words with. Should be a Single Character (e.g., ) default

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "isProfane": true,
    "filteredText": "Today is so **** hot! Why the **** would anyone go outside?",
    "mask": "*",
    "trimmed": false,
    "profaneWords": 2
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`isProfane`	boolean	`true`	Whether the text contained profanity words
`filteredText`	string	`Today is so ** hot! Why the ** would anyone go outside?`	The text with profanity words replaced by mask characters
`mask`	string	`*`	The mask character used to replace profane words
`trimmed`	boolean	`false`	Whether the text was truncated before filtering (always false)
`profaneWords`Premium	number	`2`	Number of profanity words found and filtered

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Livestream Chat Overlay: Display clean real-time viewer comments on screen by replacing detected profanities with asterisks before rendering video overlays.
E-Commerce Review Sanitization: When shoppers submit product ratings, review pipelines scrub vulgar vocabulary and set the profanity flag before publishing feedback.
Classroom Discussion Boards: Educational platforms screen student forum posts to mask inappropriate terminology automatically across shared school assignment boards.
Support Ticket Sanitization: Flag hostile customer support messages automatically on submission by evaluating incoming complaint bodies for profane language.

Other ways to use Profanity Filter Skill

Set up Profanity Filter Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →