Content Tools

unprofane.com

MCP server that checks text for profanity, slurs, threats, and sexual language, supports batch checks, and provides integration snippets for adding Unprofane to various platforms.

1 endpoint3 known toolsFirst detected October 13, 2026Last detected October 13, 2026

ENDPOINT 1

https://api.unprofane.com/mcp

No auth detected

MCP server metadata

Name: unprofane
Version: 1.0.0

Capabilities

tools

Known tools 3

check_text

Decide whether a text should be allowed: profanity, slurs, threats and sexual language, including disguised spellings.

Inferred read-only

check_batch

Check up to 100 texts at once.

Inferred read-only

get_integration_snippet

A complete, runnable recipe for adding Unprofane to a platform (supabase, clerk, firebase, auth0, better-auth, unity, godot, or plain http) in a language.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.unprofane]
url = "https://api.unprofane.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "unprofane": {
      "type": "http",
      "url": "https://api.unprofane.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: unprofane
Remote MCP URL: https://api.unprofane.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "unprofane": {
      "type": "http",
      "url": "https://api.unprofane.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "unprofane",
  "transport": "streamable-http",
  "url": "https://api.unprofane.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.