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.

GoHumanize Open Humanizer

NPM · GOHUMANIZE-OPEN-HUMANIZER-MCP

Rewrite AI-styled text into natural writing with a fine-tune model.

0 this week 84 Trust /100

Last scanned (1 hour ago)

Scores higher than 81% of npm servers

Category AI and Machine Learning

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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 176 tokens (~88/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

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 5 Nov 2026 · Analysed npm/gohumanize-open-humanizer-mcp@0.1.12

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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~176 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
about_open_humanizer ~47

Describe the GoHumanize Open Humanizer: what it is, how it was trained, where the model, dataset and paper are published, and which endpoint this server is using.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

humanize_text ~129

Rewrite a passage of AI-styled English prose so it reads more like a person wrote it, keeping the meaning, facts and order of ideas. Uses the GoHumanize Open Humanizer, a small open model (Qwen3-4B fine-tune) trained on public-domain prose. Best on passages of 50 to 400 words; longer inputs are processed paragraph by paragraph. Educational model: no claim about AI detectors.

NameTypeReqDescription
temperaturenumber–Sampling temperature, default 0.9; lower is more literal
textstringyesThe text to rewrite (English)

No output schema declared.

No examples provided.

Install

How do I install the GoHumanize Open Humanizer MCP server?

GoHumanize Open Humanizer runs locally as an npm package, launched with npx -y gohumanize-open-humanizer-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 · gohumanize-open-humanizer-mcp

# add to Claude Code
claude mcp add gohumanize-ai-gohumanize-open-humanizer-mcp -- npx -y gohumanize-open-humanizer-mcp
Common questions

What is the GoHumanize Open Humanizer MCP server?

GoHumanize Open Humanizer is an MCP server listed in the public MCP registry as io.github.GoHumanize-ai/gohumanize-open-humanizer-mcp. Rewrite AI-styled text into natural writing with a fine-tune model. This page covers its npm package (gohumanize-open-humanizer-mcp).

Is the GoHumanize Open Humanizer MCP server safe to use?

GoHumanize Open Humanizer scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 GoHumanize Open Humanizer MCP server expose?

GoHumanize Open Humanizer exposes 2 tools: humanize_text, about_open_humanizer. Their descriptions and schemas cost roughly 176 tokens of context every time the server is loaded.

Is the GoHumanize Open Humanizer MCP server still maintained?

GoHumanize Open Humanizer is still listed as active in the MCP registry. We last reached this channel on 5 November 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 GoHumanize Open Humanizer MCP server under?

GoHumanize Open Humanizer 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.