com.unprofane/unprofane · v0.1.0 · data-and-databases
Unprofane is healthy: it completed an MCP handshake in 1195 ms and exposes 3 tools. It scores 63/100.
Should I allow this text? Profanity and toxicity checks that are hard to fool, with the evidence.
Endpoint: https://api.unprofane.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 21.2 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 7 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-15T02:36:22.716Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T22:35:47.653Z | Healthy | 1195 |
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. |