Profanity Filter Skill

What this skill does

Let your agent clean text. Call it as an MCP tool to detect and mask profanity before your app displays user content. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Profanity Filter Skill — exactly what your agent gets back when it makes the call.

vervekit · profanityfiltertool call

{
  "text": "Today is so damn hot! Why the hell would anyone go outside?",
  "mask": "*"
}

result

isProfane: true
filteredText: Today is so **** hot! Why the **** would…
mask: *
trimmed: false
profaneWords: 2

Run it with your own input. Live calls happen in your dashboard, on your key.

Sign in to try

Ways to use it

Text tooling without the ML stack

Enable Profanity Filter and your app can add profanity filter to your app — translate, analyze, clean — without hosting a model or wiring a language API.

A tool your agent invokes

Over MCP, profanityfilter is the tool your model calls to process text mid-task, on the same connection as every other skill.

Batch it from your backend

Call Profanity Filter over REST to add profanity filter to your app across a whole queue of text in your own server-side job.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

profanityfilter

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/profanityfilter

Ask your agent

“Enable Profanity Filter and ask your agent to add profanity filter to your app.”
“Clean this text up and tell me what's in it.”

Profanity Filter Skill, answered

How to connect it over MCP or REST.

How do I add Profanity Filter to my app or agent?

Enable the Profanity Filter Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the profanityfilter tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add profanity filter to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Profanity Filter appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Profanity Filter call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Profanity Filter is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Profanity Filter is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

More Text Processing skills

Browse all skills

Text tooling without the ML stack

A tool your agent invokes

Batch it from your backend

Profanity Filter Skill, answered

Give your software a way to act on the world.

Scaling in production?