
Being Human
io.github.Syedomershah99Published by GitHub account Syedomershah99v0.1.2Updated Oct 28, 2026
Learns your writing voice from your own prompt history, then makes the model write like that.
The publisher's own server: TAP
Overview
Learns your personal writing voice from your own prompt history and returns style rules so the assistant writes more like you.
- What you can do
- Harvest and measure your writing from Claude Code history, a ChatGPT export or your own files, with an optional contrast pass against the model's side of the transcripts.
- Return voice rules with concrete numbers, plus a personal list of words to avoid derived by log-odds contrast.
- Check a draft for generic AI tells, rhythm and structure.
- Verify whether a draft is statistically you, using authorship distance against your own corpus.
- Export the voice profile for ChatGPT, agents, Cursor, a system prompt or JSON, and draw a shareable voiceprint card.
- Every tool returns the voice rules alongside its own result, so a score never arrives without the target attached.
- When to use it
- Useful when you want an assistant's drafts to sound like your own writing rather than generic AI prose, or when you want a local, arithmetic check on whether a text is yours or slop. Best for people with a substantial body of existing writing to learn from.
- Requirements
- Runs as a local stdio process, installed from PyPI as being-human and launched with uvx or the being-human-mcp command. Needs Python 3 (standard library only, no dependencies) and a local corpus: Claude Code history, a ChatGPT export, or your own files. No network calls, accounts, API keys or environment variables.
Installation
In SourceWeft
- Open Being Human in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
being-human
Your assistant writes like a press release because it doesn't know who you are. This tells it.
being-human reads the prompts you've already typed, measures how you actually write, and hands the model a description of your voice specific enough to follow. It also builds a list of words to avoid, computed by contrast against the model's own output, so it's personal to you rather than borrowed from a blog post about ChatGPT tells.
Local, stdlib Python 3, no dependencies, no network calls.
my own writing, measured by this tool. every bar is one real
sentence. make your own with being-human card.
quickstart
No Claude Code history? Point it at a ChatGPT export or your own files:
what comes out
Instructions with numbers attached, because "be concise" is not actionable and "your median message is 12 words" is:
the contrast trick
Your transcripts contain both sides of every conversation. So every word can be scored by log-odds: how much more likely you are to use it than the model is, on the same topics, in the same threads. The top of that list is your voice. The bottom is the model's.
Mine came back actually, clean, rather, genuinely, exactly, roughly. None of
those appear on any published list of AI words. They're the specific tics this
model has when talking to me. Yours will differ, because the contrast is against
your writing.
two checks, not one
They catch different failures, and passing one says nothing about the other:
Measured on my own corpus:
Row two is the catch: slop has unremarkable grammar, so authorship distance passes it. Row three is clean prose with no tells that is plainly a different hand. The second case is the one nobody else tests for, and it's the one that bites.
Held-out chunks of real writing sit at the 49th to 60th percentile, with a 1-6% false-positive rate above p97. Thresholds are personal. Em dashes get flagged against your measured rate rather than a universal rule, which is why this doesn't punish people who genuinely use them.
mcp server
Seven tools, two resources, two prompts. Configs for Claude Desktop, Cursor, Codex and Zed are in mcp/README.md.
MCP tools are model-invoked and nothing forces a model to call one, which is awkward when the payload is instructional. So every tool returns the voice rules alongside its own result. There's no path through the server that hands back a score without the target attached.
There's a Claude Code plugin too, via
/plugin marketplace add Syedomershah99/being-human. It adds
/being-human:learn, :check, :write, :verify, :export, and a hook that
grows the corpus as you type.
privacy
Everything is local. Grep for urllib, requests or socket and you'll find
nothing. Secrets are redacted at harvest time before anything touches disk, and
.being-human/ is gitignored. The voiceprint is safe to share. The corpus it was
built from is not.
prior art
This space got crowded in 2026. inside-lago framed the thesis, slop-guard is a mature slop linter, idiolect is architecturally closest, and writer-persona had the best idea of the lot: validate the profile with a backtest instead of trusting it.
Two things here I couldn't find elsewhere. The user-vs-model contrast, which derives the avoid-list from both sides of your own transcripts rather than from a curated list. And a deterministic impostor test. writer-persona uses an LLM judge across 8 axes; this is arithmetic, so it costs nothing and returns the same answer every time.
Burrows's Delta and log-odds with a Dirichlet prior are both established methods. The claim is the application and the calibration, not the statistics.
license
MIT. The tell list is data/slop-lexicon.json. If you keep seeing something that isn't in there, send a PR.
mcp-name: io.github.Syedomershah99/being-human
Source: README.md at commit 9826b30
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Human integrations

TAP
tech.humanOfficial publisher
TAP is a hosted remote MCP endpoint that isolates AI agents' credentials using placeholder secrets, policy checks and optional human approval.
UGC, the Human Ad Network
africa.ugcOfficial publisher
Remote MCP endpoint for UGC, a "Human Ad Network", letting an assistant work with ad campaigns, clipping and Clip Studio from chat.

PromptHuman
Published by GitHub account prompthumanhq
Lets an assistant request paid, asynchronous judgment from a real person — gut checks, how text reads, plausibility, local context — and track the reply.

HITL (Human in the Loop)
Published by GitHub account hitl-sh
Lets an AI assistant run HITL workflows that ask a real person for a decision on their phone and wait for the answer.
Human Use
dev.humanuse
Turns a person into MCP tools: an agent calls tools like photo or errand, a card appears on their phone, and the answer returns as JSON.