Overview
A username moderation API for sign-up forms. Username Profanity Checker works by analyzing the username provided and checking if it is inappropriate or profane. It uses advanced algorithms to analyze the username and return if it is inappropriate or profane.
Live Test Username Profanity Skill Skill →
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as UsernameProfanitySkill. 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.
{
"name": "UsernameProfanitySkill",
"arguments": {
"username": "b00bs"
}
}You do not name the tool yourself; the model picks it. Asking about b00bs in the terms this skill covers is enough for it to reach for UsernameProfanitySkill 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"
}
}
}https://api.vervekit.com/v1/mcpPer-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 |
|---|---|---|
usernameRequired | string | The username to check if it is inappropriate or profane |
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.
{
"status": "ok",
"error": null,
"data": {
"username": "b00bs",
"isProfane": true
}
}
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 |
|---|---|---|---|
username | string | b00bs | The username that was analyzed for profanity |
isProfane | boolean | true | Whether the username contains profane or inappropriate content |
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
- Account Registration Screen
- When visitors submit a signup form, frontend forms check the handle and prompt the user for an alternative if flagged.
- Multiplayer Gamertag Moderation
- Game servers inspect player handles during character creation to reject offensive gamertags before letting players join public lobbies.
- Community Profile Updates
- To stop disruptive members from renaming accounts to slurs, community moderators automatically block profane handle changes across social feeds.
- Event Badge Printing
- Event organizers screen attendee display names before printing badges or rendering leaderboards to prevent objectionable text on public screens.
Other ways to use Username Profanity Skill
Set up Username Profanity 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.
Related
Pages that use this skill:
- Block fake signupsGuides
More in Data Validation: