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.

Moltline Humanizer

REMOTE · MCP.MOLTLINESTUDIO.COM · SCANNED SEP 21

Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free.

+1 this week 87 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1409 tokens (~281/item across 5 items; 5 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Install

How do I install the Moltline Humanizer MCP server?

Moltline Humanizer is a hosted endpoint at https://mcp.moltlinestudio.com/humanizer, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.moltlinestudio.com

# add to Claude Code
claude mcp add --transport http com-moltlinestudio-humanizer 'https://mcp.moltlinestudio.com/humanizer'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-moltlinestudio-humanizer": {
      "url": "https://mcp.moltlinestudio.com/humanizer"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-moltlinestudio-humanizer": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/humanizer"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-moltlinestudio-humanizer]
url = "https://mcp.moltlinestudio.com/humanizer"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moltlinestudio-humanizer": {
      "type": "remote",
      "url": "https://mcp.moltlinestudio.com/humanizer",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-moltlinestudio-humanizer --url 'https://mcp.moltlinestudio.com/humanizer' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-moltlinestudio-humanizer:
    url: "https://mcp.moltlinestudio.com/humanizer"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-moltlinestudio-humanizer": {
      "Transport": "http",
      "Url": "https://mcp.moltlinestudio.com/humanizer"
    }
  }
}
# add to Vellum
assistant mcp add com-moltlinestudio-humanizer -t streamable-http -u 'https://mcp.moltlinestudio.com/humanizer'
// mcp.json
{
  "mcpServers": {
    "com-moltlinestudio-humanizer": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/humanizer"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 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.

  • 13 Sept 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.

  • 11 Sept 26 +1

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

  • 9 Sept 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.

  • 6 Sept 26 +1

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

  • 4 Sept 26 +1

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

  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 21 Sept 2026 · Probed https://mcp.moltlinestudio.com/humanizer

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=moltlinestudio.com CN=WE1,O=Google Trust Services,C=US 15 Aug 2026 13 Nov 2026 ECDSA 256 ECDSA-SHA256 72e09c6114448e7a0ed370fb03c277cb
SANs: moltlinestudio.com, *.moltlinestudio.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.moltlinestudio.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
moltlinestudio.com. present 2371 13 Verified
mcp.moltlinestudio.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15576000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.moltlinestudio.com/humanizer Verified 200
http (plaintext) http://mcp.moltlinestudio.com/humanizer HTTPS enforced 301 https://mcp.moltlinestudio.com/humanizer
MCP tools · 5 exposed · ~1,322 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
ai_tell_scan ~271

Scan a draft for the measurable tells of AI-generated prose. FREE. Flags stock phrases (with exact quotes), structural reflexes, uniform sentence rhythm, em-dash overuse, and hedging boilerplate — every flag cites the actual text. Typical input {"text": "<draft>"} returns {"reads_human_score": 0-100, "metrics": {"burstiness": ..., "avg_sentence_len": ..., ...}, "evidence": [{"type": "stock_phrase", "quote": "..."}], "note": "..."}. Use for a first read on whether a draft carries machine-writing signals. Reports measurable patterns, not a verdict on who wrote the text, and must not be used to accuse a person of anything. Not for rhythm detail (burstiness_report) or for a rewrite brief (humanize_plan). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "empty text"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
textstringyesThe draft to scan — at least one full sentence of plain text.

Structured output declared, but exposes no named fields.

No examples provided.

burstiness_report ~230

Map a draft's sentence rhythm and find where it goes flat. FREE. Reports per-sentence lengths, the burstiness coefficient, and runs of similar-length sentences. Typical input {"text": "<draft>"} returns {"sentence_lengths": [12, 14, 13, 5, 28], "burstiness": 0.52, "flat_runs": [{"sentences": "1-3", "lengths": [12, 14, 13]}], "tip": "..."}. Use when prose reads flat and sentence-length pattern is the suspect. Not for a full inventory of tells (ai_tell_scan). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "need 3+ sentences"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
textstringyesThe draft to analyze; needs at least 3 sentences.

Structured output declared, but exposes no named fields.

No examples provided.

humanize_plan ~260

Produce a precise rewrite brief that de-AIs a draft, with numeric targets. PREMIUM (license). Lists every flagged tell with its fix and sentence-rhythm surgery targets; when a voice_fingerprint result is supplied, adds numeric targets to hit that person's voice. Apply the brief with your agent, then confirm with verify_rewrite. Typical input {"text": "<draft>", "fingerprint": <voice_fingerprint result>} returns {"current_score": 0-100, "edit_list": ["..."], "numeric_targets": {...}, "process": ..., "integrity_note": ...}. Use after a scan has identified what to fix; returns a brief, not rewritten prose. Not for checking whether a rewrite worked (verify_rewrite). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
fingerprintobjectOptional voice profile object exactly as returned by voice_fingerprint; omit for a style-only pass.
textstringyesThe AI draft to plan a rewrite for.

Structured output declared, but exposes no named fields.

No examples provided.

verify_rewrite ~280

Verify a rewrite actually improved: score delta, meaning check, voice distance. PREMIUM (license). Compares reads-human score before/after, a meaning-preservation proxy, and (with a fingerprint) numeric distance to the target voice. Typical input {"original": "<draft>", "rewrite": "<edited draft>"} returns {"score_before": N, "score_after": N, "score_delta": N, "content_word_retention_pct": N, "remaining_tells": [...], "verdict": "Improved — ship it" | "Marginal — ..."}. Use only when both the before and the after text are available. Not for scoring a single draft (ai_tell_scan). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "both texts must be non-empty"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
fingerprintobjectOptional voice profile object exactly as returned by voice_fingerprint, to measure distance to the target voice.
originalstringyesThe draft before editing.
rewritestringyesThe same content after the humanize_plan edits.

Structured output declared, but exposes no named fields.

No examples provided.

voice_fingerprint ~281

Build a measurable voice profile from samples of a person's real writing. FREE. Feed it 2+ samples (emails, posts, essays — 150+ words total) and use the result with humanize_plan / verify_rewrite. Typical input {"samples": ["<email text>", "<blog post>"]} returns {"label": "my-voice", "target_metrics": {"avg_sentence_len": ..., "burstiness": ..., ...}, "favorite_words": [...], "signature_habits": ["..."], "words_analyzed": N}. Use on samples the person actually wrote, to build a target profile. Not for scoring an unknown draft (ai_tell_scan) and not on text the person did not write. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "need 150+ words of real writing across the samples"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
labelstringOptional name for this voice profile. Default "my-voice".
samplesarrayyesList of real writing samples by the same person; 150+ words combined across all samples.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Moltline Humanizer MCP server?

Moltline Humanizer is an MCP server listed in the public MCP registry as com.moltlinestudio/humanizer. Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/humanizer).

Is the Moltline Humanizer MCP server safe to use?

Moltline Humanizer scores 87 out of 100 on VerifyMCP. 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 Moltline Humanizer MCP server expose?

Moltline Humanizer exposes 5 tools: ai_tell_scan, voice_fingerprint, burstiness_report, humanize_plan, verify_rewrite. Their descriptions and schemas cost roughly 1,322 tokens of context every time the server is loaded.

Does the Moltline Humanizer MCP server require authentication?

No. We connected to Moltline Humanizer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Moltline Humanizer MCP server still maintained?

Moltline Humanizer is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.