io.github.Syedomershah99/being-human
PYPI · BEING-HUMAN
Learns your writing voice from your own prompt history, then makes the model write like that.
Available components
Last scanned (10 hours ago)
Scores higher than 88% of PyPI servers
Category Developer Tools
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 83 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1048 tokens (~116/item across 9 items; 7 tools + 2 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Provenance: unverified → fail ▼ security
- 28 Oct 26 0
- Provenance: fail → unverified ▼ security
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −1
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed pypi/being-human@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
voice_export ~94
Compile the voiceprint into a format another tool reads: 'chatgpt' (custom instructions box, ~1500 chars), 'agents' (AGENTS.md), 'cursor' (.cursorrules), 'claude' (CLAUDE.md), 'system' (raw system prompt), or 'json'. Use when the user wants their voice set up in a different assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
voice_get ~104
Get the user's measured writing voice as explicit rules. CALL THIS BEFORE writing any prose the user will send or publish under their own name -- a post, email, reply, bio, doc, commit message, cover letter, or anything else in their name. The rules are measured from their own past writing (sentence rhythm, casing, punctuation rates, vocabulary, words to avoid), so they override your defaults. Cheap and fast; call it rather than guessing what the user sounds like.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
voice_learn ~151
Build or refresh the voiceprint from the user's own writing. Sources: 'claude-history' and 'claude-projects' (local Claude Code history), 'chatgpt' (a conversations.json from a ChatGPT data export, needs path), 'files' (a folder of the user's own writing, needs path). Takes a few seconds. Run this once at setup, or again to fold in newer writing.
| Name | Type | Req | Description |
|---|---|---|---|
| append | boolean | – | Add to the existing corpus instead of replacing. |
| name | string | – | The user's name, for labelling. |
| path | string | – | Required for 'chatgpt' and 'files'. |
| source | string | yes | Where to harvest from. |
No output schema declared.
No examples provided.
voice_note ~103
Record something about the user's voice that measurement cannot reach -- a phrase they have banned, who they are usually writing for, a correction they just made to your draft, a running joke. Use this whenever the user says 'I wouldn't say that', 'too formal', or rewrites something you wrote. Notes persist across every rebuild of the voiceprint and tend to matter more than the statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | The rule or observation, in one or two sentences. |
No output schema declared.
No examples provided.
voice_score ~133
Score a draft 0-100 for AI tells and get line-level findings. CALL THIS ON EVERY DRAFT before showing it to the user. Checks a curated slop lexicon plus structural signals -- sentence-length uniformity, paragraph shape, bullet symmetry, punctuation rates -- against THIS user's own measured baseline rather than universal rules. Above 85 reads human, below 50 is slop. Also returns the voice rules, so one call gives you both the critique and the target.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a file to score, instead of text. |
| text | string | – | The draft text to score. |
No output schema declared.
No examples provided.
voice_status ~61
Check whether a voiceprint exists and how solid it is: sample count, word count, when it was built, and whether the corpus is large enough for the measurements to be stable. Use this when you are not sure the user has set being-human up yet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
voice_verify ~147
The impostor test: statistically, is this text a plausible sample of THIS user? Returns an authorship percentile against a null resampled from their own writing at the same length. Under 75 means indistinguishable from them; over 97 means it reads as someone else. This is a different question from voice_score -- that one catches AI tells, this one catches 'fluent, clean, and not you'. Run BOTH on any draft before showing it; a draft has to pass each. Also names the specific words that pushed it out of range.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a file, instead of text. |
| text | string | – | The draft text to test. |
No output schema declared.
No examples provided.
How do I install the io.github.Syedomershah99/being-human MCP server?
io.github.Syedomershah99/being-human runs locally as a PyPI package, launched with uvx being-human. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · being-human
claude mcp add syedomershah99-being-human -- uvx being-human
What is the io.github.Syedomershah99/being-human MCP server?
io.github.Syedomershah99/being-human is an MCP server listed in the public MCP registry as io.github.Syedomershah99/being-human. Learns your writing voice from your own prompt history, then makes the model write like that. This page covers its PyPI package (being-human).
Is the io.github.Syedomershah99/being-human MCP server safe to use?
io.github.Syedomershah99/being-human scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.Syedomershah99/being-human MCP server expose?
io.github.Syedomershah99/being-human exposes 7 tools: voice_get, voice_score, voice_verify, voice_status, voice_learn, and 2 more. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.
Is the io.github.Syedomershah99/being-human MCP server still maintained?
io.github.Syedomershah99/being-human 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 io.github.Syedomershah99/being-human MCP server under?
io.github.Syedomershah99/being-human declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.