Username Profanity Skill

What this skill does

Let your agent screen usernames. Call it as an MCP tool to flag inappropriate or profane handles before your app accepts them. 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 Username Profanity Skill — exactly what your agent gets back when it makes the call.

vervekit · usernameprofanitytool call

{
  "username": "b00bs"
}

result

username: b00bs
isProfane: true

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

Sign in to try

Ways to use it

Validate at the edge of your app

Enable Username Profanity so your app can add username profanity to your app before it stores or acts on input — one skill, no separate validation service to run.

A guardrail tool for agents

Over MCP, your model can call usernameprofanity to check an input is real and safe before it takes an action, closing off a common failure mode.

One request from any stack

Call Username Profanity over REST from any backend to add username profanity to your app inline in your pipeline, using the same key as every other skill.

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.

usernameprofanity

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/usernameprofanity

Ask your agent

“Enable Username Profanity and ask your agent to add username profanity to your app.”
“Is this input real and safe to use?”

Username Profanity Skill, answered

How to connect it over MCP or REST.

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

Enable the Username Profanity Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the usernameprofanity 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 username profanity 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 Username Profanity appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Username Profanity 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 Username Profanity is available immediately.

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

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

More Data Validation skills

Browse all skills

Validate at the edge of your app

A guardrail tool for agents

One request from any stack

Username Profanity Skill, answered

Give your software a way to act on the world.

Scaling in production?