Username Profanity Screening for AI Agents

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 Screening for AI Agents Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as UsernameProfanityScreeningforAIAgents. 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": "UsernameProfanityScreeningforAIAgents",
  "arguments": {
    "username": "b00bs"
  }
}

You do not name the tool yourself; the model picks it. Asking about b00bs in the terms this source covers is enough for it to reach for UsernameProfanityScreeningforAIAgents on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source 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": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.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.

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.

1
2
3
4
5
6
7
8

{
  "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.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at isProfane: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

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.

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 Screening for AI Agents

Set up Username Profanity Screening for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Data Validation: