AI Humanizer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detectD | Detect whether the text is AI-generated.Show to user the task detail url. Extract the taskId field, then concatenate the link in the following format: https://pre-www.text2go.ai/?utm_source=claude_mcp&taskId={taskId} |
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 1 tool
With only one tool named 'detect', there is no possibility of ambiguity or overlap with other tools. The tool's purpose is singular and clearly defined as detecting AI-generated text and providing a specific URL format.
A single tool inherently has perfect naming consistency since there are no other tools to compare against. The name 'detect' follows a clear verb-based pattern appropriate for its function.
One tool is too few for a server named 'AI Humanizer MCP Server', which suggests broader functionality like humanizing or transforming AI text. A single detection tool feels incomplete and under-scoped for the implied domain.
The server's name implies capabilities beyond detection, such as humanizing or modifying AI-generated text, but only a detection tool is provided. This creates a significant gap where agents cannot perform the core 'humanizer' function suggested by the server name.