A
licenseA
qualityD
maintenanceEnables AI attribution audits and quick transparency checks on written content, providing authorship analysis and segment breakdowns for editorial review.
2
2
MIT
avoid-ai-writing-mcp
avoid-ai-writing-mcp
게시된 avoid-ai-writing-detector를 사용하여 산문을 감사하기 위한 로컬 결정적 MCP 서버입니다.
두 가지 읽기 전용 도구를 제공합니다:
score_text는 간결한 점수, 분류, 신뢰도 및 개수를 반환합니다.audit_text는 플래그가 지정된 모든 패턴, 제안된 대안, 통계 및 강조 표시된 문장 영역을 추가합니다.
이 서버는 네트워크 호출을 하지 않으며 언어 모델을 사용하지 않습니다. 텍스트는 로컬 MCP 프로세스 내에 유지됩니다. 점수는 휴리스틱 작성 패턴 신호이지, 사람이나 모델이 텍스트를 작성했음을 증명하는 것이 아닙니다.
요구 사항
Node.js 18 이상
로컬 stdio 서버를 지원하는 MCP 호스트
Related MCP server: Byakugan: Private, open-source AI-text checker
GitHub에서 실행
Claude Code에 이 서버를 추가하세요:
claude mcp add avoid-ai-writing -- npx -y github:conorbronsdon/avoid-ai-writing-mcp또는 MCP JSON 구성에 추가하세요:
{
"mcpServers": {
"avoid-ai-writing": {
"command": "npx",
"args": ["-y", "github:conorbronsdon/avoid-ai-writing-mcp"]
}
}
}패키지가 npm에 게시된 후에는 GitHub 패키지 사양을 avoid-ai-writing-mcp로 바꾸세요.
이 패키지는 프로토콜 메시지에 stdio를 사용합니다. 포트를 열거나 API로 입력을 보내지 않습니다.
도구 입력
두 도구 모두 다음을 허용합니다:
필드 | 유형 | 필수 | 설명 |
| string | 예 | 로컬에서 평가할 텍스트(최대 100,000자). |
| enum | 아니요 |
|
technical 모드는 코드 인접 작성에서 일반적인 패턴의 노이즈를 줄입니다. 다른 모드는 감지기의 컨텍스트별 동작을 유지합니다.
개발
npm install
npm test
npm run inspectnpm run inspect는 로컬 stdio 진입점에 대해 공식 MCP Inspector를 실행합니다.
범위
이 패키지는 의도적으로 재작성 도구를 제공하지 않습니다. 재작성에는 편집상의 판단과 종종 호스팅 모델이 필요합니다. 이를 추가하면 이 서버의 결정적이고 로컬이며 개인 정보를 보호하는 계약이 훼손될 수 있습니다.
라이선스
MIT
Available Tools
2 toolsaudit_textAudit text for AI-writing patternsARead-onlyIdempotent
Audit text locally with the deterministic Avoid AI Writing detector. Returns the score plus up to 100 flagged patterns and 100 highlighted sentence regions, with truncation counts. This is a heuristic writing audit, not proof of authorship; use score_text for a compact result.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to evaluate locally. The text is not sent to any network service. | |
| context | No | Writing context. Technical mode suppresses patterns common in code-adjacent prose; defaults to general. | general |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| label | Yes | |
| score | Yes | |
| issues | Yes | |
| context | Yes | |
| scorable | Yes | |
| truncated | Yes | |
| confidence | Yes | |
| highlights | Yes | |
| statistics | Yes | |
| word_count | Yes | |
| issue_count | Yes | |
| probabilities | Yes | |
| classification | Yes | |
| unscored_reason | Yes |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds valuable behavior beyond that: the audit runs locally, is deterministic, returns up to 100 flagged patterns and 100 highlighted sentence regions, and includes truncation counts. It also disclaims that the result is heuristic rather than proof, which is essential context for the agent's interpretation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each earning its place: one identifies the action and method, one lists the return bounds and truncation behavior, and one sets expectations and routes to the sibling. The most decision-relevant facts are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists, the annotations cover safety, and the description covers local processing, deterministic behavior, response bounds, truncation counts, and the heuristic caveat, an agent has everything it needs to select and invoke the tool correctly. The only thing left to the schema is the context enum, which is appropriately delegated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the text and context parameters are already documented. The description adds no extra parameter semantics, but it doesn't need to because the schema carries that weight. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Audit text'), names the concrete detector ('the deterministic Avoid AI Writing detector'), and distinguishes this tool from its sibling score_text by describing the richer audit output. An agent can tell exactly what this tool does and how it differs from the sibling without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear usage context: it is a local, deterministic, heuristic writing audit and not proof of authorship. It explicitly says to use score_text when a compact result is needed, naming the alternative and the condition that selects it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
score_textScore text for AI-writing patternsARead-onlyIdempotent
Score text locally with the deterministic Avoid AI Writing detector. Returns a compact 0-100 pattern score, classification, confidence, and counts. This is a heuristic signal, not proof of authorship; use audit_text when individual findings are needed.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to evaluate locally. The text is not sent to any network service. | |
| context | No | Writing context. Technical mode suppresses patterns common in code-adjacent prose; defaults to general. | general |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| label | Yes | |
| score | Yes | |
| context | Yes | |
| scorable | Yes | |
| confidence | Yes | |
| word_count | Yes | |
| issue_count | Yes | |
| probabilities | Yes | |
| classification | Yes | |
| unscored_reason | Yes |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive hints. The description adds critical behavioral traits: the detector is deterministic, it is a heuristic signal not proof of authorship, and it operates locally. These go beyond the annotations and help calibrate trust in the output.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The action and scope are front-loaded, the caveat is stated compactly, and the alternative is offered in the same breath. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a rich output schema, complete parameter documentation, and strong annotations. The description covers the operation's purpose, the caveat about heuristic results, and the routing to audit_text. Nothing an agent needs to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% – both parameters have clear descriptions (text is local, context has default and behavior). The description itself does not add parameter-specific semantics beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Score'), a resource ('text'), and the exact detector ('Avoid AI Writing'). It also names the sibling tool 'audit_text' and differentiates by saying when audit_text is needed, so it clearly distinguishes from the alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says to 'use audit_text when individual findings are needed', implying this tool is for a compact score. It also notes the operation is local and deterministic, giving clear context for when to choose this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
audit_text4 fields changed- added
Output schema / properties / highlights / maxItemsAdded value: +100 - added
Output schema / properties / issues / maxItemsAdded value: +100 - added
Output schema / properties / truncatedAdded value: +{ + "additionalProperties": false, + "properties": { + "highlights": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "issues": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "issues", + "highlights" + ], + "type": "object" +} - changed
Output schema / requiredPrevious value: -[ - "score", - "label", - "scorable", - "unscored_reason", - "classification", - "confidence", - "probabilities", - "word_count", - "issue_count", - "context", - "issues", - "statistics", - "highlights" -]New value: +[ + "score", + "label", + "scorable", + "unscored_reason", + "classification", + "confidence", + "probabilities", + "word_count", + "issue_count", + "context", + "issues", + "statistics", + "highlights", + "truncated" +]
2 tool updates
v0.1.0- First observed
audit_text - First observed
score_text
TDQS
A4.7/5.0
Scored across 2 tools
Disambiguation5/5
score_text and audit_text have clearly separated purposes: one returns a compact classification while the other returns detailed flagged patterns and highlighted regions. The cross-references in the descriptions remove any real ambiguity about which tool to use.
Naming Consistency5/5
Both tool names follow the same verb_noun pattern with lowercase snake_case and concise action words. This is fully consistent and predictable.
Tool Count4/5
Two tools is slightly below the typical 3-15 range, but for a narrowly scoped local text detector the pair covers both a compact score and a detailed audit. Each tool has a distinct, useful role, so the small count feels intentional rather than inadequate.
Completeness5/5
The server's apparent domain is deterministic AI-writing detection on text, and the two tools cover the full user journey: getting a quick judgment or drilling into specific flagged patterns and highlighted regions. There are no obvious missing operations for this stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
DraftCheck: flags AI-writing patterns in prose with fix hints. Deterministic linter, not a detector.
Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free.
Deterministic prompt-injection detector; signed, offline-verifiable verdicts. Not an LLM.
Six tools for SEO and AI-readability audits. 91 checks, 11 score modules.
Related MCP Servers
- AlicenseAqualityDmaintenanceA private, open-source AI-text checker. Get a read on whether text looks AI-written, the exact AI-tell spans to fix, a reuse check, and a grammar pass.4MIT
- AlicenseAqualityAmaintenanceBilingual (EN/ES) AI-writing detection that shows the evidence instead of a percentage: named tells with line and column, hidden-character inspection, and citation cross-checking against a document's own bibliography. Seven of its nine tools run entirely locally and never touch the network.1027MIT
- AlicenseAqualityCmaintenanceEnables editorial content QA over the Model Context Protocol with four local tools that analyze readability, AI-sounding language, SEO on-page factors, and produce full reports where every finding includes an actionable fix.41MIT