Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.humanpen/humanpen-mcp

NPM · HUMANPEN-MCP

Document-level AI humanizer for .docx/.pptx: whole file, selected passages, or flagged text.

Available components

0 this week 83 Trust /100

Last scanned (10 minutes ago)

Scores higher than 72% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1472 tokens (~184/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 4 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 3 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Analysed npm/humanpen-mcp@1.4.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,472 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_job ~85

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.

NameTypeReqDescription
document_pathstring–The original document, so a downloaded result can be named after it
job_idstringyesThe job id an earlier call returned
output_pathstring–Where to write the result

No output schema declared.

No examples provided.

condense_document ~149

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.

NameTypeReqDescription
document_pathstringyesAbsolute path to the .docx
instructionsstring–Extra requirements for this job
max_wordsintegeryesTarget word count for the whole document
output_pathstring–Where to write the result; defaults to beside the source
wait_secondsnumber–How long to wait before returning a job id (default 55)

No output schema declared.

No examples provided.

fix_citations ~189

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.

NameTypeReqDescription
document_pathstringyesAbsolute path to the .docx
instructionsstring–Extra requirements for this job
output_pathstring–Where to write the result; defaults to beside the source
stylestringyesTarget style: apa7, mla9, harvard, chicago_author_date, chicago_notes, ieee, vancouver, gbt7714, gbt7714_author_year, ama, acs, or oscola
wait_secondsnumber–How long to wait before returning a job id (default 55)

No output schema declared.

No examples provided.

free_rehumanize ~278

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.

NameTypeReqDescription
instructionsstring–Extra requirements for this job
job_idstringyesThe finished humanize job to continue (its job_id from humanize_document/check_job)
output_pathstring–Where to write the result; defaults to beside the report
report_pathstringyesAbsolute path to the fresh Turnitin/iThenticate report for that job's result
segmentsarray–Per-passage word control for the still-flagged passages (optional), same shape and experimental caveat as humanize_document.segments
wait_secondsnumber–How long to wait before returning a job id (default 55)

No output schema declared.

No examples provided.

get_credit_balance ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

humanize_document ~414

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.

NameTypeReqDescription
document_pathstringyesAbsolute path to the .docx or .pptx to rewrite
instructionsstring–Extra requirements for this job
max_wordsinteger–Upper word bound for the rewritten document (optional; omit for no limit). Same experimental caveat and exclusivity as min_words.
min_wordsinteger–Lower word bound for the rewritten document (optional; omit for no limit). Experimental - a word limit noticeably weakens AI-rate reduction, so omit unless the user requires a length. Cannot combine…
output_pathstring–Where to write the result; defaults to beside the source
report_pathstring–Path to a Turnitin/iThenticate AI report PDF; only its flagged passages are rewritten
segmentsarray–Per-passage word control (optional): each item is a flagged passage plus its own min_words/max_words. Get the passage texts from read_detection_report and pass report_path alongside so the report def…
strategystring–Rewriting intensity; balanced is the usual first choice, aggressive rewrites more heavily
wait_secondsnumber–How long to wait before returning a job id (default 55)

No output schema declared.

No examples provided.

read_detection_report ~111

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.

NameTypeReqDescription
include_segmentsboolean–Include the flagged passage texts, which can be long (default false)
report_pathstringyesAbsolute path to the report PDF
typestring–Which product exported it; omit to identify it from the file

No output schema declared.

No examples provided.

translate_document ~197

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.

NameTypeReqDescription
document_pathstringyesAbsolute path to the document
output_pathstring–Where to write the result; defaults to beside the source
source_langstring–Source language, or auto to detect it (the default)
target_langstringyesTarget language: zh, en, zh-tw, ja, ko, es, fr, pt, ru, de, pl or it
wait_secondsnumber–How long to wait before returning a job id (default 55)

No output schema declared.

No examples provided.

Install

How do I install the io.github.humanpen/humanpen-mcp server?

io.github.humanpen/humanpen-mcp runs locally as an npm package, launched with npx -y humanpen-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · humanpen-mcp

# add to Claude Code
claude mcp add humanpen-humanpen-mcp -- npx -y humanpen-mcp
Common questions

What is the io.github.humanpen/humanpen-mcp server?

io.github.humanpen/humanpen-mcp is listed in the public MCP registry as io.github.humanpen/humanpen-mcp. Document-level AI humanizer for .docx/.pptx: whole file, selected passages, or flagged text. This page covers its npm package (humanpen-mcp).

Is the io.github.humanpen/humanpen-mcp server safe to use?

io.github.humanpen/humanpen-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.humanpen/humanpen-mcp server expose?

io.github.humanpen/humanpen-mcp exposes 8 tools: humanize_document, free_rehumanize, fix_citations, condense_document, translate_document, and 3 more. Their descriptions and schemas cost roughly 1,472 tokens of context every time the server is loaded.

Is the io.github.humanpen/humanpen-mcp server still maintained?

io.github.humanpen/humanpen-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.humanpen/humanpen-mcp server under?

io.github.humanpen/humanpen-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.