humanpen-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUMANPEN_API_KEY | Yes | Your HumanPen API key, required to authenticate with the HumanPen API. |
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 |
|---|---|
| humanize_documentA | Rewrite a .docx or .pptx so it reads as human-written and scores lower on AI detectors, keeping meaning, citations, tables and layout. Optionally pass a Turnitin/iThenticate AI report to rewrite only the passages it flagged. If a fresh report still flags the result, run this tool again on the rewritten file with that new report - only the still-flagged passages are touched, and balanced remains the right strategy for the second pass. Saves the result next to the source and returns its path. COSTS CREDITS at 100 per 1,000 words processed (10 minimum) - say so and get agreement first. |
| free_rehumanizeA | Continue a finished humanize job for FREE. Upload a fresh detection report for that job's result; only the passages it still flags are rewritten, at no credit cost. The server enforces strict limits: one free continuation per job, a per-day cap, the report must be of THAT job's own result (>=90% match) and show >=20% AI, and the result must still exist (kept ~7 days). If a limit is not met it returns a clear reason - relay it and stop; do not retry or silently fall back to a paid job. Pass the job_id a prior humanize_document (or check_job) returned. |
| fix_citationsA | Rewrite a .docx's in-text citations and reference list into one target style, leaving the body text alone. Saves the result next to the source and returns its path. COSTS CREDITS at 100 per 1,000 words processed (10 minimum) - say so and get agreement first. |
| condense_documentA | Shorten a .docx to a target word count, keeping meaning, structure and citations. Saves the result next to the source and returns its path. COSTS CREDITS at 100 per 1,000 words processed (10 minimum) - say so and get agreement first. |
| translate_documentB | Translate a document into another language while keeping its layout, tables, images and formulas. Takes .docx, .pdf, .pptx, .xlsx, .epub, .html and .txt. Saves the result next to the source and returns its path. COSTS CREDITS at 100 per 1,000 words processed (10 minimum) - say so and get agreement first. |
| read_detection_reportA | Read a Turnitin or iThenticate AI Writing report PDF: returns the overall AI percentage and the flagged passages. Free - reads the file without starting a job. Pass the same report to humanize_document to rewrite only what was flagged. |
| check_jobA | Look up a job by id, and download its result if it has finished. Use this after a tool returned before the job was done. |
| get_credit_balanceA | How many credits the account has. 1,000 words costs 100 credits, charged on the words actually processed, with a 10-credit minimum per job. Worth checking before a large document. |
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 8 tools
Each tool targets a distinct operation: humanizing, job checking, free continuation, citation fixing, condensing, translating, report reading, and credit balance. Even humanize_document and free_rehumanize are clearly separated by free continuation logic. No ambiguity in purpose.
Tool names follow a consistent verb_noun pattern (e.g., humanize_document, check_job, fix_citations). The only deviation is free_rehumanize, which starts with an adjective rather than a verb, but it is still understandable and not chaotic.
Eight tools is well within the ideal range for a document processing server. Each tool either performs a distinct document transformation, manages job lifecycle, or provides necessary account information, with no extraneous entries.
The server covers the core document processing lifecycle: create jobs (humanize, fix citations, condense, translate), check job status, retrieve results, and even a free continuation path. Minor gaps like listing all jobs or cancelling jobs exist, but agents can work around these using check_job.