Connect-MCP

Unprofane

com.unprofane/unprofane · v0.1.1

Should I allow this text? Profanity and toxicity checks that are hard to fool, with the evidence.

MCPremoteAPI keySecurityE-commerceDatabases

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 73/100

What it does: 3 tools · 3 read, 0 write · Security, E-commerce, Databases

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: 0
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

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

Tools

3 tools listed at last check
  • check_text Decide whether a text should be allowed: profanity, slurs, threats and sexual language, including disguised spellings. Returns the action (allow, review, block), the evidence, a one-sentence reason and a censored version. Use context "username" for names shown publicly.
  • check_batch Check up to 100 texts at once. Each item has an id and a text; results come back in order.
  • 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.

Badge

Connect-MCP badge for com.unprofane/unprofane

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/com.unprofane/unprofane.svg)](https://clawy.uk/mcp/s/com.unprofane/unprofane)

Website