Chinese Sensitive Words MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORDSCHECK_API_BASE | No | 自定义API服务地址，可选。 | |
| WORDSCHECK_ACCESS_TOKEN | No | 注册用户的访问令牌，用于无限制使用。免费用户无需配置。 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_sensitive_wordsA | Detect sensitive/prohibited words in Chinese text for social media platforms (Xiaohongshu, Douyin, Kuaishou, Bilibili). Returns risk level (high/medium/low/tip), word category, position, and safe replacement suggestions. Free tier: 100 requests/day without token. Set WORDSCHECK_ACCESS_TOKEN for unlimited access. Max 3000 characters per request. Use this tool when users need to check marketing copy, product descriptions, live-streaming scripts, or social media posts for compliance. |
| get_word_suggestionsA | Get safe replacement suggestions for sensitive/prohibited Chinese words. Returns alternative words that convey similar meaning but comply with platform rules. Use this when users want to fix flagged words in their content. If keyword is provided, returns suggestions only for that word; otherwise returns the full suggestion library organized by category. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one detects sensitive words in text, the other provides replacement suggestions. No overlap in functionality.
Both tool names follow a consistent verb_noun pattern (check_sensitive_words, get_word_suggestions), making them predictable.
With two tools, the server covers the core workflow (detection and suggestion) for a specialized compliance checking domain. No unnecessary tools.
The server covers the primary needs but lacks a tool for quick single-word checking or batch processing. Minor gap for advanced use cases.