HumanifyMe
NPM · HUMANIFYME
Learns your writing voice locally and rewrites AI drafts so they sound like you.
Available components
Last scanned (1 hour ago)
Scores higher than 89% of npm servers
Category AI and Machine Learning
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
- A known CVE affects sprintf-js, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 46 of 132 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to JoshMcQ/HumanifyMe). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- 63% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 929 tokens (~48/item across 19 items; 16 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "humanify_delete_sample" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 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.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
- Security disclosure: pass → unverified ▼ functional
- 7 Oct 26 +1
- CVE-2026-97058 affects this package ▼ security
- Known CVEs: pass → partial ▼ security
- 4 Oct 26 +5
- Stability: unverified → 0.30 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 17 Oct 2026 · Analysed npm/humanifyme@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | JoshMcQ/HumanifyMe |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/JoshMcQ/HumanifyMe/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 2962245877 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2f3a63fdf1456c8ccdef2016624e0df1eb0062e12125071060d0686b1180d0f3fe538c909de3b60b521a2142b1baaaccdecad3a99fbd1051a002f936c |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-hp3w-g68c-fv3c | CVE-2026-97058 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 132 packages
| Packages resolved | 132 |
|---|---|
| Stale | 46 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
humanify_add_sample ~60
Store a writing sample (something the user actually wrote) so HumanifyMe can learn their voice. Text must be at least 100 characters and carry at least one context label.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | array | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
humanify_audit_list ~47
List the most recent outbound requests HumanifyMe made (metadata only, never content): provider, route, payload size, draft length, success.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
humanify_build_profile ~55
Build (or rebuild with force:true) the user's style profile from their stored samples. Needs at least 3 samples. Samples are redacted before being sent to the configured LLM provider.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
No output schema declared.
No examples provided.
humanify_delete_profile ~20
Delete the current style profile. Samples are kept.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
humanify_delete_sample ~25
Delete a stored writing sample by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
humanify_get_profile ~25
Return the user's current style profile, or null if none has been built.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
humanify_import_chat_export ~82
Import writing samples from a ChatGPT or Claude data-export (.zip, conversations.json, or extracted directory). Only user-authored turns are kept; code-heavy turns are dropped; everything is redacted before storage. Call with commit:false first to preview 5 samples, then commit:true.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | boolean | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
humanify_import_text_files ~81
Bulk-import writing samples from a directory (or single file) of .txt/.md/.docx the user wrote — notes, blog drafts, an Obsidian vault. Requires a default context label. Files are redacted before storage; oversize files split at paragraph boundaries.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
humanify_list_samples ~30
List stored writing samples (previews truncated to 200 chars).
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | – |
No output schema declared.
No examples provided.
humanify_metrics ~85
Show how well HumanifyMe is matching the user's voice, from their own recorded feedback: total rewrites, accept/edit/reject rates, "sounds like me" breakdown, per-context and per-provider counts, and p50/p95 latency. Local only; counts, never content. Optional `since` (ISO timestamp) windows the stats.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | – |
No output schema declared.
No examples provided.
humanify_record_feedback ~126
Record whether a humanify_text rewrite sounded like the user. Pass the feedbackToken from that rewrite and a signal: 'accept' (sounded like me / used as-is), 'edit' (kinda — I tweaked it), or 'reject' (no — didn't sound like me). Optional short reason. This powers local quality metrics (humanify_metrics) and, only if the user opted in, anonymous aggregate counts.
| Name | Type | Req | Description |
|---|---|---|---|
| editedText | string | – | – |
| reason | string | – | – |
| signal | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
humanify_set_provider ~75
Configure local Ollama and make it the default. Cloud API keys are intentionally rejected in MCP tool arguments because the host model can see them; configure cloud providers with the interactive `humanifyme setup` CLI instead.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | – | – |
| model | string | – | – |
| provider | string | yes | – |
No output schema declared.
No examples provided.
humanify_test_key ~33
Confirm the configured API key works with a cheap (≤1 token) ping.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | – |
No output schema declared.
No examples provided.
humanify_text ~83
Rewrite a draft (usually AI-generated) so it reads in the user's own voice, using their stored style profile. The headline tool: call this whenever the user wants text to 'sound like me' or 'less AI'.
| Name | Type | Req | Description |
|---|---|---|---|
| contextLabel | string | – | – |
| directives | array | – | – |
| draft | string | yes | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
humanify_update_profile ~42
Replace the style profile with an edited version (schema-validated). Use for manual tweaks; does not call any LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | yes | – |
No output schema declared.
No examples provided.
humanify_wipe_all ~45
Delete ALL HumanifyMe data: samples, profile, cache, audit log. Irrevocable. Requires confirm: "DELETE EVERYTHING".
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | – |
No output schema declared.
No examples provided.
How do I install the HumanifyMe MCP server?
HumanifyMe runs locally as an npm package, launched with npx -y humanifyme. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · humanifyme
claude mcp add joshmcq-humanifyme -- npx -y humanifyme
What is the HumanifyMe MCP server?
HumanifyMe is an MCP server listed in the public MCP registry as io.github.JoshMcQ/humanifyme. Learns your writing voice locally and rewrites AI drafts so they sound like you. This page covers its npm package (humanifyme).
Is the HumanifyMe MCP server safe to use?
HumanifyMe scores 86 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 HumanifyMe MCP server expose?
HumanifyMe exposes 16 tools: humanify_text, humanify_record_feedback, humanify_metrics, humanify_add_sample, humanify_list_samples, and 11 more. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.
Is the HumanifyMe MCP server still maintained?
HumanifyMe is still listed as active in the MCP registry. We last reached this channel on 17 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 HumanifyMe MCP server under?
HumanifyMe 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.